Project

General

Profile

Actions

Bug #20969

closed

Installer doesn't seem to restart nginx when a new bring-your-own cert is deployed

Added by Lucas Di Pentima 8 months ago. Updated 9 days ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Deployment
Story points:
2.0
Release:
Release relationship:
Auto

Subtasks 1 (0 open1 closed)

Task #21075: Review 20969-installer-nginx-reload-fixResolvedPeter Amstutz10/13/2023Actions
Actions #1

Updated by Peter Amstutz 8 months ago

  • Target version changed from Development 2023-09-27 sprint to Development 2023-10-11 sprint
Actions #2

Updated by Peter Amstutz 8 months ago

  • Story points set to 2.0
Actions #3

Updated by Peter Amstutz 8 months ago

  • Target version changed from Development 2023-10-11 sprint to Development 2023-10-25 sprint
Actions #4

Updated by Peter Amstutz 7 months ago

  • Target version changed from Development 2023-10-25 sprint to Development 2023-11-08 sprint
Actions #5

Updated by Lucas Di Pentima 7 months ago

  • Status changed from New to In Progress
Actions #6

Updated by Lucas Di Pentima 7 months ago

Updates at 1d068f13d0 - branch 20969-installer-nginx-reload-fix
Debian11 provision test: test-provision-debian11: #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.

Actions #7

Updated by Peter Amstutz 7 months ago

  • Target version changed from Development 2023-11-08 sprint to Development 2023-10-25 sprint
Actions #8

Updated by Peter Amstutz 7 months ago

Lucas Di Pentima wrote in #note-6:

Updates at 1d068f13d0 - branch 20969-installer-nginx-reload-fix
Debian11 provision test: test-provision-debian11: #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!

Actions #9

Updated by Lucas Di Pentima 7 months ago

  • Status changed from In Progress to Resolved
Actions #10

Updated by Peter Amstutz 9 days ago

  • Release set to 70
Actions

Also available in: Atom PDF