The `openshift-tests run-resourcewatch` command, which provides a monitor that logs config changes to a git repository, needs to be added to the 4.4 openshift-tests binary in order to be able to run on upgrade tests.
Moving to unknown component, this is not under purview of DPTP.
Moved to kcm component. It's also not quite right, but at least the BZ does not land on a board of another team ;-)
Confirmed with payload: 4.4.0-0.nightly-2020-06-27-171816, the issue has fixed: [root@dhcp-140-138 ~]# oc get is tests -n openshift -o yaml dockerImageReference: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a91fdc7898fe2f830a5640188a207d5489eac5694d496626b91b0aea6d3ee98e [root@dhcp-140-138 ~]# oc run mytest --image=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a91fdc7898fe2f830a5640188a207d5489eac5694d496626b91b0aea6d3ee98e --command -- sleep 3600 [root@dhcp-140-138 ~]# oc get po NAME READY STATUS RESTARTS AGE mytest-1-46f9w 1/1 Running 0 5s mytest-1-deploy 0/1 Completed 0 8s [root@dhcp-140-138 ~]# oc rsh mytest-1-46f9w sh-4.2$ openshift-tests -h .... Available Commands: help Help about any command run Run a test suite run-monitor Continuously verify the cluster is functional run-resourcewatch Run watching resource changes run-test Run a single test by name run-upgrade Run an upgrade suite sh-4.2$ openshift-tests run-resourcewatch W0628 03:20:16.931761 21 cmd.go:199] Using insecure, self-signed certificates I0628 03:20:17.526670 21 observer_polling.go:159] Starting file observer ....
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-2020:2786