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

USHIFT-5281: Include MicroShift RPMs from brew into S3 cache #60913

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

ggiguash
Copy link
Contributor

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 23, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 23, 2025

@ggiguash: This pull request references USHIFT-5281 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

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

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 23, 2025
Copy link
Contributor

openshift-ci bot commented Jan 23, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@ggiguash
Copy link
Contributor Author

/test ?

Copy link
Contributor

openshift-ci bot commented Jan 23, 2025

@ggiguash: The following commands are available to trigger required jobs:

/test app-ci-config-dry
/test boskos-config
/test boskos-config-generation
/test build01-dry
/test build02-dry
/test build03-dry
/test build04-dry
/test build05-dry
/test build06-dry
/test build09-dry
/test build10-dry
/test build11-dry
/test check-gh-automation
/test check-gh-automation-tide
/test ci-operator-config
/test ci-operator-config-metadata
/test ci-operator-registry
/test ci-secret-bootstrap-config-validation
/test ci-testgrid-allow-list
/test clusterimageset-validate
/test config
/test core-valid
/test generated-config
/test generated-dashboards
/test hosted-mgmt-dry
/test image-mirroring-config-validation
/test jira-lifecycle-config
/test openshift-image-mirror-mappings
/test ordered-prow-config
/test owners
/test pr-reminder-config
/test prow-config
/test prow-config-filenames
/test prow-config-semantics
/test pylint
/test release-config
/test release-controller-config
/test secret-generator-config-valid
/test services-valid
/test stackrox-stackrox-stackrox-stackrox-check
/test step-registry-metadata
/test step-registry-shellcheck
/test sync-rover-groups
/test vsphere02-dry
/test yamllint

The following commands are available to trigger optional jobs:

/test check-cluster-profiles-config

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-release-master-ci-operator-config
pull-ci-openshift-release-master-ci-operator-registry
pull-ci-openshift-release-master-core-valid
pull-ci-openshift-release-master-owners
pull-ci-openshift-release-master-release-controller-config
pull-ci-openshift-release-master-step-registry-metadata
pull-ci-openshift-release-master-step-registry-shellcheck
pull-ci-openshift-release-openshift-image-mirror-mappings
pull-ci-openshift-release-yamllint

In response to this:

/test ?

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.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 23, 2025
@ggiguash
Copy link
Contributor Author

/pj-rehearse ?

@openshift-ci-robot
Copy link
Contributor

@ggiguash: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@ggiguash
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-microshift-main-e2e-aws-tests-cache

@openshift-ci-robot
Copy link
Contributor

@ggiguash: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Contributor

@ggiguash: job(s): ? either don't exist or were not found to be affected, and cannot be rehearsed

@ggiguash
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-cache

@openshift-ci-robot
Copy link
Contributor

@ggiguash: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

Copy link
Contributor

openshift-ci bot commented Jan 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash

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

@pmtk
Copy link
Member

pmtk commented Jan 23, 2025

/pj-rehearse network-access-allowed

@openshift-ci-robot
Copy link
Contributor

@pmtk: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@ggiguash
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-cache

@openshift-ci-robot
Copy link
Contributor

@ggiguash: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@pacevedom
Copy link
Contributor

/pj-rehearse network-access-allowed

@openshift-ci-robot
Copy link
Contributor

@pacevedom: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@ggiguash
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-cache

@openshift-ci-robot
Copy link
Contributor

@ggiguash: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@ggiguash: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-microshift-main-e2e-aws-tests-cache openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-main-e2e-aws-tests-cache-arm openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-cache openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-cache-arm openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-cache openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-cache-arm openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.18-e2e-aws-tests-cache openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.18-e2e-aws-tests-cache-arm openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.17-microshift-metal-cache openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.17-microshift-metal-cache-arm openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-main-e2e-aws-tests openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-main-e2e-aws-tests-arm openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-main-e2e-aws-tests-periodic openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-main-e2e-aws-tests-periodic-arm openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-main-e2e-aws-tests-bootc openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-arm openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-periodic openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-periodic-arm openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.20-e2e-aws-tests openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-arm openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-periodic openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-periodic-arm openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-bootc openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-bootc-arm openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-bootc-periodic openshift/microshift presubmit Registry content changed

A total of 86 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
The following jobs are not rehearsable without the network-access-rehearsals-ok, and approved labels present on this PR. This is due to the restrict_network_access field being set to false. The network-access-rehearsals-ok label can be added by any openshift org member other than the PR's author by commenting: /pj-rehearse network-access-allowed:

Test name
periodic-ci-openshift-microshift-release-4.19-periodics-e2e-aws-tests-cache-nightly
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

Copy link
Contributor

openshift-ci bot commented Jan 23, 2025

@ggiguash: The following tests 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/rehearse/openshift/microshift/release-4.19/e2e-aws-tests-cache e29be5e link unknown /pj-rehearse pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-cache
ci/rehearse/openshift/microshift/main/e2e-aws-tests-cache 4e9f331 link unknown /pj-rehearse pull-ci-openshift-microshift-main-e2e-aws-tests-cache

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.

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/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. network-access-rehearsals-ok
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants