Xiaofeng Wang

1. The connection issue is caused by issue https://github.com/fedora-iot/fido-device-onboard-rs/issues/374. It's fixed already. Just re-run will work now. We have a discussion about this issue on slack thread https://coreos.slack.com/archives/C022TDCV3FH/p1672752884390489 2. Can...

@atodorov The ostree.sh covers the edge-commit image type, ostree-ng.sh covers edge-container and edge-installer image types, ostree-raw-image.sh covers edge-raw-image image type, and ostree-simplified-installer.sh covers edge-simplified-installer image type. The reason I suggest...

Test passed in PR https://github.com/coreos/coreos-installer-dracut/pull/18

Yeah, I agree it's not a bug but one of installation scenarios. The `autopart` in kickstart will give `/home` a very big space of the disk. So I filed this...

From my understanding, `bootc install` is OS installation, not OS upgrade. That should be the `delete` case. The `empty` case = `delete` case + re-partition. bootc or bootc submodule might...

I totally agree with you. Our daily test covered much more. We can catch failure with daily test. What about the plan like this: - rhel9.4: x86_64 - rhel9.5: x86_64,...

> This is a huge PR. Is it possible to break it into smaller PRs such that it is less risky and easier to review? It's not easy to split...

For example, `tmt --root . -c arch=x86_64 run --all --verbose -e TEST_OS=fedora-40 -e ARCH=x86_64 -e QUAY_USERNAME=abc -e QUAY_PASSWORD="foobar" -e QUAY_SECRET="quayiouserpassbase64" provision --how local plans --name install-upgrade/to-disk` command will run all...

[Packit](https://packit.dev/) can be one of solutions for bootc testing. There're some benefits we can get from Packit solution: 1. It does not need github runner, that can save github runner...

> I'm still looking at this problem domain; in the short term I did https://github.com/containers/bootc/pull/576 to just clean up that whole framework, but it doesn't cover the "local hermetic VM...