Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
If node-installer is re-run with different proxy features enabled each time (like --tftp=false and then --tftp=true), the feature list in Foreman isn't kept in sync as it was fetched when the proxy was first registered.
Version-Release number of selected component (if applicable):
node-installer-0.0.11-1.el6sat.noarch
How reproducible:
Always
Steps to Reproduce:
1. node-install --tftp false --puppet true
2. check smart proxies list in Foreman
3. node-install --tftp true --puppet true
4. check smart proxies list in Foreman
Actual results:
"Puppet", then only "Puppet"
Expected results:
"Puppet", then "Puppet and TFTP"
Additional info:
Workaround: edit the proxy in the Foreman UI and re-save it, the feature list will be retrieved again. In Foreman 1.4, there's a refresh link + API call.
Moving to POST since upstream bug http://projects.theforeman.org/issues/3185 has been closed
-------------
Dominic Cleal
Applied in changeset commit:puppet-foreman|03978d6a5eb55da4fe5eb316db1833fbba344d14.
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