-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add optional CI jobs for testing Compliance Operator on ARM64 #61066
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhmdnd 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 |
/pj-rehearse pull-ci-ComplianceAsCode-compliance-operator-master-e2e-aws-parallel-arm |
@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
@rhmdnd: requesting more than one rehearsal in one comment is not supported. If you would like to rehearse multiple specific jobs, please separate the job names by a space in a single command. |
/pj-rehearse pull-ci-ComplianceAsCode-compliance-operator-master-e2e-aws-parallel-arm pull-ci-ComplianceAsCode-compliance-operator-master-e2e-aws-serial-arm |
@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse |
@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse |
@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Deployment failed to come up - which could be symptomatic of architecture issues:
|
Marked these ARM jobs as optional so we can land this PR and start getting them to pass with changes to the ComplianceAaCode/compliance-operator. |
/pj-rehearse ack @Vincent056 should be ready for a look. |
@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse pull-ci-ComplianceAsCode-compliance-operator-master-e2e-aws-parallel-arm |
@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
@rhmdnd: requesting more than one rehearsal in one comment is not supported. If you would like to rehearse multiple specific jobs, please separate the job names by a space in a single command. |
The `ipi-aws` workflow allows us to request ARM64 architecture for the control plane and worker nodes. Let's use it so we can start building out CI for the Compliance Operator on ARM64. This job is optional for now until we smooth out failures in the compliance operator running on ARM. Once we have stable jobs, we'll make this a required.
/pj-rehearse pull-ci-ComplianceAsCode-compliance-operator-master-e2e-aws-parallel-arm pull-ci-ComplianceAsCode-compliance-operator-master-e2e-aws-serial-arm |
@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
@rhmdnd: The following tests failed, say
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-sigs/prow repository. I understand the commands that are listed here. |
This makes it so the container image we use for testing is build for arm64 architecture in addition to Power/Z/AMD64. This will get used in CI testing the Compliance Operatoron ARM: openshift/release#61066
Seeing failures because the profile bundles aren't parsing, which could be due to content images not being built for arm64.
Proposed ComplianceAsCode/content#12964 to start building the content for arm64. Once that lands we can try rekicking the rehearsal jobs. |
The
ipi-aws
workflow allows us to request ARM64 architecture for thecontrol plane and worker nodes. Let's use it so we can start building
out CI for the Compliance Operator on ARM64.
This job is optional for now until we smooth out failures in the
compliance operator running on ARM. Once we have stable jobs, we'll make
this a required.