OCPBUGS-25341,OCPBUGS-34173: [Manual] Synchronize From Upstream Repositories#795
OCPBUGS-25341,OCPBUGS-34173: [Manual] Synchronize From Upstream Repositories#795ankitathomas wants to merge 2 commits intoopenshift:masterfrom
Conversation
* fix sorting unpack jobs Signed-off-by: Ankita Thomas <ankithom@redhat.com> * Add test cases to reproduce panic Signed-off-by: Catherine Chan-Tse <cchantse@redhat.com> * handle nil jobs while sorting unpack jobs Signed-off-by: Ankita Thomas <ankithom@redhat.com> --------- Signed-off-by: Ankita Thomas <ankithom@redhat.com> Signed-off-by: Catherine Chan-Tse <cchantse@redhat.com> Co-authored-by: Catherine Chan-Tse <cchantse@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 20a3cbcde1f46ed7f4d56042ccc8b5d962e4d1b8
openshift-ci-robot
added
the
jira/valid-reference
|
@ankitathomas: This pull request explicitly references no jira issue. DetailsIn 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. |
ankitathomas
changed the title
openshift-ci-robot
added
the
jira/severity-important
|
@ankitathomas: This pull request references Jira Issue OCPBUGS-25341, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. This pull request references Jira Issue OCPBUGS-34173, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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-robot
added
the
jira/invalid-bug
openshift-ci
Bot
added
the
approved
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@ankitathomas: This pull request references Jira Issue OCPBUGS-25341, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request. This pull request references Jira Issue OCPBUGS-34173, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request. DetailsIn 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. |
…cks directly (#3217) * perform operator apiService certificate validity checks directly Signed-off-by: Ankita Thomas <ankithom@redhat.com> * use sets to track certs to install, revert to checking for installPlan timeouts after API availability checks, add service FQDN to list of hostnames. Signed-off-by: Ankita Thomas <ankithom@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 908da0c05363da40ad09ab774d9904b22aca7869 --------- Signed-off-by: Ankita Thomas <ankithom@redhat.com>
ankitathomas
force-pushed
the
sync-manual
branch
from
4a39888 to
0365511
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ankitathomas, grokspawn The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Closing in favor of #796 |
|
@ankitathomas: This pull request references Jira Issue OCPBUGS-25341. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state. This pull request references Jira Issue OCPBUGS-34173. The bug has been updated to no longer refer to the pull request using the external bug tracker. DetailsIn 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. |
3 participants
The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:
This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.
/cc @openshift/openshift-team-operator-runtime
/cc @openshift/openshift-team-operator-ecosystem