Attempting to delete a host

Support
1

I've created a host and now I want to delete the host from the foreman UI.
The delete operation telling me that it could not delete the host's
certificate. Inspecting the list of certificates show that there is no
certificate for the host to be provisioned.

Failed to save: Failed to remove dizz2.cloudcomplab.ch's puppet
certificate: 406 Not Acceptable, Failed to generate PXELinux template:
Missing host to link to! Please provide :host parameter or set
default_url_options[:host]

Full logs are here: http://pastebin.com/JMCyHKUy

Any ideas on what is going on here? Should there be a certificate created
for a host when it is created via the foreman UI? I presume so…

Andy

2

I've looked at the creation phase via logs and from what I can tell (debug
logs on) there is no step where puppetca is invoked when create the host.

··· On Tuesday, 4 September 2012 22:45:30 UTC+2, Andy Edmonds wrote: > > I've created a host and now I want to delete the host from the foreman UI. > The delete operation telling me that it could not delete the host's > certificate. Inspecting the list of certificates show that there is no > certificate for the host to be provisioned. > > Failed to save: Failed to remove dizz2.cloudcomplab.ch's puppet > certificate: 406 Not Acceptable, Failed to generate PXELinux template: > Missing host to link to! Please provide :host parameter or set > default_url_options[:host] > > Full logs are here: http://pastebin.com/JMCyHKUy > > Any ideas on what is going on here? Should there be a certificate created > for a host when it is created via the foreman UI? I presume so... > > Andy >
3

> I've created a host and now I want to delete the host from the foreman UI.
> The delete operation telling me that it could not delete the host's
> certificate. Inspecting the list of certificates show that there is no
> certificate for the host to be provisioned.
>
> Failed to save: Failed to remove dizz2.cloudcomplab.ch's puppet
> certificate: 406 Not Acceptable, Failed to generate PXELinux template:
> Missing host to link to! Please provide :host parameter or set
> default_url_options[:host]
>
> Full logs are here: http://pastebin.com/JMCyHKUy
>
are you using puppet 2.7.19? it might be the same bug as
Bug #1836: Foreman chokes on "puppet cert clean host.does.not.exist.example.com" as of Puppet 2.7.19 and thus can't provision new hosts - Smart Proxy - Foreman

··· On Tue, Sep 4, 2012 at 11:45 PM, Andy Edmonds wrote:

Any ideas on what is going on here? Should there be a certificate created
for a host when it is created via the foreman UI? I presume so…

Andy

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/gbLHm6dws48J.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

4

I should also note that although I create the host through the UI I do not
provision it on the metal.

··· On Tuesday, 4 September 2012 23:06:55 UTC+2, Andy Edmonds wrote: > > I've looked at the creation phase via logs and from what I can tell (debug > logs on) there is no step where puppetca is invoked when create the host. > > On Tuesday, 4 September 2012 22:45:30 UTC+2, Andy Edmonds wrote: >> >> I've created a host and now I want to delete the host from the foreman >> UI. The delete operation telling me that it could not delete the host's >> certificate. Inspecting the list of certificates show that there is no >> certificate for the host to be provisioned. >> >> Failed to save: Failed to remove dizz2.cloudcomplab.ch's puppet >> certificate: 406 Not Acceptable, Failed to generate PXELinux template: >> Missing host to link to! Please provide :host parameter or set >> default_url_options[:host] >> >> Full logs are here: http://pastebin.com/JMCyHKUy >> >> Any ideas on what is going on here? Should there be a certificate created >> for a host when it is created via the foreman UI? I presume so... >> >> Andy >> >
5

Hi Ohad,

Yes I'm using 2.7.19.

I also see this behaviour when I go to provision a host and the URL http://:3000$FOREMAN/provision/unattended is called when a host is PXE booting. That results in the provisioning process failing and falling back into manual mode :frowning:

Thanks for the pointer to #1836. I guess the temporary fix here is to roll back to an earlier version of puppet.

Andy

··· On 5 Sep 2012, at 08:28, Ohad Levy wrote:

On Tue, Sep 4, 2012 at 11:45 PM, Andy Edmonds andy.edmonds@gmail.com wrote:
I’ve created a host and now I want to delete the host from the foreman UI. The delete operation telling me that it could not delete the host’s certificate. Inspecting the list of certificates show that there is no certificate for the host to be provisioned.

Failed to save: Failed to remove dizz2.cloudcomplab.ch’s puppet certificate: 406 Not Acceptable, Failed to generate PXELinux template: Missing host to link to! Please provide :host parameter or set default_url_options[:host]

Full logs are here: http://pastebin.com/JMCyHKUy
are you using puppet 2.7.19? it might be the same bug as Bug #1836: Foreman chokes on "puppet cert clean host.does.not.exist.example.com" as of Puppet 2.7.19 and thus can't provision new hosts - Smart Proxy - Foreman

Any ideas on what is going on here? Should there be a certificate created for a host when it is created via the foreman UI? I presume so…

Andy

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To view this discussion on the web visit https://groups.google.com/d/msg/foreman-users/-/gbLHm6dws48J.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

6

