Bug 1259174 - Smart variables values always shows default in host edit form
Summary: Smart variables values always shows default in host edit form
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: Tomer Brisker
QA Contact: jcallaha
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-02 06:59 UTC by Tomer Brisker
Modified: 2019-11-14 06:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 08:55:44 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Foreman Issue Tracker 7840 None None None 2016-04-22 15:42:23 UTC
Red Hat Product Errata RHBA-2016:1500 normal SHIPPED_LIVE Red Hat Satellite 6.2 Base Libraries 2016-07-27 12:24:38 UTC

Description Tomer Brisker 2015-09-02 06:59:55 UTC
When editing a host in the "Parameters" tab under "Puppet class" smart variables always show default value even when there is an override for the variable that matches the host.
The host's yaml show's the correct value

Comment 1 Tomer Brisker 2015-09-02 06:59:56 UTC
Created from redmine issue http://projects.theforeman.org/issues/7840

Comment 3 Bryan Kearney 2015-09-02 08:04:26 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/7840 has been closed
-------------
Anonymous
Applied in changeset commit:33eca4dfec4949308aa265420b963cd80c5f7d13.

Comment 6 jcallaha 2016-04-07 17:51:35 UTC
Verified in Satellite 6.2 Beta snap 6 Compose 2. Overriden values are shown.

Comment 8 errata-xmlrpc 2016-07-27 08:55:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1500


Note You need to log in before you can comment on or make changes to this bug.