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

OCPBUGS-31290: Dockerfile should keep prior rhel8 behavior for ccoctl default #694

Merged
merged 1 commit into from Apr 22, 2024

Conversation

jstuever
Copy link
Contributor

Previously we updated the Dockerfile to default to RHEL9 ccoctl binary. However, in order to remain consistent with prior behavior, we should instead default to the RHEL8 binary.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 19, 2024
@openshift-ci-robot
Copy link
Contributor

@jstuever: This pull request references Jira Issue OCPBUGS-31290, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Previously we updated the Dockerfile to default to RHEL9 ccoctl binary. However, in order to remain consistent with prior behavior, we should instead default to the RHEL8 binary.

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 openshift-eng/jira-lifecycle-plugin repository.

@jstuever
Copy link
Contributor Author

/test e2e-aws-manual-oidc e2e-azure-manual-oidc e2e-gcp-manual-oidc

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 19, 2024
@jstuever
Copy link
Contributor Author

/jira refresh
/override ci/prow/security

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Apr 19, 2024
@openshift-ci-robot
Copy link
Contributor

@jstuever: This pull request references Jira Issue OCPBUGS-31290, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jianping-shu

In response to this:

/jira refresh
/override ci/prow/security

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 19, 2024
Copy link
Contributor

openshift-ci bot commented Apr 19, 2024

@jstuever: Overrode contexts on behalf of jstuever: ci/prow/security

In response to this:

/jira refresh
/override ci/prow/security

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.

Copy link
Contributor

openshift-ci bot commented Apr 19, 2024

@jstuever: all tests passed!

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.

@jianping-shu
Copy link

Verified with cluster-bot build and AWS STS flexy template.
ccoctl ran on rhel8 agent and AWS STS cluster installed successfully.

https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/Flexy-install/278060/consoleFull
04-22 08:41:37.362 Running Command: ./ccoctl aws create-all --name='jshu22-22582' --region='us-east-2' --credentials-requests-dir='/home/jenkins/ws/workspace/ocp-common/Flexy-install/flexy/workdir/install-dir/pre_action/sts/creds' --output-dir '/home/jenkins/ws/workspace/ocp-common/Flexy-install/flexy/workdir/install-dir/pre_action/sts' 04-22 08:41:37.363 2024/04/22 00:41:36 Generating RSA keypair 04-22 08:41:39.250 2024/04/22 00:41:38 Writing private key to /home/jenkins/ws/workspace/ocp-common/Flexy-install/flexy/workdir/install-dir/pre_action/sts/serviceaccount-signer.private

@joepvd
Copy link

joepvd commented Apr 22, 2024

Hmm this basically makes a rhel8 compiled ccoctl running in a rhel9 container. I think this does not give runtime errors, but should not be intended.

@jstuever
Copy link
Contributor Author

Hmm this basically makes a rhel8 compiled ccoctl running in a rhel9 container. I think this does not give runtime errors, but should not be intended.

ccoctl does not run in cluster, it is intended to be downloaded by the end user and executed on their workstation.

@jstuever
Copy link
Contributor Author

/assign @dlom
We may also need to update the CI jobs to pick the right binary based on the container.

@dlom
Copy link
Contributor

dlom commented Apr 22, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 22, 2024
Copy link
Contributor

openshift-ci bot commented Apr 22, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dlom, jstuever

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-merge-bot openshift-merge-bot bot merged commit 6fe4910 into openshift:master Apr 22, 2024
12 checks passed
@openshift-ci-robot
Copy link
Contributor

@jstuever: Jira Issue OCPBUGS-31290: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-31290 has been moved to the MODIFIED state.

In response to this:

Previously we updated the Dockerfile to default to RHEL9 ccoctl binary. However, in order to remain consistent with prior behavior, we should instead default to the RHEL8 binary.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cloud-credential-operator-container-v4.16.0-202404222343.p0.g6fe4910.assembly.stream.el9 for distgit ose-cloud-credential-operator.
All builds following this will include this PR.

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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants