The DNS Operator's TestCoreDNSImageUpgrade test currently relies on modifying the DNS operator's deployment. Any changes made to this deployment are immediately overwritten by the CVO. PR 226 skips this test. The test should be re-worked so that either the clusterversion elements are overridden safely, or so that the scope of the test is appropriately limited.
Prior to PR 226, the TestCoreDNSImageUpgrade tests did not properly verify that CoreDNS image changes were effectively rolled out to all DNS pods. Rather, TestCoreDNSImageUpgrade simply checked for at least 1 DNS pod definition with the newly applied image, which is a defect. Upon enhancing the test to verify that all pods in the DNS daemonset update to the correct image, we noticed that the CVO interacts with the fundamental intent of this test.
didn't see the error in e2e test and moving 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.