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.

Host facets refactoring broke host RABL API which is used in Hooks to deliver JSON output. Symptoms are missing fields in JSON output: https://github.com/theforeman/foreman_hooks/issues/34

Foreman hook plugin is widely used, for example to workaround UEFI PXE for 6.0-6.2 versions. This is a blocker.

QA notes: Install a test hook:

cat config/hooks/host/managed/create/00_test.sh 
#!/bin/bash
echo " *** got hook $* ***" >> /tmp/hook.log
cat >> /tmp/hook.log
exit 0

Create a new host and verify the log file contains MAC address. Previously, it was missing from the JSON output.

Upstream bug assigned to lzap

Upstream bug assigned to lzap

Moving to POST since upstream bug http://projects.theforeman.org/issues/14981 has been closed

QA: See the notes in the description.

Please only test after https://bugzilla.redhat.com/show_bug.cgi?id=1337200 is released (currently POST, pending new build).

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:1501