AIO-DX kube upgrade from 1.21 to 1.22 fails on second control plane
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Chris Friesen |
Bug Description
Performing an AIO-DX kube upgrade (using the vim) of 1.21 to 1.22 fails when it gets to the second control plane.
From sysinv.log:
2023-04-28 14:22:45.975 64199 ERROR sysinv.
sysinv 2023-04-28 14:22:45.980 64199 ERROR zerorpc.core [-] : sysinv.
2023-04-28 14:22:45.980 64199 ERROR zerorpc.core Traceback (most recent call last):
2023-04-28 14:22:45.980 64199 ERROR zerorpc.core File "/usr/lib/
2023-04-28 14:22:45.980 64199 ERROR zerorpc.core subprocess.
2023-04-28 14:22:45.980 64199 ERROR zerorpc.core File "/usr/lib/
2023-04-28 14:22:45.980 64199 ERROR zerorpc.core raise CalledProcessEr
2023-04-28 14:22:45.980 64199 ERROR zerorpc.core subprocess.
The kube command reports this output:
sudo kubeadm init phase upload-certs --upload-certs --config /tmp/tmpwm_
W0428 14:30:54.462803 3402454 strict.go:47] unknown configuration schema.
{Group:
Changed in starlingx: | |
assignee: | nobody → Chris Friesen (cbf123) |
status: | New → In Progress |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.9.0 stx.containers stx.update |
Fix proposed to branch: master /review. opendev. org/c/starlingx /config/ +/881922
Review: https:/