Problem, with Vagrant and Puppet

[Almudena Soblechero Garcia]

Good morning, I' m Almudena, it's my first question in these group, and my english, it'snt good, i apologize


I have a problem with vagrant and puppet.


The problem, its with de certificates, puppetd and puppetmaster.


I think that the problems ist with Vagrant, and with the actuamatically configuration.


I'm goint to explain the problem, I wnat to have one server (puppet master) and one client (puppet), both VM Vagrant have a DNS configurations, but, if reboot the VM client, tha VM lose all the dns configuration.


Any sugestion?



Thnks

[Christopher Wood]

On Mon, Jun 09, 2014 at 01:44:20AM -0700, Almudena Soblechero Garcia wrote:
> Good morning, I' m Almudena, it's my first question in these group, and my
> english, it'snt good, i apologize
>
> I have a problem with vagrant and puppet.
>
> The problem, its with de certificates, puppetd and puppetmaster.
>
> I think that the problems ist with Vagrant, and with the actuamatically
> configuration.

Here's a hint to the problem. How is Vagrant configuring /etc/resolv.conf before the first puppet agent run?

> I'm goint to explain the problem, I wnat to have one server (puppet
> master) and one client (puppet), both VM Vagrant have a DNS
> configurations, but, if reboot the VM client, tha VM lose all the dns
> configuration.
>
> Any sugestion?

Not that I've worked with Vagrant much, but it sounds like Vagrant may be setting up networking, breaking the puppet configuration you used. In your place I'd go dig around in the network settings to see if I could disable DHCP or something similar.

Otherwise, since the damage happens after reboot but before puppet, you might want to go ask the Vagrant people:

https://www.vagrantup.com/support.html#community

> Thnks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [1]puppet-users...@googlegroups.com.
> To view this discussion on the web visit
> [2]https://groups.google.com/d/msgid/puppet-users/a7e0b738-9e2b-4859-a60c-7ec716002d48%40googlegroups.com.
> For more options, visit [3]https://groups.google.com/d/optout.
>
> References
>
> Visible links
> 1. mailto:puppet-users...@googlegroups.com
> 2. https://groups.google.com/d/msgid/puppet-users/a7e0b738-9e2b-4859-a60c-7ec716002d48%40googlegroups.com?utm_medium=email&utm_source=footer
> 3. https://groups.google.com/d/optout

[Almudena Soblechero Garcia]

Hello good afternoon

El lunes, 9 de junio de 2014 13:42:04 UTC+2, Christopher Wood escribió:

On Mon, Jun 09, 2014 at 01:44:20AM -0700, Almudena Soblechero Garcia wrote:
>    Good morning, I' m Almudena, it's my first question in these group, and my
>    english, it'snt good, i apologize
>
>    I have a problem with vagrant and puppet.
>
>    The problem, its with de certificates, puppetd and puppetmaster.
>
>    I think that the problems ist with Vagrant, and with the actuamatically
>    configuration.

Here's a hint to the problem. How is Vagrant configuring /etc/resolv.conf before the first puppet agent run?

My personal configuration with Vagrant before restart Vagrant: it's 

resolv.conf:

search despliegues.com

nameserver 192.168.33.2

nameserver 8.8.8.8

I  wnat to have an  server/client configuration, and DNS its necessary for the certificates between clients and server, right? So Its necessary have DNS configuration, but, when i restart my VM that dns configuration desapear (specially resolv.conf).

 

>    I'm goint to explain the problem, I wnat to have one server (puppet
>    master) and one client (puppet), both VM Vagrant have a DNS
>    configurations, but, if reboot the VM client, tha VM lose all the dns
>    configuration.
>
>    Any sugestion?

Not that I've worked with Vagrant much, but it sounds like Vagrant may be setting up networking, breaking the puppet configuration you used. In your place I'd go dig around in the network settings to see if I could disable DHCP or something similar.

Otherwise, since the damage happens after reboot but before puppet, you might want to go ask the Vagrant people:

https://www.vagrantup.com/support.html#community

I think so, im goint to ask vagrant people, but, thank very much for you help!!

Almudena. 

>    Thnks
>
>    --
>    You received this message because you are subscribed to the Google Groups
>    "Puppet Users" group.
>    To unsubscribe from this group and stop receiving emails from it, send an
>    email to [1]puppet-users...@googlegroups.com.
>    To view this discussion on the web visit
>    [2]https://groups.google.com/d/msgid/puppet-users/a7e0b738-9e2b-4859-a60c-7ec716002d48%40googlegroups.com.
>    For more options, visit [3]https://groups.google.com/d/optout.
>
> References
>
>    Visible links

>    1. mailto:puppet-users+unsub...@googlegroups.com

[Rich Burroughs]

If you want to rule out Puppet as being involved, you could run the Puppet agent by hand when you know that the resolv.conf is correct and see if anything changes. If it's something happening on reboot, I doubt Puppet is involved.

If you're using VirtualBox, Vagrant will assign a NAT interface automatically as the first interface on the host and that will use DHCP. You can specify other additional network interfaces in your Vagrantfile.

I have a multi-host Vagrant environment I use with Virtualbox for Puppet testing. I define a second interface on the hosts using private_network, and just copy in a pre-populated hosts file during the provisioning. If you need your VM to talk to your real Puppet master, then that setup wouldn't work.

Rich

To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/63ec01eb-6e88-47f0-837c-62c7116a1e00%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.