Description of problem:
Whenever adding new changes, the generate check fails because we have not run jb update.
Tested with 4.3.0-0.nightly-2020-02-09-195913, I see the fix is in the image, example
# oc -n openshift-monitoring get deploy prometheus-operator -oyaml
But I see in the prometheus-operator pod's log, the vesion is still 0.34.0, should it be 0.34.1?
# oc -n openshift-monitoring logs prometheus-operator-98d6fb856-99rsl | head
ts=2020-02-10T02:36:20.910391444Z caller=main.go:199 msg="Starting Prometheus Operator version '0.34.0'."
Since the issue in this bug is fixed, close it, if the report version is wrong, will file another bug
We will need a new bugzilla for that, as we want to port the fix to 4.3 as well. But thats separate from this, so new bugzilla is correct for 4.3 to have 0.34.1.
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.