OCPBUGS-72511: Explicitly set the name of BSL#568
OCPBUGS-72511: Explicitly set the name of BSL#568sudomakeinstall2 wants to merge 1 commit intoopenshift-kni:mainfrom
Conversation
This commit explicitly sets the name of backupstoragelocation in DataProtectionApplication, and no longer rely only on the default behaviour. Also we make sure the backupstoragelocation status policy has a bigger ztp wave annotation number. This is because the status policy creates an empty backupstoragelocation, and with recent changes in oadp we are not allowed to set the default value for a backupstoragelocation after it has been already created. Signed-off-by: Saeid Askari <saskari@redhat.com>
|
@sudomakeinstall2: This pull request references Jira Issue OCPBUGS-72511, 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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: sudomakeinstall2 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/hold |
openshift-ci
bot
added
the
do-not-merge/hold
2 participants
This commit explicitly sets the name of backupstoragelocation in DataProtectionApplication, and no longer rely only on the default behaviour.
Also we make sure the backupstoragelocation status policy has a bigger ztp wave annotation number. This is because the status policy creates an empty backupstoragelocation, and with recent changes in oadp we are not allowed to set the default value for a backupstoragelocation after it has been already created.