search

openshift / openshift-docs

OpenShift 3 and 4 product and community documentation
https://docs.openshift.com
Apache License 2.0
764 stars 1.76k forks source link

Uninstalling OKD Virtualization by using the CLI refers to wrong subscription name #74928

Closed scrool closed 1 month ago

scrool commented 6 months ago

Which section(s) is the issue in?

Uninstalling OKD Virtualization by using the CLI or Subscribing to the OKD Virtualization catalog by using the CLI

What needs fixing?

Following the second point of the procedure:

$ oc delete subscription kubevirt-hyperconverged -n kubevirt-hyperconverged

fails with an error:

Error from server (NotFound): hyperconvergeds.hco.kubevirt.io "kubevirt-hyperconverged" not found

Because the subscription created during the installation is called "hco-operatorhub":

$ oc get subscription -n kubevirt-hyperconverged
NAMESPACE                 NAME              PACKAGE                             SOURCE                CHANNEL
kubevirt-hyperconverged   hco-operatorhub   community-kubevirt-hyperconverged   community-operators   stable

While the obvious way would be to replace "kubevirt-hyperconverged" with "hco-operatorhub" in the uninstall section, because of the commit https://github.com/openshift/openshift-docs/commit/6f7483a1db5fbfc0e23e93631106d3d77434c4d3 Change hco to hyperconverged, the installation section might need to be updated instead to hyperconverged-operatorhub.

I'm not sure what is the more preferred way.

openshift-bot commented 3 months ago

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

openshift-bot commented 2 months ago

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

openshift-bot commented 1 month ago

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-ci[bot] commented 1 month ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/openshift-docs/issues/74928#issuecomment-2382385595): >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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.