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
STOR-1713:Restore Dockerfile for azure-disk operator #47498
STOR-1713:Restore Dockerfile for azure-disk operator #47498
Conversation
@gnufied: This pull request references STOR-1713 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.16.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. |
[REHEARSALNOTIFIER]
A total of 30 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 Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dobsonj, gnufied 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 |
@gnufied: 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/test-infra repository. I understand the commands that are listed here. |
/pj-rehearse ack |
This restores changes done via https://github.com/openshift/release/pull/47448/files#diff-d3c90828d0b4a3954ff9498d3c2196b600508244ece93a922fd3f8df79cc38fd
I assume we were unforunate that our changes to ocp-build-data is not merged yet. Once everything is merged, this should not happen again.