Xiaofeng Wang

According to @cgwalters and @martinpitt (Hi, long time no see 😊) chatting, we can move integration test (shell + ansible) part to packit but with some changes: 1. rename this...

Hi @cgwalters. We encountered this issue in QE CI environment many times in two days. All `bootc install to-existing-root` tests failed due to this error. https://artifacts.osci.redhat.com/testing-farm/10a21cd4-b029-48fa-9c23-9848288a7065/ This issue can be...

OH!!!. Since yesterday (Saturday), I can't run container inside `quay.io/fedora/fedora:40`. And reports `Error: configure storage: 'overlay' is not supported over overlayfs, a mount_program is required: backing file system is unsupported...

> And we're also now getting that in the host environment. Can you play with downgrading that in the host environment too? Sure. I'll run that tomorrow.

@cgwalters I re-run the test with an old Fedora 40 runner, tests passed. I checked the log. I found the difference is the latest `containers-common-5:0.59.1-1.fc40` [added composefs](https://src.fedoraproject.org/rpms/containers-common/c/80bb884433729c94027883feec6645cb06069ff5?branch=f40). That might be...

Yes, https://github.com/virt-s1/bootc-workflow-test is using `update_pull_request_status`. But that still needs a github action runner. For example, https://github.com/virt-s1/bootc-workflow-test/actions/runs/8845171999/job/24288556567. Or we can use self hosted runner (container). The https://github.com/virt-s1/bootc-workflow-report repo already uses self...

Yeah, this's a really good solution for self hosted runner. Three reasons I didn't use this solution: 1. This solution needs a public k8s, I can't find a free one....

I usually save QUAY_SECRET into `/etc/ostree/auth.json` and copy auth.json into container image when build image. ``` QUAY_SECRET=$(echo -n "${QUAY_USERNAME}:${QUAY_PASSWORD}" | base64 -w 0) ``` ``` { "auths": { "quay.io": {...

> But anyways I think the larger problem pointed out by the aws error message is the script hardcodes a security group in a specific AZ, when it could really...

> OK, got it. Well...per the other discussion, what if we focused only on fedora:40 and centos:stream9 for PR testing by default I agree. > and did rhel integration testing...