openshift
Update the OLM note
TELCODOCS-1904: Update the OLM generic note. Update other SRIOV-specific info in related modules
Version(s): 4.13+
Issue: https://issues.redhat.com/browse/TELCODOCS-1904
Link to docs preview: https://81511--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/ztp-advanced-install-ztp.html#ztp-deleting-node-siteconfig_ztp-advanced-install-ztp
QE review:
- [ ] QE has approved this change.
🤖 Wed Aug 20 19:06:33 - Prow CI generated the docs preview:
https://84096--ocpdocs-pr.netlify.app/ https://84096--ocpdocs-pr.netlify.app/openshift-dedicated/latest/operators/admin/olm-deleting-operators-from-cluster.html https://84096--ocpdocs-pr.netlify.app/openshift-enterprise/latest/operators/admin/olm-deleting-operators-from-cluster.html https://84096--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/install/uninstalling-virt.html https://84096--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/operators/admin/olm-deleting-operators-from-cluster.html https://84096--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/virt/install/uninstalling-virt.html https://84096--ocpdocs-pr.netlify.app/openshift-rosa/latest/operators/admin/olm-deleting-operators-from-cluster.html https://84096--ocpdocs-pr.netlify.app/openshift-rosa/latest/virt/install/uninstalling-virt.html
Hi @adellape, requesting your review on this one since it affects the generic OLM note. This change is a requested as a result of a customer case that i have linked in the comment zero.
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
The branch/enterprise-4.19 label has been added to this PR.
This is because your PR targets the main branch and is labeled for enterprise-4.18. And any PR going into main must also target the latest version branch (enterprise-4.19).
If the update in your PR does NOT apply to version 4.19 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.
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
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.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@abhatt-rh: 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-sigs/prow repository. I understand the commands that are listed here.
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.