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:
@host.operatingsystem.password_hash should work with safe mode enabled
Version-Release number of selected component (if applicable):
foreman 1-10
How reproducible:
100%
Steps to Reproduce:
1. try using @host.operatingsystem.password_hash in a KS template with safe_mode render set to true
2.
3.
Actual results:
KS render error
Expected results:
KS to render
Additional info:
The template shipped with Katello was not updated to load the hash algorithm from OS, only templates coming in Foreman core were. I sent a patch that should make this complete.
Comment 7Satellite Program
2017-02-15 09:19:41 UTC
Upstream bug assigned to mhulan
Comment 8Satellite Program
2017-02-15 09:19:45 UTC
This bug has an upstream issue. When this issue is resolved, it will be included in the next Satellite release. We will no longer be tracking this downstream. If you feel this should not have been closed, please feel free to re-open with additional details.