consoleproxy vm not rebooting after certificate update - 4.22.0
Open
component:console-proxy
type:new-feature
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 32
Description
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
Contributor guide
Research direction
Start by reproducing the certificate replacement through cloudmonkey on the 4.22.0 KVM setup and compare the secondarystorage and consoleproxy VM behavior. Trace the certificate-update path and the consoleproxy restart handling; done means the consoleproxy reboots automatically and console connections no longer report SSL errors without a manual VM reboot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, ubuntu
- Domain
- cloud, infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100