Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Puppet broke my Xen

DZone's Guide to

Puppet broke my Xen

· DevOps Zone
Free Resource

The Nexus Suite is uniquely architected for a DevOps native world and creates value early in the development pipeline, provides precise contextual controls at every phase, and accelerates DevOps innovation with automation you can trust. Read how in this ebook.

Actually it didn't , but now I got your attention. 
We just adopted the use of adding headers to all of our files that are managed by puppet so people will know not to touch it
    file {
    "/etc/xen/scripts/network-custom-vlan-bridges":
    owner => "root",
    group => "root",
    mode => "0755",
    content => template(
    "headers/header-hash.erb',
    "xen/co-mmx-network-custom-vlan-bridges.erb");
    }

All worked nice however upon bootstrapping our Xen host the bridges stopped working .. running the network-custom-vlan-bridges script manually solved everything and created the appropriate bridges. But at boottime it didn't..

I added some debug info to the script and figured it never got executed at boot time.

Turns out that when I removed the headers Xen actually does configure the bridges at boot time, Xen probably checks for a shebang at the beginning of the file.

Putting the header at the end of the file therefore solved the problem.

Source:  http://www.krisbuytaert.be/blog/puppet-broke-my-xen


The DevOps Zone is brought to you in partnership with Sonatype Nexus.  See how the Nexus platform infuses precise open source component intelligence into the DevOps pipeline early, everywhere, and at scale. Read how in this ebook

Topics:

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}