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:

Create a host-group and add an activation_key to it via the "activation keys" tab.

Note that the "activation key" for example: "rhel7_ak", is not saved when it's edited and checked again.

Also the host doesn't configure the necessary repos becauses the activation-keys info is missing.

Version-Release number of selected component (if applicable):
Sat6.2.0-Beta-SNAP1

How reproducible:


Steps to Reproduce:
1. create a new host-group, provide activation_keys
2. Click on host-group and notice that the value of the activation_key is not saved.
3.

Actual results:
hostgroup does not save activation-key info, results in clients not getting repos configured.

Expected results:
hostgroup should save activation-key info.

Additional info:

Workaround could be adding a "global parameter"=kt_activation_keys, value=<ak_name>

*** This bug has been marked as a duplicate of bug 1311767 ***