search

openshift / openshift-docs

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

Yaml to subscribe to the OKD Virtualization catalog by using the CLI refers to non-existent kubevirt-hyperconverged-operator #74927

Closed scrool closed 2 months ago

scrool commented 7 months ago

Which section(s) is the issue in?

Subscribing to the OKD Virtualization catalog by using the CLI

What needs fixing?

YAML file in the sections ends with:

spec:
  source: redhat-operators
  sourceNamespace: openshift-marketplace
  name: kubevirt-hyperconverged
  startingCSV: kubevirt-hyperconverged-operator.v4.15.1
  channel: "stable"

When this yaml is applied in the next step the operator cannot be installed and following error is later found:

constraints not satisfiable: no operators found with name kubevirt-hyperconverged-operator.v4.15.1 in channel stable of package community-kubevirt-hyperconverged in the catalog referenced by subscription hco-operatorhub, subscription hco-operatorhub exists

The reason is that the latest operator at the time of writing is 1.10.1.

The version "v4.14.1" comes from the source modules/virt-subscribing-cli.adoc#L48:

  startingCSV: kubevirt-hyperconverged-operator.v{HCOVersion}

where :HCOVersion: is defined in _attributes/common-attributes.adoc#L107.

Leaving startingCSV completely fixes this but I'm not sure if that's desired/recommended way to install the operator - to completely skip version specification. Alternatively this could contain a note to update the version to the latest/compatible for the current OKD version.

In the Verification subsection there is an output of successful deployment which also refers to the same values as above.

openshift-bot commented 4 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 3 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 2 months 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 2 months ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/openshift-docs/issues/74927#issuecomment-2362415824): >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.