openshift/os: start building scos node images#62296
Conversation
|
/hold |
|
depends on openshift/os#1757 |
|
/pj-rehearse pull-ci-openshift-os-master-okd-scos-images |
|
@Prashanth684: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-os-master-okd-scos-images |
|
@Prashanth684: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-os-master-images |
|
@Prashanth684: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@Prashanth684: job(s): pull-ci-openshift-os-master-images either don't exist or were not found to be affected, and cannot be rehearsed |
…xtensions container for scos This PR: openshift/release#62296 now builds scos images. The extensions image build hit this error: ``` INFO: Neutering RHEL repos for SCOS centos-stream-release-9.0-26.el9.noarch package centos-release-cloud is not installed Updating Subscription Management repositories. Unable to read consumer identity This system is not registered with an entitlement server. You can use subscription-manager to register. Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d". ``` This is because the centos-release* repos are not installed in the base image as we clean them up and remove the repo file. We need to copy it gain to /etc/yum.repos.d so these repos can be re-installed
| - registry.access.redhat.com/ubi9/ubi:latest | ||
| stream-coreos: | ||
| as: | ||
| - registry.ci.openshift.org/rhcos-devel/rhel-coreos:latest |
There was a problem hiding this comment.
this will build the okd node image on top of rhel-coreos, which is unwanted.
We should use the c9s base image but we don't publish it to registry.ci as of now.
We can change that though
There was a problem hiding this comment.
AIUI according to https://docs.ci.openshift.org/docs/architecture/images/#ci-images, the extensions will be built on top of the previously built stream-coreos image which is substituted for the registry.ci.openshift.org/rhcos-devel/rhel-coreos:latest. This is similar to what is done for rhel-coreos
There was a problem hiding this comment.
@jbtrystram this is now ready to go. Do you have any other concerns before approval?
There was a problem hiding this comment.
this will build the okd node image on top of rhel-coreos, which is unwanted.
The default in the Containerfile of the os repo is a c9s base image (quay.io/openshift-release-dev/ocp-v4.0-art-dev:c9s-coreos) - and that is used to build the stream-coreos image which is then used to build the extensions. hope this makes it clear.
There was a problem hiding this comment.
We should probably use the same default in both TBH, but no need to block on that.
…xtensions container for scos This PR: openshift/release#62296 now builds scos images. The extensions image build hit this error: ``` INFO: Neutering RHEL repos for SCOS centos-stream-release-9.0-26.el9.noarch package centos-release-cloud is not installed Updating Subscription Management repositories. Unable to read consumer identity This system is not registered with an entitlement server. You can use subscription-manager to register. Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d". ``` This is because the centos-release* repos are not installed in the base image as we clean them up and remove the repo file. We need to copy it gain to /etc/yum.repos.d so these repos can be re-installed
This PR: openshift/release#62296 now builds scos images. The extensions image build hit this error: ``` INFO: Neutering RHEL repos for SCOS centos-stream-release-9.0-26.el9.noarch package centos-release-cloud is not installed Updating Subscription Management repositories. Unable to read consumer identity This system is not registered with an entitlement server. You can use subscription-manager to register. Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d". ``` This is because the centos-release* repos are disabled in the node image which is used for building extensions
|
/pj-rehearse pull-ci-openshift-os-master-okd-scos-images |
|
@Prashanth684: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-os-master-okd-scos-images |
|
@Prashanth684: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-os-master-okd-scos-e2e-aws-ovn |
|
@Prashanth684: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/hold cancel |
|
/cc @jlebon |
| - registry.access.redhat.com/ubi9/ubi:latest | ||
| stream-coreos: | ||
| as: | ||
| - registry.ci.openshift.org/rhcos-devel/rhel-coreos:latest |
There was a problem hiding this comment.
We should probably use the same default in both TBH, but no need to block on that.
|
/approve |
- build the stream-coreos and stream-coreos-extensions images which is used in OKD releases - promote these images to the scos imagestream as they will be used as the node images going forward in favour of the m-o-c pipeline
|
@Prashanth684: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse ack |
|
@Prashanth684: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ausil, jlebon, jupierce, Prashanth684 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@Prashanth684: Updated the
DetailsIn response to this:
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. |
…mTag Now that we have images being generated through openshift#62296, we no longer need this
…mTag Now that we have images being generated through openshift#62296, we no longer need this
Uh oh!
There was an error while loading. Please reload this page.