Skip to content

fix: clean dirty metal3-dev-env tree between dev-scripts passes#56

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-eng:mainfrom
gamado:fix/dev-scripts-metal3-dirty-tree
Mar 16, 2026
Merged

fix: clean dirty metal3-dev-env tree between dev-scripts passes#56
openshift-merge-bot[bot] merged 1 commit intoopenshift-eng:mainfrom
gamado:fix/dev-scripts-metal3-dirty-tree

Conversation

@gamado
Copy link
Contributor

@gamado gamado commented Mar 15, 2026

dev-scripts' 01_install_requirements.sh uses sed -i to downgrade the ansible version in metal3-dev-env/lib/common.sh (10.7.0 -> 8.7.0 for RHEL 9 Python 3.9 compatibility). This leaves the file dirty. When 'make all' re-runs sync_repo_and_patch, git rebase fails with "cannot rebase: You have unstaged changes".

Add a task to git checkout the modified file after requirements install, before 'make all' runs.

Upstream issue: openshift-metal3/dev-scripts

dev-scripts' 01_install_requirements.sh uses sed -i to downgrade
the ansible version in metal3-dev-env/lib/common.sh (10.7.0 -> 8.7.0
for RHEL 9 Python 3.9 compatibility). This leaves the file dirty.
When 'make all' re-runs sync_repo_and_patch, git rebase fails with
"cannot rebase: You have unstaged changes".

Add a task to git checkout the modified file after requirements install,
before 'make all' runs.

Upstream issue: openshift-metal3/dev-scripts

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci openshift-ci bot requested review from fonta-rh and slintes March 15, 2026 13:49
@openshift-ci
Copy link

openshift-ci bot commented Mar 15, 2026

Hi @gamado. Thanks for your PR.

I'm waiting for a openshift-eng member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Mar 15, 2026
Copy link
Contributor

@fonta-rh fonta-rh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good workaround Gal!

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 16, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fonta-rh, gamado

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 16, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit 5603c93 into openshift-eng:main Mar 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants