Skip to content

OADP 1.1.2 Release notes#56940

Merged
mjpytlak merged 1 commit intoopenshift:mainfrom
sbeskin-redhat:OADP_1215_OADP_1_1_2_release_notes
Mar 9, 2023
Merged

OADP 1.1.2 Release notes#56940
mjpytlak merged 1 commit intoopenshift:mainfrom
sbeskin-redhat:OADP_1215_OADP_1_1_2_release_notes

Conversation

@sbeskin-redhat
Copy link
Contributor

@sbeskin-redhat sbeskin-redhat commented Mar 8, 2023

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 8, 2023
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Mar 8, 2023

🤖 Updated build preview is available at:
https://56940--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/10763

@openshift-ci openshift-ci bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 8, 2023
@PrasadJoshi12
Copy link
Contributor

/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Mar 9, 2023

@PrasadJoshi12: changing LGTM is restricted to collaborators

Details

In response to this:

/lgtm

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.

@anarnold97
Copy link
Contributor

@weshayutin @kaovilai please can i ask for a dev check on this? thanks

@sbeskin-redhat
Copy link
Contributor Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Mar 9, 2023
@jeana-redhat jeana-redhat added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Mar 9, 2023
Copy link
Contributor

@jeana-redhat jeana-redhat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few small things


== Product recommendations

To prepare for the upgrade from VolSync 0.5.1 to 0.6.0, in the `openshift-adp` namespace you must add this annotation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To prepare for the upgrade from VolSync 0.5.1 to 0.6.0, in the `openshift-adp` namespace you must add this annotation.
To prepare for the upgrade from VolSync 0.5.1 to 0.6.0, you must add this annotation in the `openshift-adp` namespace by running the following command:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

change to the latest available volsync from the volsync stable channel.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@weshayutin
Like this?
"...the upgrade from VolSync 0.5.1 to the latest available volSync from the VolSync stable channel"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ya.. that's fine.. I want to make sure we're not suggesting 0.6.0 is the required version. 0.6.1 is going to be published in a few days.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

You can create many snapshots of the same persistent volume claim (PVC) but cannot schedule periodic creation of snapshots:
+
** For CephFS, you can create up to 100 snapshots per PVC.
** For RADOS Block Device (RBD), you can create up to 512 snapshots for each PVC. (link:https://issues.redhat.com/browse/OADP-804[*OADP-804*]) and (link:https://issues.redhat.com/browse/OADP-975[*OADP-975*])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do these linked issues apply to only this bullet?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Corrected

@jeana-redhat jeana-redhat added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR peer-review-needed Signifies that the peer review team needs to review this PR labels Mar 9, 2023
@weshayutin
Copy link

this is missing the comments I made in the jira ticket afaict.

We bumped the upstream releases
https://github.com/vmware-tanzu/velero/releases ( 1.9.2 >= 1.9.5 )
https://github.com/restic/restic/releases ( 0.13.1 >= 0.14.0 )

@weshayutin
Copy link

ha.. ya.. volsync 0.6.1 is production actually.. afaict now. lolz

@weshayutin
Copy link

specifying the version is silly.. it's more important to get the channel correct...

@sbeskin-redhat
Copy link
Contributor Author

sbeskin-redhat commented Mar 9, 2023

@weshayutin
These links lead to Velero 1.10.2 and Restic 0.15.1.
Also, does this mean that these versions should be used now? Now the Velero version that appears in the docs is 1.9. Should I change it to 1.9.5?

@weshayutin
Copy link

The specific link to the specific release would be great.. 0/

@sbeskin-redhat
Copy link
Contributor Author

@weshayutin
Please take a look.

@sbeskin-redhat
Copy link
Contributor Author

@jeana-redhat
I've made the corrections that you requested, but there have been some last-minute changes. Please take a look.

Copy link

@weshayutin weshayutin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks lgtm :)

Copy link
Contributor

@jeana-redhat jeana-redhat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updates LGTM, just need to squash your commits 👍

@sbeskin-redhat sbeskin-redhat force-pushed the OADP_1215_OADP_1_1_2_release_notes branch from c4d79ab to 97aaf58 Compare March 9, 2023 21:21
@sbeskin-redhat
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Mar 9, 2023
@mjpytlak mjpytlak added merge-review-in-progress Signifies that the merge review team is reviewing this PR branch/enterprise-4.9 branch/enterprise-4.10 branch/enterprise-4.11 branch/enterprise-4.12 branch/enterprise-4.13 and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Mar 9, 2023
@mjpytlak mjpytlak added this to the Continuous Release milestone Mar 9, 2023
@mjpytlak mjpytlak merged commit a8bc4a0 into openshift:main Mar 9, 2023
@mjpytlak
Copy link
Contributor

mjpytlak commented Mar 9, 2023

/cherrypick enterprise-4.13

@openshift-cherrypick-robot

@mjpytlak: new pull request created: #57034

Details

In response to this:

/cherrypick enterprise-4.13

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.

@mjpytlak
Copy link
Contributor

mjpytlak commented Mar 9, 2023

/cherrypick enterprise-4.12

@openshift-cherrypick-robot

@mjpytlak: new pull request created: #57035

Details

In response to this:

/cherrypick enterprise-4.12

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.

@mjpytlak
Copy link
Contributor

mjpytlak commented Mar 9, 2023

/cherrypick enterprise-4.11

@openshift-cherrypick-robot

@mjpytlak: new pull request created: #57036

Details

In response to this:

/cherrypick enterprise-4.11

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.

@mjpytlak
Copy link
Contributor

mjpytlak commented Mar 9, 2023

/cherrypick enterprise-4.10

@openshift-cherrypick-robot

@mjpytlak: new pull request created: #57037

Details

In response to this:

/cherrypick enterprise-4.10

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.

@mjpytlak
Copy link
Contributor

mjpytlak commented Mar 9, 2023

/cherrypick enterprise-4.9

@openshift-cherrypick-robot

@mjpytlak: new pull request created: #57038

Details

In response to this:

/cherrypick enterprise-4.9

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.9 branch/enterprise-4.10 branch/enterprise-4.11 branch/enterprise-4.12 branch/enterprise-4.13 merge-review-in-progress Signifies that the merge review team is reviewing this PR peer-review-done Signifies that the peer review team has reviewed this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants