OCPBUGS-4799: Fix label key truncation for subscription annotations (#2731)#421
Conversation
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com> Co-authored-by: Per Goncalves da Silva <pegoncal@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 1bdf969e6dff317e975de21078d60dd1406235e0
|
@grokspawn: This pull request references Jira Issue OCPBUGS-4799, 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 kubernetes/test-infra repository. |
|
@grokspawn: No Bugzilla bug is referenced in the title of this pull 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 kubernetes/test-infra repository. |
|
/lgtm |
|
/cherry-pick release-4.9 |
|
@grokspawn: once the present PR merges, I will cherry-pick it on top of release-4.9 in a new PR and assign it to you. 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 kubernetes/test-infra repository. |
|
/jira refresh |
|
@jianzhangbjz: This pull request references Jira Issue OCPBUGS-4799, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
Requesting review from QA contact: 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 kubernetes/test-infra repository. |
|
/retest-required |
|
/cherry-pick-approved |
|
/approve |
|
/label backport-risk-assessed |
|
@jianzhangbjz: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers] 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 kubernetes/test-infra repository. |
|
/retest-required |
|
/label backport-risk-assessed |
|
/label approved |
|
/retest-required |
bandrade
left a comment
There was a problem hiding this comment.
/label cherry-pick-approved
|
I guess it needs the |
|
/approve |
1 similar comment
|
/approve |
|
/label approved |
|
@perdasilva: Can not set label approved: Must be member in one of these teams: [openshift-release-oversight] 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 kubernetes/test-infra repository. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bandrade, grokspawn, jianzhangbjz, oceanc80, perdasilva 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 |
|
/retest-required |
It was strange that it retracted the approved label once Bruno applied the cherry-pick-approved label. Is that intentional? |
|
@grokspawn: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@grokspawn: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-4799 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
|
@grokspawn: new pull request created: #423 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 kubernetes/test-infra repository. |
…ft#421) Upstream-repository: api Upstream-commit: 436783bec2efadaeb51864c212923f8e226d21a3
…ft#421) Upstream-repository: api Upstream-commit: 436783bec2efadaeb51864c212923f8e226d21a3
…ft#421) Upstream-repository: api Upstream-commit: 436783bec2efadaeb51864c212923f8e226d21a3
…ft#421) Upstream-repository: api Upstream-commit: 436783bec2efadaeb51864c212923f8e226d21a3
Signed-off-by: Per Goncalves da Silva pegoncal@redhat.com
Co-authored-by: Per Goncalves da Silva pegoncal@redhat.com
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 1bdf969e6dff317e975de21078d60dd1406235e0