Bug 1737780
| Summary: | [sriov] DaemonSet did not be sync after updated the image of csv | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | zhaozhanqi <zzhao> | ||||
| Component: | Networking | Assignee: | Peng Liu <pliu> | ||||
| Status: | CLOSED ERRATA | QA Contact: | zhaozhanqi <zzhao> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.2.0 | CC: | aos-bugs, nagrawal, piqin | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.2.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-10-16 06:34:48 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Verified this bug on quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908192219-ose-sriov-network-operator 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-2019:2922 |
Created attachment 1600897 [details] sriov-operator logs Description of problem: After I updated all images in the csv. The sriov-operator can be updated using the correct image and pod will be recreate. After a while. Find the image in the DaemonSet sriov-network-config-daemon/sriov-device-plugin/sriov-cni did not be updated. Version-Release number of selected component (if applicable): quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908051019-ose-sriov-network-operator How reproducible: alwyas Steps to Reproduce: 1. install the sriov operator 2. Create the SriovNetworkNodePolicy CR 3. Check sriov-cni and dp pod will be running 4. update the image of csv 5. After a while. check all images in ds 6. Check the sriov-operator logs Actual results: 5. DaemonSet sriov-network-config-daemon/sriov-device-plugin/sriov-cni did not be updated Expected results: All images should be updated. Additional info: