BugZero updated this defect 38 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
4/11/2024
Integrated OpenStack
Integrated Openstack
7.x
No fixed releases provided.
The scheduled backup is failing with error messages: In rnb-controller log: rnb-controller-78f9dd7f9d-qwb2b rnb-controller time="2023-02-14T08:50:37Z" level=warning msg="failed retrieving backup state: no status found" In kubelet.log: Feb 15 04:57:26 photon-machine.local kubelet[32189]: E0215 04:57:26.225091 32189 pod_workers.go:191] Error syncing pod 5aacb74c-351d-44d5-9444-09fd829a2dc1 ("backup-backupschedule480-xqjfv7x545-1674777900-92gdf_openstack(5aacb74c-351d-44d5-9444-09fd829a2dc1)"), skipping: failed to "StartContainer" for "backupschedule480" with ImagePullBackOff: "Back-off pulling image \"docker-registry.default.svc.example.vio:5000/vmware/vio/cluster-controller:7.1.0.17987093\""
The old job/pod created based on the cronjob is using old image that is not current in the running system.The cronjob for the backupSchedule CR was created before VIO 7.2 patch.
Find cluster-controller image version on the running system. osctl describe pods -l app=vio-lcm-controllers,component=rnb_controller | grep IMAGE Edit the cronjob and change the image to the correct version. osctl edit cronjob Example: Replace image: docker-registry.default.svc.cluster.local:5000/vmware/vio/cluster-controller:7.1.0.17987093 with image: docker-registry.default.svc.cluster.local:5000/vmware/vio/cluster-controller:7.2.1.0.20003387 Delete old job running. osctl describe pod backup-backupschedule480-xqjfv7x545osctl describe pod backup-backupschedule480-xqjfv7x545 | grep job-nameosctl delete job backup-backupschedule-xxxxxx A new job with correct image tag would be created by the cronjob at the scheduled time.