Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release-controller: Treat rhel-coreos-8 the same as machine-os-content #31083

Closed

Conversation

cgwalters
Copy link
Member

The former is going to replace the latter. See
https://github.com/openshift/enhancements/blob/master/enhancements/ocp-coreos-layering.md

I'm hoping this is somehow what's necessary to have the image
that is now built by ART included in the CI payload, so that
we can get this PR to work:

openshift/machine-config-operator#3258 (comment)

…tent`

The former is going to replace the latter.  See
https://github.com/openshift/enhancements/blob/master/enhancements/ocp-coreos-layering.md

I'm *hoping* this is somehow what's necessary to have the image
that is now built by ART included in the CI payload, so that
we can get this PR to work:

openshift/machine-config-operator#3258 (comment)
@LorbusChris
Copy link
Member

I don't think this change will do what you're actually trying to achieve, but it still LGTM, as we don't want to mirror the rhel oscontainer from the ocp namespace to the origin ns (we'll obviously want to build FCOS/SCOS oscontainers directly to the origin ns as replacements instead).

From my admittedly limited understanding of the Prow CI release controller, the rhel-coreos-8 image would have to be part of the 4.12 imagestream, i.e. be named 4.12:rhel-coreos-8, for automatic inclusion in 4.12 CI releases.

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 4, 2022
@cgwalters
Copy link
Member Author

cgwalters commented Aug 5, 2022

Yeah, thanks I think you're right! Clearly this whole thing raises the issue of whether ci uses fcos/scos9 but I don't think we can pull the trigger on that right now (unless we add scos8, but even then).

@LorbusChris
Copy link
Member

LorbusChris commented Aug 24, 2022

Let's get this in.

/assign @bradmwilliams

Could you take a look?

Edit: @cgwalters re the question whether fcos or scos is used in OKD CI: FCOS for now, but we'll soon rename the okd variant to okd-fcos, and introduce an additional okd-scos variant (plus the required changes to have release controller do two distinct releases, one for FCOS, and one for SCOS, and dupe the CI so we get all we have for okd today for both fcos/scos in the future)

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 24, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bradmwilliams, cgwalters, LorbusChris

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:

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 Aug 24, 2022
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 2 against base HEAD 3904cfa and 8 for PR HEAD 0f66edf in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 1 against base HEAD 3904cfa and 7 for PR HEAD 0f66edf in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 3904cfa and 6 for PR HEAD 0f66edf in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 2 against base HEAD 529559f and 5 for PR HEAD 0f66edf in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 2 against base HEAD 526a41d and 4 for PR HEAD 0f66edf in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 1 against base HEAD 526a41d and 3 for PR HEAD 0f66edf in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 2 against base HEAD c98c26f and 2 for PR HEAD 0f66edf in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 2 against base HEAD 58eecab and 1 for PR HEAD 0f66edf in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 2 against base HEAD 9d3451e and 0 for PR HEAD 0f66edf in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 25, 2022

@cgwalters: 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/openshift-image-mirror-mappings 0f66edf link true /test openshift-image-mirror-mappings

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
Copy link
Contributor

/hold

Revision 0f66edf was retested 9 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 25, 2022
@LorbusChris
Copy link
Member

@cgwalters this change requires an update to the mapping file: make openshift-image-mirror-mappings

@LorbusChris
Copy link
Member

I'm folding this into #31663

/close

@openshift-ci openshift-ci bot closed this Aug 31, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 31, 2022

@LorbusChris: Closed this PR.

In response to this:

I'm folding this into #31663

/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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants