Bug #20969
closed
Installer doesn't seem to restart nginx when a new bring-your-own cert is deployed
Added by Lucas Di Pentima 12 months ago.
Updated 4 months ago.
Release relationship:
Auto
- Target version changed from Development 2023-09-27 sprint to Development 2023-10-11 sprint
- Target version changed from Development 2023-10-11 sprint to Development 2023-10-25 sprint
- Target version changed from Development 2023-10-25 sprint to Development 2023-11-08 sprint
- Status changed from New to In Progress
Updates at 1d068f13d0 - branch 20969-installer-nginx-reload-fix
Debian11 provision test: test-provision-debian11: #523 ![](https://ci.arvados.org/buildStatus/icon?job=test-provision-debian11&build=523)
Refactors the custom_certs
state so that it reloads nginx
only when both *.key
& *.pem
files are updated and correspond to each other. An initial attempt to just have a cmd.run
state monitoring both files failed because it was executed on each file change, failing to reload the service on the first file copy.
Manually tested changing certs and confirming that the new ones were being used after running installer.sh deploy
.
- Target version changed from Development 2023-11-08 sprint to Development 2023-10-25 sprint
Lucas Di Pentima wrote in #note-6:
Updates at 1d068f13d0 - branch 20969-installer-nginx-reload-fix
Debian11 provision test: test-provision-debian11: #523 ![](https://ci.arvados.org/buildStatus/icon?job=test-provision-debian11&build=523)
Refactors the custom_certs
state so that it reloads nginx
only when both *.key
& *.pem
files are updated and correspond to each other. An initial attempt to just have a cmd.run
state monitoring both files failed because it was executed on each file change, failing to reload the service on the first file copy.
Manually tested changing certs and confirming that the new ones were being used after running installer.sh deploy
.
This LGTM, thanks!
- Status changed from In Progress to Resolved
Also available in: Atom
PDF