-
Notifications
You must be signed in to change notification settings - Fork 216
NO-ISSUE: rebase-main-4.19.0-0.nightly-2025-03-21-030708_amd64-2025-03-21_arm64-2025-03-22 #4721
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
NO-ISSUE: rebase-main-4.19.0-0.nightly-2025-03-21-030708_amd64-2025-03-21_arm64-2025-03-22 #4721
Conversation
@microshift-rebase-script[bot]: This pull request explicitly references no jira issue. 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. |
Extra messages:
|
The optional.Olm suite failed the setup phase because of an error creating the the catalogSource object. From the catalog operator logs (sos report):
var/log/pods/openshift-operator-lifecycle-manager_catalog-operator-b7db78d4b-dmxgl_1c651bbb-0c8d-4e38-86e6-28164c2b0c78/catalog-operator/0.log This error message usually indicates that the create call pushed an API definition that contains managed fields, and that the value of the field(s) differs from the server's. Since this catalogSource object is only created once, and only by the optional.Olm test, more investigation will be required. |
Giving the test one more chance as this may just be a transient error /retest |
@microshift-rebase-script[bot]: 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-sigs/prow repository. I understand the commands that are listed here. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: copejon, microshift-rebase-script[bot] 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 |
amd64: 4.19.0-0.nightly-2025-03-21-030708
arm64: 4.19.0-0.nightly-arm64-2025-03-22-080021
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1904020750948372480
api embedded-component 477760860ebdd921db389cf539439b0ec1064179 to 3aa9dd5b9002b370acc8ca4b4b041d682c22ca85
kubernetes embedded-component 2ed17b46fa89c438d5983268bdc352ba8bd9b4bb to 1601b9e27d8570364d9a1b94be16a0ca7b744a7e
OrderedNamespaceDeletion
for apiserver.oc image-amd64 fe18ae25a123e896fd218210073141f7f5811465 to 57018b1991282fd743495e240efe056f5f37be4a
kubernetes image-amd64 2ed17b46fa89c438d5983268bdc352ba8bd9b4bb to 1601b9e27d8570364d9a1b94be16a0ca7b744a7e
OrderedNamespaceDeletion
for apiserver.The change list was truncated. See scripts/auto-rebase/changelog.txt in the PR for the full details.
/label tide/merge-method-squash
/label cherry-pick-approved
/label backport-risk-assessed
/label jira/valid-bug