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.
Could you please specify what the impact after the registration should be from the Satellite perspective? E.g. would saving that priority level as a host parameter be sufficient? Or does the customer expect that Satellite would call some external service (e.g. Service Now) upon the host registration? How would the customer consume the priority level from the Satellite after the registration?
An option that could be used with the existing version is adding a custom fact to subscription-manager or puppet (if customer uses puppet). We are also improving the registration flow that will be easier to customize by modifying the registration template and we also work on webhooks that could potentially help. But we'd need a better understanding of what the customer exactly needs. Thanks
The RFE triage team have evaluated this request, and while it's a valid request, we are closing this as it isn't being prioritized to fix in the next several releases. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
webhooks is coming and would be a possible solution here.
The RFE triage team have evaluated this request, and while it's a valid request, we are closing this as it isn't being prioritized to fix in the next several releases. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
webhooks is coming and would be a possible solution here.