Skip to content

openshift/os: Sync 4.11 CI with 4.12, fix image tags for 4.12#29178

Closed
cgwalters wants to merge 1 commit intoopenshift:masterfrom
cgwalters:openshift-os-sync-411
Closed

openshift/os: Sync 4.11 CI with 4.12, fix image tags for 4.12#29178
cgwalters wants to merge 1 commit intoopenshift:masterfrom
cgwalters:openshift-os-sync-411

Conversation

@cgwalters
Copy link
Copy Markdown
Member

Copy all the bits from current master to the 4.11 branch to keep
things in sync.

However, we also fix the tags for the master job to target 4.12.

Copy all the bits from current master to the 4.11 branch to keep
things in sync.

However, we also fix the tags for the master job to target 4.12.
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 6, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cgwalters

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 Jun 6, 2022
initial:
integration:
name: "4.11"
name: "4.12"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This doesn't seem to match some of the other CI configs (MCO, Installer) for the master branch that I checked and I'm curious if this is going to have an adverse affect on the automated branching operation. Any harm in leaving it at 4.11?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

For some reason though, openshift/os is not having its release-4.11 branch fast forwarded to match master automatically today, unlike other repos.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

IOW, things are already not in sync, so we need to this now.

@travier
Copy link
Copy Markdown
Member

travier commented Jun 8, 2022

Whoops, I duplicated part of this one in #29258

@travier
Copy link
Copy Markdown
Member

travier commented Jun 8, 2022

Moving the COSA changes to #29266

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 16, 2022

@cgwalters: 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/rehearse/openshift/os/master/test-qemu-kola 75a6fa9 link unknown /test pj-rehearse
ci/prow/pj-rehearse 75a6fa9 link false /test pj-rehearse
ci/rehearse/openshift/os/master/test-in-cluster 75a6fa9 link unknown /test pj-rehearse
ci/prow/generated-config 75a6fa9 link true /test generated-config
ci/prow/release-controller-config 75a6fa9 link true /test release-controller-config

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

@travier
Copy link
Copy Markdown
Member

travier commented Jun 30, 2022

This one is replaced by either #29949 or #29964
/close

@openshift-ci openshift-ci Bot closed this Jun 30, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 30, 2022

@travier: Closed this PR.

Details

In response to this:

This one is replaced by either #29949 or #29964
/close

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.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants