Hey,
I'm having trouble with the puppet provisioning of a host running Ubuntu
12.10:
On the foreman machine, I manually installed the puppet module
puppetlabs-apache and imported the classes in the foreman GUI.
Then I edited the host and added the classes. After clicking the button
"Run puppet", apache was successfully installed in the host system and the
test website showed up as expected.
Here's the YAML:
> —
> environment: cloud
> parameters:
> …
> classes:
> stdlib:
> concat::setup:
> apache:
Now I edited the host, deleted the classes and clicked "Run puppet" again.
But apache stayed installed, while I would have expected it to be
uninstalled.
Again, the YAML:
> —
> environment: cloud
> parameters:
> …
> classes: {}
How can I make sure that the classes get uninstalled after removing them?
Thanks for the help
Fredi
This is a puppet issue. Please read the puppet docs.
Also I suggest you read a copy of 'Pro Puppet'
To give you a hint edit the apache class - change the 'ensure' line to read
'ensure = absent'
Regards, Mike.
···
On Friday, February 14, 2014 6:06:21 AM UTC-5, Jan-Frederic Markert wrote:
Hey,
I’m having trouble with the puppet provisioning of a host running Ubuntu
12.10:
On the foreman machine, I manually installed the puppet module
puppetlabs-apache and imported the classes in the foreman GUI.
Then I edited the host and added the classes. After clicking the button
"Run puppet", apache was successfully installed in the host system and the
test website showed up as expected.
Here’s the YAML:
environment: cloud
parameters:
…
classes:
stdlib:
concat::setup:
apache:
Now I edited the host, deleted the classes and clicked “Run puppet” again.
But apache stayed installed, while I would have expected it to be
uninstalled.
Again, the YAML:
environment: cloud
parameters:
…
classes: {}
How can I make sure that the classes get uninstalled after removing them?
Thanks for the help
Fredi
> Hey,
>
> I'm having trouble with the puppet provisioning of a host running Ubuntu
> 12.10:
>
> On the foreman machine, I manually installed the puppet module
> puppetlabs-apache and imported the classes in the foreman GUI.
> Then I edited the host and added the classes. After clicking the button
> "Run puppet", apache was successfully installed in the host system and the
> test website showed up as expected.
> Here's the YAML:
>
>> —
>> environment: cloud
>> parameters:
>> …
>> classes:
>> stdlib:
>> concat::setup:
>> apache:
>
>
> Now I edited the host, deleted the classes and clicked "Run puppet" again.
> But apache stayed installed, while I would have expected it to be
> uninstalled.
> Again, the YAML:
>
>> —
>> environment: cloud
>> parameters:
>> …
>> classes: {}
>
>
> How can I make sure that the classes get uninstalled after removing them?
>
Puppet doesn't actually do the removable of the resources (i.e. vhost,
docroot, etc) you previously managed. Instead, those are just outside the
worldview of the puppet agent; the resources are now unmanaged.
···
On Fri, Feb 14, 2014 at 6:06 AM, Jan-Frederic Markert < jan-frederic.markert@codecentric.de> wrote:
Thanks for the help
Fredi
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
Thanks again for the answers.
We have read the puppet docs and we have also found out, that we either
have to remove the puppet class by using "ensure=absent" or to write some
sort of script. But we just hoped, that there is some way that foreman
takes over.
But I think its all about opening my mind and accept, that I have to
destroy the os on the metal once I have done misconfiguration.
Best regards Felix
···
Am Dienstag, 18. Februar 2014 00:55:19 UTC+1 schrieb Sam Kottler:
>
>
>
>
> On Fri, Feb 14, 2014 at 6:06 AM, Jan-Frederic Markert < > jan-freder...@codecentric.de > wrote:
>
>> Hey,
>>
>> I'm having trouble with the puppet provisioning of a host running Ubuntu
>> 12.10:
>>
>> On the foreman machine, I manually installed the puppet module
>> puppetlabs-apache and imported the classes in the foreman GUI.
>> Then I edited the host and added the classes. After clicking the button
>> "Run puppet", apache was successfully installed in the host system and the
>> test website showed up as expected.
>> Here's the YAML:
>>
>>> ---
>>> environment: cloud
>>> parameters:
>>> ...
>>> classes:
>>> stdlib:
>>> concat::setup:
>>> apache:
>>
>>
>> Now I edited the host, deleted the classes and clicked "Run puppet"
>> again. But apache stayed installed, while I would have expected it to be
>> uninstalled.
>> Again, the YAML:
>>
>>> ---
>>> environment: cloud
>>> parameters:
>>> ...
>>> classes: {}
>>
>>
>> How can I make sure that the classes get uninstalled after removing them?
>>
>
> Puppet doesn't actually do the removable of the resources (i.e. vhost,
> docroot, etc) you previously managed. Instead, those are just outside the
> worldview of the puppet agent; the resources are now unmanaged.
>
>
>>
>> Thanks for the help
>> Fredi
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
There are modules which have been written to manage their own removal by
exposing a parameter to manage the "ensure" property.
https://github.com/example42/puppet-apache is one example.
Hope this helps.
···
On Wed, Feb 19, 2014 at 10:11 AM, Felix Massem wrote:
Thanks again for the answers.
We have read the puppet docs and we have also found out, that we either
have to remove the puppet class by using “ensure=absent” or to write some
sort of script. But we just hoped, that there is some way that foreman
takes over.
But I think its all about opening my mind and accept, that I have to
destroy the os on the metal once I have done misconfiguration.
Best regards Felix
Am Dienstag, 18. Februar 2014 00:55:19 UTC+1 schrieb Sam Kottler:
On Fri, Feb 14, 2014 at 6:06 AM, Jan-Frederic Markert <jan-freder…@ >> codecentric.de> wrote:
Hey,
I’m having trouble with the puppet provisioning of a host running Ubuntu
12.10:
On the foreman machine, I manually installed the puppet module
puppetlabs-apache and imported the classes in the foreman GUI.
Then I edited the host and added the classes. After clicking the button
"Run puppet", apache was successfully installed in the host system and the
test website showed up as expected.
Here’s the YAML:
environment: cloud
parameters:
…
classes:
stdlib:
concat::setup:
apache:
Now I edited the host, deleted the classes and clicked "Run puppet"
again. But apache stayed installed, while I would have expected it to be
uninstalled.
Again, the YAML:
environment: cloud
parameters:
…
classes: {}
How can I make sure that the classes get uninstalled after removing them?
Puppet doesn’t actually do the removable of the resources (i.e. vhost,
docroot, etc) you previously managed. Instead, those are just outside the
worldview of the puppet agent; the resources are now unmanaged.
Thanks for the help
Fredi
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
–
Sean M. Alderman
Senior Engineer, UDit Systems Integration and Engineering
University of Dayton
salderman1@udayton.edu
“We are not some casual and meaningless product of evolution. Each of us
is the result of a thought of God. Each of us is willed. Each of us is
loved. Each of us is necessary.” - BXVI
