Bug 2050466
Summary: | machine config update with invalid container runtime config should be more robust | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Karthik Perumal <kramraja> |
Component: | Node | Assignee: | Qi Wang <qiwan> |
Node sub component: | Kubelet | QA Contact: | MinLi <minmli> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | urgent | ||
Priority: | medium | CC: | aos-bugs, cblecker, jerzhang, mkrejci, travi |
Version: | 4.9 | Keywords: | ServiceDeliveryBlocker |
Target Milestone: | --- | ||
Target Release: | 4.11.0 | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-08-10 10:47:09 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: |
Description
Karthik Perumal
2022-02-04 02:37:39 UTC
I'm not sure what degree of validation we would like to apply. Also consider that the MCO does similar things where you are able to break your nodes. > Also, is there a recommended approach to manually getting the machine config pool to point to a specific machine-config object so that SRE could potentially use it to fix such situations? See our debugging guide at https://docs.google.com/document/d/1fgP6Kv1D-75e1Ot0Kg-W2qPyxWDp2_CALltlBLuseec for some general cases and recommendations. It heavily depends on your scenario. Also passing this to the node team, as the node team owns the containerruntimecontroller/ICSP configuration. verified! % oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-0.nightly-2022-03-20-160505 True False 79m Cluster version is 4.11.0-0.nightly-2022-03-20-160505 After applying "invalid" ICMP to the cluster, it didn't generate any machine config. And there is error log which tip : invalid empty entry for mirror configuration. % oc logs -f machine-config-controller-b4b69f8b8-6zrh9 -n openshift-machine-config-operator ... I0321 03:30:39.037209 1 container_runtime_config_controller.go:363] Error syncing image config openshift-config: could not Create/Update MachineConfig: could not update registries config with new changes: invalid empty entry for mirror configuration E0321 03:32:01.014926 1 container_runtime_config_controller.go:368] could not Create/Update MachineConfig: could not update registries config with new changes: invalid empty entry for mirror configuration I0321 03:32:01.014946 1 container_runtime_config_controller.go:369] Dropping image config "openshift-config" out of the queue: could not Create/Update MachineConfig: could not update registries config with new changes: invalid empty entry for mirror configuration 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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. https://access.redhat.com/errata/RHSA-2022:5069 |