kubevirt - Waiting for kube-control relation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KubeVirt Charm |
Triaged
|
Low
|
Adam Dyess |
Bug Description
Using the ck8s 1.24/stable and kubevirt edge/rev-3 the environment is not able to finish the kubevirt deployment
Status:
kubevirt - Waiting for kube-control relation
Juju logs:
unit-kubevirt-1: 18:28:59 ERROR unit.kubevirt/
registry-location
field required (type=value_
unit-kubevirt-1: 18:28:59 INFO juju.worker.
unit-kubevirt-1: 18:29:33 INFO juju.worker.
unit-kubevirt-1: 18:30:41 ERROR unit.kubevirt/
registry-location
As per the log[0] kubevirt is not showing registry-location.
Workaround:
Force to re-set the registry-location:
juju config kubernetes-
Wait to finish the configuration and set it again:
juju config kubernetes-
Now it is showing the registry:
description: | updated |
Changed in charm-kubevirt: | |
assignee: | nobody → Adam Dyess (addyess) |
Changed in charm-kubevirt: | |
milestone: | 1.27 → 1.27+ck1 |
Changed in charm-kubevirt: | |
milestone: | 1.27+ck1 → 1.27+ck2 |
Changed in charm-kubevirt: | |
milestone: | 1.27+ck2 → 1.29 |
the `registry-location` field was missing in the `kube-control` relation from the 1.24/stable kubernetes- control- plane charm. Looking over that charm (as well as 1.25 and 1.26 releases) it may be possible to get this bug to occur again by deploying charmed kubernetes until it's completely active/idle.
Next, one would then deploy and relate the kubevirt charm with all its necessary relations. This may create the kube-control relation in such a way that the registry-location isn't provided.