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.
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:
When this yaml is applied in the next step the operator cannot be installed and following error is later found:
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:
where
:HCOVersion:is defined in _attributes/common-attributes.adoc#L107.Leaving
startingCSVcompletely 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.