Project

General

Profile

Bug #6369

Unable to create host without Puppet master when specified on host group

Added by Dominic Cleal over 7 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Host creation
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1108099
Description of problem:
I detected the problem with switch off the puppet in the provisioning form ("Hosts" > "New host"). Satellite ignores my choice of puppet options in "New host" form and it uses configuration from host group.

Version-Release number of selected component (if applicable):
katello-1.5.0-25.el6sat
foreman-1.6.0.14-1.el6sat

How reproducible:
100%

Steps to Reproduce:
1. We have got Sat6.0.3 with some compute resource (in my case RHEV)
2. We create new host group ("Configure" > "Host Groups" > "New Host Group") and choose some "Puppet CA" and "Puppet Master".
3. We create new guest (in my case RHEV) and we choose our new host group in the selectbox "Host Group"
4. We try to disable puppet, choose empty line for "Puppet CA" and "Puppet Master".

Actual results:
In my case, I had a bad configuration of puppet and I got this error in the log file /var/log/foreman/production.log. When I deselect "Puppet CA" and "Puppet Master" in the host group, everything works well.

Operation FAILED: ERF12-0104 [ProxyAPI::ProxyException]: Unable to set PuppetCA autosign for rhev11.test.example.com ([RestClient::ResourceNotFound]: 404 Resource Not Found) for proxy https://sat6.redhat.com:9090/puppet/ca

Completed 500 Internal Server Error in 418ms

Expected results:
The configuration in the new host form, it will have higher priority than configuration from host group (especially puppet options).

Additional info:


Related issues

Related to Foreman - Bug #9532: Removing environment from a host in hostgroup that has environment silently picks hostgroup environmentResolved2015-02-24
Related to Foreman - Bug #9591: Override puppet configuration on host level does not work if specified on host groupClosed2015-03-01
Related to Discovery - Bug #9784: Autoprovisioning via hostgroup does not populate all parameters via WebUI or APIClosed2015-03-16

Associated revisions

Revision 5e1f3b71 (diff)
Added by Tom Caspy almost 7 years ago

fixes #6369 - allow to override puppet ca/master to nil

History

#1 Updated by Dominic Cleal over 7 years ago

  • Category set to Host creation
  • Assignee deleted (Dominic Cleal)

#2 Updated by Tom Caspy almost 7 years ago

  • Assignee set to Tom Caspy

#3 Updated by The Foreman Bot almost 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2068 added
  • Pull request deleted ()

#4 Updated by Dominic Cleal almost 7 years ago

  • Legacy Backlogs Release (now unused) set to 28

#5 Updated by Tom Caspy almost 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#6 Updated by Dominic Cleal almost 7 years ago

  • Related to Bug #9532: Removing environment from a host in hostgroup that has environment silently picks hostgroup environment added

#7 Updated by Dominic Cleal almost 7 years ago

  • Related to Bug #9591: Override puppet configuration on host level does not work if specified on host group added

#8 Updated by Lukas Zapletal over 6 years ago

  • Related to Bug #9784: Autoprovisioning via hostgroup does not populate all parameters via WebUI or API added

Also available in: Atom PDF