OCPBUGS-20198: Bump fedora-coreos-config

[coreosbot-releng]

Created by GitHub workflow (source).

Aashish Radhakrishnan (2):
      denylist: snooze ext.config.docker.basic on rawhide
      denylist: drop ext.config.kdump.crash test

Jonathan Lebon (4):
      05core/dracut: enable `iscsi` module
      kola/expected-contents: only check for `iscsi_ibft` on supported arches
      manifests: add crun-wasm.yaml
      Revert "coreos-teardown-initramfs: use NetworkManager to teardown networking"

Michael Armijo (1):
      overrides: fast-track glibc-2.37-10.fc38

Steven Presti (1):
      manifest: add bash-color-prompt for >= f39 fixes coreos/fedora-coreos-tracker#1567

Timothée Ravier (3):
      tests/kola/docker: Add a basic docker run test
      ci & tests: Switch to quay.io/fedora/fedora
      tests/kola/docker/basic: Only run on FCOS

gursewak1997 (5):
      upgrade/extended: Get latest release from update server This test fails when it is run during the time period between the stream build and the release. Updated the test to get the last_release from update server and check if there's an edge pointing to it.
      upgrade/extended: Fix last_release_index extraction method Initially, I was getting the last_release_index from the update json file itself under key org.fedoraproject.coreos.releases.age_index whereas we are using the actual index value of the versions as edge values in edges array
      denylist: extend snooze for coreos.ignition.ssh.key
      denylist: bump snooze for ext.config.kdump.crash on aarch64 This test is still failing.
      denylist: snooze kdump.crash for ppc64le in rawhide

[jmarrero]

/retest-required
/lgtm
/approve

[jlebon]

This contains the fix for https://issues.redhat.com/browse/OCPBUGS-19811.

/approve
/lgtm

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD b86ac33 and 2 for PR HEAD 232fd95 in total

[jmarrero]

/retest-required
/lgtm
/approve

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD b86ac33 and 2 for PR HEAD eeda12e in total

[jmarrero]

/retest-required

[jmarrero]

/lgtm

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD b86ac33 and 2 for PR HEAD ef807cf in total

[openshift-merge-robot]

@coreosbot-releng: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/scos-9-build-test-qemu	ef807cf	link	true	/test scos-9-build-test-qemu
ci/prow/rhcos-92-build-test-qemu	ef807cf	link	true	/test rhcos-92-build-test-qemu

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD b2cf889 and 1 for PR HEAD ef807cf in total

[travier]

--- FAIL: ext.config.shared.docker.basic (56.67s)
        cluster.go:162: Error: Unit kola-runext.service exited with code 127

Arg, I missed making this test FCOS only. Will make a PR.

[travier]

coreos/fedora-coreos-config#2659

[jlebon]

Forced a GHA rerun for this since it should now have everything we need. Thanks @travier for fixing the CI failure!

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: coreosbot-releng, jlebon, jmarrero

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jlebon,jmarrero]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@coreosbot-releng: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[sdodson]

/retitle OCPBUGS-20198: Bump fedora-coreos-config

[openshift-ci-robot]

@coreosbot-releng: Jira Issue OCPBUGS-20198: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-20198 has been moved to the MODIFIED state.

In response to this:

Created by GitHub workflow (source).

Aashish Radhakrishnan (2):
     denylist: snooze ext.config.docker.basic on rawhide
     denylist: drop ext.config.kdump.crash test

Jonathan Lebon (4):
     05core/dracut: enable `iscsi` module
     kola/expected-contents: only check for `iscsi_ibft` on supported arches
     manifests: add crun-wasm.yaml
     Revert "coreos-teardown-initramfs: use NetworkManager to teardown networking"

Michael Armijo (1):
     overrides: fast-track glibc-2.37-10.fc38

Steven Presti (1):
     manifest: add bash-color-prompt for >= f39 fixes coreos/fedora-coreos-tracker#1567

Timothée Ravier (3):
     tests/kola/docker: Add a basic docker run test
     ci & tests: Switch to quay.io/fedora/fedora
     tests/kola/docker/basic: Only run on FCOS

gursewak1997 (5):
     upgrade/extended: Get latest release from update server This test fails when it is run during the time period between the stream build and the release. Updated the test to get the last_release from update server and check if there's an edge pointing to it.
     upgrade/extended: Fix last_release_index extraction method Initially, I was getting the last_release_index from the update json file itself under key org.fedoraproject.coreos.releases.age_index whereas we are using the actual index value of the versions as edge values in edges array
     denylist: extend snooze for coreos.ignition.ssh.key
     denylist: bump snooze for ext.config.kdump.crash on aarch64 This test is still failing.
     denylist: snooze kdump.crash for ppc64le in rawhide

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.