-
Bug
-
Resolution: Done
-
Major
-
None
-
OSSM 2.0.0, OSSM 2.1.0
-
None
-
5
-
False
-
False
-
Undefined
-
Details in BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1911602
[Document URL]
https://docs.openshift.com/container-platform/4.6/service_mesh/v1x/installing-ossm.html#ossm-control-plane-deploy-cli_installing-ossm-v1x
[Section Number and Name]
Deploying the control plane from the CLI
[Describe the issue]
- Errata 1:
It's possible to read:
"The installation has finished successfully when the STATUS column is InstallSuccessful."
As it's possible to read from one deployed service mesh in 4.6, it's not "InstallSuccessful", it's ComponentsReady the value of the STATUS field.
~~~
{{ $ oc get smcp -n istio-system}}
{{ NAME READY STATUS PROFILES VERSION AGE}}
{{ basic 9/9 ComponentsReady ["default"] 2.0.1 40h}}
{{ ~~~}}
- Errata 2
In the output of the command "of get smcp -n istion-system" the version used is v1.1. When you deploy it by default, the version is 2.0.1.
Then, I'd suggest o update the output from:
~~~
{{ NAME READY STATUS TEMPLATE VERSION AGE}}
{{ basic-install 9/9 InstallSuccessful default v1.1 4m25s}}
{{ ~~~}}
To:
~~~
NAME READY STATUS PROFILES VERSION AGE
basic 9/9 ComponentsReady ["default"] 2.0.1 40h
~~~
Where it's possible to see that some fields are changed:
- STATUS, it's not more InstallSuccessful and it's ComponentsReady
- The TEMPLATE field has been replaces by the PROFILES field
- The version is different