NO-JIRA: Bump fedora-bootc submodule

[coreosbot-releng]

Created by GitHub workflow (source).

Dusty Mabe (1):
      minimal: name systemd-pam in manifest lists

Joseph Marrero Corchado (2):
      kernel-install: Use drop-in config to preserve layout=ostree
      kernel-install: Write layout=ostree to both install.conf and drop-in

Xiaofeng Wang (1):
      Add workaround for https://issues.redhat.com/browse/RHEL-106203

[gemini-code-assist]

Summary of Changes

Hello @coreosbot-releng, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates the update of the fedora-bootc submodule to a more recent version. The primary purpose of this update is to integrate a critical workaround for a known Red Hat issue, ensuring the project benefits from the latest fixes and improvements from the upstream submodule. This change was triggered by an automated GitHub workflow.

Highlights

• Submodule Update: The fedora-bootc submodule has been updated to a newer commit (4da2fc1ec728ecaafff8c1ac9a4fb49572dbf48f) from its previous version (1443b263c4476963286694015c31bd90597fe88a).
• Purpose of Update: This submodule bump incorporates a workaround for the issue tracked at https://issues.redhat.com/browse/RHEL-106203, as indicated by the included commit message.
• Automation: This pull request was automatically generated by a GitHub workflow, ensuring consistent and automated updates.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the fedora-bootc submodule to a new commit. This is an automated change that appears to be a routine dependency bump, incorporating a workaround as mentioned in the commit message. The change itself, updating the submodule pointer, is correct and I see no issues with it.

[dustymabe]

/lgtm

[dustymabe]

/override ci/prow/scos-10-build-test-qemu

chasing down the kernel-rt failure in #163

[openshift-ci]

@dustymabe: Overrode contexts on behalf of dustymabe: ci/prow/scos-10-build-test-qemu

Details

In response to this:

/override ci/prow/scos-10-build-test-qemu

chasing down the kernel-rt failure in #163

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.

[openshift-ci-robot]

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

Details

In response to this:

Created by GitHub workflow (source).

Dusty Mabe (1):
     minimal: name systemd-pam in manifest lists

Joseph Marrero Corchado (2):
     kernel-install: Use drop-in config to preserve layout=ostree
     kernel-install: Write layout=ostree to both install.conf and drop-in

Xiaofeng Wang (1):
     Add workaround for https://issues.redhat.com/browse/RHEL-106203

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.

[dustymabe]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [dustymabe]

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: 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	fc53e1b	link	unknown	/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.