Closed Bug 1529432 Opened 6 years ago Closed 2 years ago

puppet: synchronization fails if both scriptworker yaml and supervisord config are changed at the same time

Categories

(Release Engineering :: Release Automation: Other, defect)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: mhentges, Unassigned)

References

Details

To reproduce:

  1. Set up a puppet environment and pin an instance to it (e.g.: dep-m-signing-linux-1, if not being used)
  2. Edit modules/scriptworker/templates/scriptworker.yaml.erb, make an irrelevant change, like tweaking artifact_upload_timeout
  3. Edit modules/scriptworker/templates/supervisor_config.erb, make an irrelevant change like adding a comment to the end of the file "# comment"
  4. On the pinned instance, do a puppet run

Workaround:

  • Make the scriptworker and supervisord changes independently
  • Perform a second puppet run, which will succeed

(In reply to Mitchell Hentges [:mhentges] from comment #0)

Workaround:

  • Make the scriptworker and supervisord changes independently
  • Perform a second puppet run, which will succeed
  • verify that scriptworker is running. If not, sudo supervisorctl start <scriptworkername>

Aiui this is build-puppet / puppetagain, which is EOL.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.