Closed Bug 1465309 Opened 7 years ago Closed 7 years ago

Ubuntu 16 puppet at-boot setup

Categories

(Infrastructure & Operations :: RelOps: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dhouse, Assigned: dragrom)

References

Details

Attachments

(1 file, 1 obsolete file)

In bug 1463970, we found that the atboot setup for puppet was not working under systemd. Jake wrote: (In reply to Jake Watkins [:dividehex] from comment #10) > Comment on attachment 8980222 [details] [diff] [review] > Bug_1463970_adding_puppet_service.patch > > Review of attachment 8980222 [details] [diff] [review]: > ----------------------------------------------------------------- > > The point of atboot is to make sure puppet only runs "at boot" and runs in a > loop until completing a full puppet run successfully. This patch enables > the puppet systemd service to run puppet like a daemon and that isn't what > we want. That also is why the service is disabled in systemd by default. > > Instead, you will need to change the puppet service > (/lib/systemd/system/puppet.service) to source puppet_atboot_common and call > the run_until_success function. You also need to config the service to > treat it as a run-once. Also don't forget to exec the systemd reload after > changing the service file.
Assignee: relops → dcrisan
Status: NEW → ASSIGNED
The atboot setup for puppet was not working under systemd. - created systemd service file - enabled puppet service under Ubuntu 16.04 machines
Attachment #8987482 - Flags: review?(jwatkins)
Attachment #8987482 - Flags: review?(dhouse)
Attachment #8987482 - Flags: review?(dhouse) → review-
Attachment #8987482 - Flags: review?(jwatkins) → review-
The atboot setup for puppet was not working under systemd. - created systemd service file - enabled puppet service under Ubuntu 16.04 machines
Attachment #8987482 - Attachment is obsolete: true
Attachment #8987812 - Flags: review?(jwatkins)
Attachment #8987812 - Flags: review?(dhouse)
Attachment #8987812 - Flags: review?(dhouse) → review+
Attachment #8987812 - Flags: review?(jwatkins) → review+
Attachment #8987812 - Flags: checked-in+
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
I applied this across the moonshot linux instances. On first run, it failed. But each worked on re-running puppet with the change: ``` Notice: /Stage[main]/Puppet::Atboot/File[/lib/systemd/system/puppet.service]/content: content changed '{md5}b90923e2e0e9639faa2819fd2e183899' to '{md5}f31dea6170efe15870a2202ad958f6ac' Info: /Stage[main]/Puppet::Atboot/File[/lib/systemd/system/puppet.service]: Scheduling refresh of Exec[reload systemd] Notice: /Stage[main]/Puppet::Atboot/Exec[reload systemd]/returns: executed successfully Notice: /Stage[main]/Puppet::Atboot/Exec[reload systemd]: Triggered 'refresh' from 1 events Error: Could not enable puppet: Error: /Stage[main]/Puppet::Atboot/Service[puppet]/enable: change from false to true failed: Could not enable puppet: Notice: Finished catalog run in 39.67 seconds ```
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: