Tweak the cluster operator obj messages per updates to the doc in the summary
See https://github.com/openshift/cluster-samples-operator/pull/70#discussion_r244821629 for probably changes
Also, in reading the new https://github.com/openshift/cluster-version-operator/blob/master/docs/dev/clusteroperator.md#conditions
It has: "If an error blocks reaching 4.0.1, the conditions might be ..... Progressing is true with message Unable to apply 4.0.1: a required object is missing"
That also lines up with my read of the godoc that we added as a reference.
That will require a tweak to the current logic as well.
PR https://github.com/openshift/cluster-samples-operator/pull/76 is up
PR has merged
@XiuJuan Wang - I updated the QE card for this space, https://jira.coreos.com/browse/DEVEXP-175 .... given the churn we've
had on the dev side since you first were asked to test this, we need to update the test cases.
Hopefully in re-reviewing those, I can answer any clarification question you may have wrt https://github.com/openshift/cluster-version-operator/blob/master/docs/dev/clusteroperator.md#conditions
and what I did for the samples operator around https://github.com/openshift/cluster-samples-operator/pull/76
This change works well with 4.0.0-0.alpha-2019-01-20-082408
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.