> I've looked at the creation phase via logs and from what I can tell (debug
> logs on) there is no step where puppetca is invoked when create the host.

thats true, we don't want to modify puppetca or autosign until the host is
actually provisioned.

in case the system is not reinstalling yet, you dont want to expire the
cert, and we want to minimize the amount of time autosign is enabled for
that uuid/fqdn (e.g. open up only when the machine is starting to boot).

Ohad

··· On Wed, Sep 5, 2012 at 12:06 AM, Andy Edmonds wrote:

On Tuesday, 4 September 2012 22:45:30 UTC+2, Andy Edmonds wrote:

I’ve created a host and now I want to delete the host from the foreman
UI. The delete operation telling me that it could not delete the host’s
certificate. Inspecting the list of certificates show that there is no
certificate for the host to be provisioned.

Failed to save: Failed to remove dizz2.cloudcomplab.ch’s puppet
certificate: 406 Not Acceptable, Failed to generate PXELinux template:
Missing host to link to! Please provide :host parameter or set
default_url_options[:host]

Full logs are here: http://pastebin.com/**JMCyHKUyhttp://pastebin.com/JMCyHKUy

Any ideas on what is going on here? Should there be a certificate created
for a host when it is created via the foreman UI? I presume so…

Andy

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/pyvKBpVOSBYJ.

To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

7

> Hi Ohad,
>
> Yes I'm using 2.7.19.
>
> I also see this behaviour when I go to provision a host and the URL
> http://:3000$FOREMAN/provision/unattended is called when a host is PXE
> booting. That results in the provisioning process failing and falling back
> into manual mode :frowning:
>
> Thanks for the pointer to #1836. I guess the temporary fix here is to roll
> back to an earlier version of puppet.
>
> just the motivation i needed :wink: http://git.io/uYupBQ

> Andy
>
>
>
>
>
>
>> I've created a host and now I want to delete the host from the foreman
>> UI. The delete operation telling me that it could not delete the host's
>> certificate. Inspecting the list of certificates show that there is no
>> certificate for the host to be provisioned.
>>
>> Failed to save: Failed to remove dizz2.cloudcomplab.ch's puppet
>> certificate: 406 Not Acceptable, Failed to generate PXELinux template:
>> Missing host to link to! Please provide :host parameter or set
>> default_url_options[:host]
>>
>> Full logs are here: http://pastebin.com/JMCyHKUy
>>
> are you using puppet 2.7.19? it might be the same bug as
> Bug #1836: Foreman chokes on "puppet cert clean host.does.not.exist.example.com" as of Puppet 2.7.19 and thus can't provision new hosts - Smart Proxy - Foreman
>
>>
>> Any ideas on what is going on here? Should there be a certificate created
>> for a host when it is created via the foreman UI? I presume so…
>>
>> Andy
>>
>> –
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/foreman-users/-/gbLHm6dws48J.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> foreman-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
>
> –
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to
> foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/foreman-users?hl=en.
>
>
> –
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to
> foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/foreman-users?hl=en.
>

··· On Wed, Sep 5, 2012 at 10:00 AM, Andy Edmonds wrote: > On 5 Sep 2012, at 08:28, Ohad Levy wrote: > On Tue, Sep 4, 2012 at 11:45 PM, Andy Edmonds wrote:
8

That fix is confirmed working here! :slight_smile:

··· On 5 Sep 2012, at 09:34, Ohad Levy wrote:

On Wed, Sep 5, 2012 at 10:00 AM, Andy Edmonds andy.edmonds@gmail.com wrote:
Hi Ohad,

Yes I’m using 2.7.19.

I also see this behaviour when I go to provision a host and the URL http://:3000$FOREMAN/provision/unattended is called when a host is PXE booting. That results in the provisioning process failing and falling back into manual mode :frowning:

Thanks for the pointer to #1836. I guess the temporary fix here is to roll back to an earlier version of puppet.

just the motivation i needed :wink: http://git.io/uYupBQ

Andy

On 5 Sep 2012, at 08:28, Ohad Levy ohadlevy@gmail.com wrote:

On Tue, Sep 4, 2012 at 11:45 PM, Andy Edmonds andy.edmonds@gmail.com wrote:
I’ve created a host and now I want to delete the host from the foreman UI. The delete operation telling me that it could not delete the host’s certificate. Inspecting the list of certificates show that there is no certificate for the host to be provisioned.

Failed to save: Failed to remove dizz2.cloudcomplab.ch’s puppet certificate: 406 Not Acceptable, Failed to generate PXELinux template: Missing host to link to! Please provide :host parameter or set default_url_options[:host]

Full logs are here: http://pastebin.com/JMCyHKUy
are you using puppet 2.7.19? it might be the same bug as Bug #1836: Foreman chokes on "puppet cert clean host.does.not.exist.example.com" as of Puppet 2.7.19 and thus can't provision new hosts - Smart Proxy - Foreman

Any ideas on what is going on here? Should there be a certificate created for a host when it is created via the foreman UI? I presume so…

Andy

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To view this discussion on the web visit https://groups.google.com/d/msg/foreman-users/-/gbLHm6dws48J.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.