Bug #17648
closed
Attribute inheritance is not propagated correctly in UI/API workflows
Added by Shimon Shtein over 7 years ago.
Updated about 6 years ago.
Description
update method does not invoke #apply_inherited_attributes on the newly created host.
Files
- Subject changed from PUT /discovered_hosts/:id is not inheriting attributes from selected hostgroup to Attribute inheritance is not propagated correctly in UI/API workflows
So after some chat it looks like we are not calling apply_inherited_attributes properly from API and also from UI (we call it in edit but not in update).
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_discovery/pull/316 added
- Related to Refactor #14316: Host group fails to auto fill puppet ca & master in discovery provisioning added
I believe this same issue exists with the realm as well. Please see attached screen shots for example. If I'm talking about something different let me know and I'll open a new bug.
In short, inherited Puppet CA, Puppet Master, and Realm are showing up in the host group but not on a newly created host.
It should all be solved by this fix.
All inherited attributes are manged by those two methods: #apply_inherited_attributes and #set_hostgroup_defaults that are added by this PR.
Let us know, if it's not solving your case.
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Related to Bug #18106: Discovery v8 provisioning throws ActiveModel::ForbiddenAttributesError when Katello is installed added
- Related to Bug #20797: Provisioning errors with undefined method permit! for ActiveSupport::HashWithIndifferentAccess added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by