Closed scrool closed 1 month 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
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: Closing this issue.
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
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.