Per recent upgrade experience in openshift/starter while samples operator was unmanaged NOTE: workaround in the interim is the add the openshift-samples ClusterOperator obj into the clusterversion overrides list
PR https://github.com/openshift/cluster-samples-operator/pull/151 is up
PR has merged into master for 4.2
Set samples operator to 'Unmanaged' then upgrade 4.2.0-0.ci-2019-06-03-105723 to 4.2.0-0.ci-2019-06-11-224610 After upgrade successfully, the managed imagestreams are still 4.2.0-0.ci-2019-06-03-105723, that's correct. But crd version and openshift-samples clusteroperator version have been upgrade to 4.2.0-0.ci-2019-06-11-224610 $ oc describe is -n openshift | grep "4.2.0-0.ci-2019-06-11-224610" (return null) $oc get config.samples.operator -o yaml | grep version -B 1 managementState: Unmanaged version: 4.2.0-0.ci-2019-06-11-224610 $oc describe clusteroperator openshift-samples Status: Conditions: Last Transition Time: 2019-06-12T10:55:58Z Message: Samples installation successful at 4.2.0-0.ci-2019-06-11-224610 Status: True Type: Available Last Transition Time: 2019-06-12T10:55:59Z Message: Samples installation successful at 4.2.0-0.ci-2019-06-11-224610 Status: False Type: Progressing Last Transition Time: 2019-06-12T08:35:05Z Status: False Type: Degraded Extension: <nil> Related Objects: Group: samples.operator.openshift.io Name: cluster Resource: configs Group: Name: openshift-cluster-samples-operator Resource: namespaces Group: Name: openshift Resource: namespaces Versions: Name: operator Version: 4.2.0-0.ci-2019-06-11-224610
Changing the version to the latest is part of what this fix is about. Version: 4.2.0-0.ci-2019-06-11-224610 in the config CRD and cluster operator is correct You've verified this fix.
Thanks Gabe~ Add removed status upgrade scenario. Imagestream under managed are removed.And openshift-samples clusteroperator version and crd version are latest. Also Available = true. Move this to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922