consoleproxy vm not rebooting after certificate update - 4.22.0

[Jayd603]

Applied a new cert (replacing an expired one) via cloudmonkey - got API success, secondarystorage vm rebooted, consoleproxy did not.

SSL errors are received when connecting to console but all works fine after manually rebooting the consoleproxy VM.

versions

4.22.0, KVM, Ubuntu 24.04

[DaanHoogland]

@Jayd603 , I don’t think an operator would want to have the cp reboot automatically as that will disconnect all clients and need separate planning (in some cases).

[Jayd603]

@Jayd603 , I don’t think an operator would want to have the cp reboot automatically as that will disconnect all clients and need separate planning (in some cases).

That's a good point. In my use case it would be fine but if the console is very active that would be bad to force disconnect everyone.

[DaanHoogland]

@Jayd603 , I don’t think an operator would want to have the cp reboot automatically as that will disconnect all clients and need separate planning (in some cases).

That's a good point. In my use case it would be fine but if the console is very active that would be bad to force disconnect everyone.

ok, glad you agree. This then will require a feature flag if you want to implement it as you originally specified.