[OKD-SCOS v4.16] Machinesets/machines provisioned on Openstack(2024.1 Caracal (SLURP)) does not get deleted #2027
Replies: 3 comments
-
The panic isn't great. Might want to understand what nil pointer is being dereferenced there. But as for the issue of deleting the bad VMs: I can reproduce your issue easily enough:
Since the VM won't exist in OpenStack, you could remove the So, if I delete the MachineSet to get the machine stuck in Deleting:
Then I can just patch the
|
Beta Was this translation helpful? Give feedback.
-
I couldn't reproduce the panic. Is there more of a traceback in the logs? If you can maybe share more of the But it's probably an issue that needs to be raised against the |
Beta Was this translation helpful? Give feedback.
-
Applying with these options:
Logs before pod crashes
|
Beta Was this translation helpful? Give feedback.
-
Hey.
We are in the process of testing machinesets for OKD SCOS on our Openstack installation and have noticed an issue in where the machines get stuck in a phase if you send in a faulty configuration parameter in a yaml file containing configuration of a given machineset. What we are trying to accomplish is to use an RBAC bridged network so that OKD nodes can live in different network segments. Along the way i've tried several configuration parameters, it is a bit hard to get a grasp of what actually gets accepted in the openstack providerSpec.
Applying a machineset:
Applying a non working machineset:
changing to a subnet that is not currently working
It does not show in openstack GUI. Since the config is not working i want to delete it again.
The machineset and nodes gets deleted.
Applying another non working machineset that uses wrong config parameters:
Logs from
oc logs -f machine-api-controllers-6d9d4f8b8b-lh94s -c machine-controller
shows:I want to delete this machineset then.
Stuck in provisioning.
CLI unresponsive. But it gets deleted and the prompt resumes after a while. It is tempting to send a sigint(ctrl+C) but if you do not wait the machines will be stuck in the phase they are in i think.
Applying a completely borked machineset:
It does not seem like the machines created from this machineset will ever get deleted. We've had one stuck for 8 days deleting now.
oc logs -f machine-api-controllers-6d9d4f8b8b-lh94s -c machine-controller shows:
Beta Was this translation helpful? Give feedback.
All reactions