puppetAgain should not force ifcfg management

RESOLVED FIXED

Status

Infrastructure & Operations
CIDuty
RESOLVED FIXED
5 years ago
3 months ago

People

(Reporter: Callek, Assigned: Callek)

Tracking

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Created attachment 763289 [details] [diff] [review]
[puppet320] v1

So today in final stages of setting up seamonkey's puppetmaster I did a reboot, which then brought the host down.

:fox2mike noticed it had a modified ifcfg-eth0 which was forcing it to try to use DHCP which of course, community doesn't have available.

This patch allows us to mark it to not be managed (so we don't blow away the proper ifcfg)
Attachment #763289 - Flags: review?(dustin)
(Assignee)

Comment 1

5 years ago
Comment on attachment 763289 [details] [diff] [review]
[puppet320] v1

Review of attachment 763289 [details] [diff] [review]:
-----------------------------------------------------------------

::: modules/network/manifests/init.pp
@@ +2,4 @@
>  # License, v. 2.0. If a copy of the MPL was not distributed with this
>  # file, You can obtain one at http://mozilla.org/MPL/2.0/.
>  class network {
> +    import config

err include ::config
Comment on attachment 763289 [details] [diff] [review]
[puppet320] v1

Review of attachment 763289 [details] [diff] [review]:
-----------------------------------------------------------------

This looks fine.  Don't forget to document the new config var.
Attachment #763289 - Flags: review?(dustin) → review+
Product: mozilla.org → Release Engineering

Updated

3 months ago
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.