openshift-docs
openshift-docs copied to clipboard
OSDOCS-3386: Y-stream manual | Z-stream opt documentation updates
Version(s): 4.13+
Issue: https://issues.redhat.com/browse/OSDOCS-3386
Link to docs preview: Preparing for 4.12: https://60917--docspreview.netlify.app/openshift-rosa/latest/upgrading/rosa-updating-cluster-prepare-4-12.html Preparing for 4.13: https://60917--docspreview.netlify.app/openshift-rosa/latest/upgrading/rosa-updating-cluster-prepare-4-13.html Updating ROSA Classic: https://60917--docspreview.netlify.app/openshift-rosa/latest/upgrading/rosa-upgrading-sts.html
QE review:
- [ ] QE has approved this change.
Additional information:
@bmcelvee: This pull request references OSDOCS-3386 which is a valid jira issue.
In response to this:
Version(s): 4.13+
Issue: https://issues.redhat.com/browse/OSDOCS-3386
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Additional information:
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.
@bmcelvee: This pull request references OSDOCS-3386 which is a valid jira issue.
In response to this:
Version(s): 4.13+
Issue: https://issues.redhat.com/browse/OSDOCS-3386
Link to docs preview: Will provide preview when the new assemblies are in place. The missing assemblies are causing the checks to fail.
QE review:
- [ ] QE has approved this change.
Additional information:
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.
🤖 Updated build preview is available at: https://60917--docspreview.netlify.app
Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/20302
@bmcelvee: This pull request references OSDOCS-3386 which is a valid jira issue.
In response to this:
Version(s): 4.13+
Issue: https://issues.redhat.com/browse/OSDOCS-3386
Link to docs preview: Preparing for 4.12: https://60917--docspreview.netlify.app/openshift-rosa/latest/upgrading/rosa-updating-cluster-prepare-4-12.html Preparing for 4.13: https://60917--docspreview.netlify.app/openshift-rosa/latest/upgrading/rosa-updating-cluster-prepare-4-13.html
QE review:
- [ ] QE has approved this change.
Additional information:
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.
@bmcelvee: This pull request references OSDOCS-3386 which is a valid jira issue.
In response to this:
Version(s): 4.13+
Issue: https://issues.redhat.com/browse/OSDOCS-3386
Link to docs preview: Preparing for 4.12: https://60917--docspreview.netlify.app/openshift-rosa/latest/upgrading/rosa-updating-cluster-prepare-4-12.html Preparing for 4.13: https://60917--docspreview.netlify.app/openshift-rosa/latest/upgrading/rosa-updating-cluster-prepare-4-13.html Updating ROSA Classic: https://60917--docspreview.netlify.app/openshift-rosa/latest/upgrading/rosa-upgrading-sts.html
QE review:
- [ ] QE has approved this change.
Additional information:
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.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
@bmcelvee: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/validate-asciidoc | d43f27b777cf5c03aa03cd04ac862ba51e282dae | link | true | /test validate-asciidoc |
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.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
PR needs rebase.
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.
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
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.