NO-JIRA: Bump fedora-coreos-config

[coreosbot-releng]

Created by GitHub workflow (source).

Steven Presti (1):
      denylist: deny kdump.crash.ssh && ext.config.kdump.crash on s390x

[openshift-ci-robot]

@coreosbot-releng: This pull request explicitly references no jira issue.

Details

In response to this:

Created by GitHub workflow (source).

Steven Presti (1):
     denylist: deny kdump.crash.ssh && ext.config.kdump.crash on s390x

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: coreosbot-releng
Once this PR has been reviewed and has the lgtm label, please assign cgwalters for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[gemini-code-assist]

Code Review

This pull request updates the fedora-coreos-config submodule to a newer commit. The change is an automated bump, as indicated by the pull request description, and incorporates a denylist update for kdump.crash.ssh and ext.config.kdump.crash on s390x within the submodule. No direct code changes are present in this repository, only the submodule reference update.

[openshift-ci]

@coreosbot-releng: The following test 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-10-build-test-qemu	db3b0f5	link	true	/test scos-10-build-test-qemu

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.