[OKD] Uninstalling OKD Virtualization by using the CLI refers to wrong subscription name

[scrool]

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 6f7483a 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]

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]

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]

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]

@openshift-bot: Closing this issue.

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.

[mburke5678]

/reopen

[openshift-ci]

@mburke5678: Reopened this issue.

In response to this:

/reopen

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-bot]

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