OCPBUGS-72511: Explicitly set the name of BSL#568
OCPBUGS-72511: Explicitly set the name of BSL#568openshift-merge-bot[bot] merged 1 commit intoopenshift-kni:mainfrom
Conversation
|
@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. |
|
/hold |
openshift-ci
bot
added
the
do-not-merge/hold
sudomakeinstall2
force-pushed
the
OCPBUGS-72511
branch
from
cd2f8b4 to
c569d0a
Compare
...o-ran/configuration/argocd/example/acmpolicygenerator/acm-group-du-sno-validator-ranGen.yaml
Outdated
Show resolved
Hide resolved
|
/lgtm |
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 <[email protected]>
sudomakeinstall2
force-pushed
the
OCPBUGS-72511
branch
from
c569d0a to
d6be7dd
Compare
|
@sudomakeinstall2: This pull request references Jira Issue OCPBUGS-72511, which is invalid:
Comment 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. |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: irinamihai, sudomakeinstall2 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 |
openshift-ci
bot
added
the
approved
|
/unhold |
openshift-ci
bot
removed
the
do-not-merge/hold
|
@sudomakeinstall2: Jira Issue OCPBUGS-72511: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-72511 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/cherrypick release-4.21 |
|
/cherrypick release-4.20 |
|
@sudomakeinstall2: new pull request created: #620 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-sigs/prow repository. |
|
@sudomakeinstall2: new pull request created: #621 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-sigs/prow repository. |
6 participants
This commit explicitly sets the BackupStorageLocation name in the DataProtectionApplication rather than relying on the default behavior. Additionally, BackupStorageLocation status policy is added to valdiator policy. This change is necessary because the status policy creates an empty BackupStorageLocation, and recent OADP updates no longer allow setting a default value for a BackupStorageLocation after it has already been created.