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.

In 1.0 (well, Beta6) I try to change the environment name. I get a validation error with no explanation (that's a bug unto itself), but then I find these bugs: bug 787226 and bug 795928.

Apparently one can't change the name of an environment because it is linked to its repoID. If this is the case, this is a design flaw. Names (or labels) need to be editable for nearly all objects that one can edit details about within the system. Separately, there needs to be a unique and immutable ID. One is for humans, the other is for uniqueness and machines.

Now, it would be sensible to warn an admin of a potential conflict (like if I wanted to call three environments "Dev". Warn, but not disallow.

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