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

OKD: fix entrypoint.sh for new SCOS builds #322

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

bernhardloos
Copy link

Builds of OKD starting with 4.16 are based on CentOS Stream but the images identify as centos in /etc/os-release:

NAME="CentOS Stream"
VERSION="9"
ID="centos"
VERSION_ID="9"

See also okd-project/okd#2060

Builds of OKD starting with 4.16 are based on CentOS Stream but the images identify as centos in /etc/os-release:
NAME="CentOS Stream"
VERSION="9"
ID="centos"
VERSION_ID="9"

See also okd-project/okd#2060
@openshift-ci openshift-ci bot requested review from pliurh and s1061123 December 12, 2024 20:24
Copy link
Contributor

openshift-ci bot commented Dec 12, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bernhardloos
Once this PR has been reviewed and has the lgtm label, please assign s1061123 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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 needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Dec 12, 2024
Copy link
Contributor

openshift-ci bot commented Dec 12, 2024

Hi @bernhardloos. Thanks for your PR.

I'm waiting for a openshift 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.

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.

@GingerGeek
Copy link

We are tracking this in OKD as okd-project/okd#2070

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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