Did you set the `openshift_web_console_version` inventory var? It defaults to v3.9, so you might get a different version unless specify v3.9.0-0.33.0.
We're looking at changing how the prefix and version get set for the console in 3.10, but you need to set the variable for now, similar to metrics and logging.
I didn't set "openshift_web_console_version" in previous env installation. After I set "openshift_web_console_version = v3.9.0-0.33.0" in a new installation, the web console version is the defined "v3.9.0-0.33.0".
Now that the change is planed in 3.10, I'd like to change the target release to 3.10. Pls modify if it's not correct.
Changing priority to low since this is working as intended. It's reasonable to be able to set the version in one place for installs, however, and I know Scott has mentioned that as a goal. Scott, let me know if you have something tracking that already.
Tested with openshift-ansible-3.10.0-0.46.0.git.0.85c3afd.el7.noarch.rpm
Now install env without set `openshift_web_console_version` inventory var, master and web console pod will use image with v3.10 tag by default.
registry.reg-aws.openshift.com:443/openshift3/ose-control-plane v3.10 35628f394eff 32 hours ago 634 MB
registry.reg-aws.openshift.com:443/openshift3/ose-web-console v3.10 615eec2b9949 32 hours ago 318 MB
OpenShift Web Console:
The master version and web console version are consistent now.
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.