Closed Bug 525443 Opened 17 years ago Closed 17 years ago

puppet should auto-accept the host keys of machines listed in the manifests

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

Attachments

(1 file)

We already have to patch the Puppet manifests when we add new machines. There's no good reason (IMHO) why Puppet shouldn't automatically accept the host keys of machines listed in there. I'm working on a cronjob script to accomplish this, since there's no way to do this within Puppet, as best I can tell.
I just gave this a successful run through with staging-puppet and moz2-linux-slave04. I installed it into the crontab like so: */5 * * * * source /etc/profile && bash /etc/puppet/manifests/accept-hostname-keys.sh /etc/puppet/manifests/site.pp I reset the keys on moz2-linux-slave04, so it would need accepting again, and when the cronjob ran, it did in fact accept the key. And as intended, it did NOT accept the .local key that was also waiting (due to bug 522727).
Attachment #409335 - Flags: review?(catlee)
Comment on attachment 409335 [details] [diff] [review] key accepting cronjob Looks good, as long as the extra "accepted_keys" line is removed.
Attachment #409335 - Flags: review?(catlee) → review+
Comment on attachment 409335 [details] [diff] [review] key accepting cronjob changeset: 73:94172b759d33 I set up the cronjobs on the machines, too: */5 * * * * source /etc/profile && bash /etc/puppet/manifests/accept-hostname-keys.sh /etc/puppet/manifests/site.pp
Attachment #409335 - Flags: checked-in+
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: