This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2187539 - unable to use environment names, must use ids
Summary: unable to use environment names, must use ids
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rhel-system-roles
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.3
Assignee: Pino Toscano
QA Contact: CS System Management SST QE
Sagar Dubewar
URL:
Whiteboard: role:rhc
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-17 21:31 UTC by Rich Megginson
Modified: 2023-08-10 22:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
.Unable to register systems with environment names The `rhc` system role fails to register the system when specifying environment names in `rhc_environment`. As a workaround, use environment IDs instead of environment names while registering.
Clone Of:
Environment:
Last Closed: 2023-08-10 22:43:04 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ansible-collections community.general pull 6319 0 None Merged redhat_subscription: use CLI when using environments 2023-05-19 10:24:28 UTC
Red Hat Issue Tracker   RHEL-1172 0 None Migrated None 2023-08-10 22:42:50 UTC
Red Hat Issue Tracker RHELPLAN-154999 0 None None None 2023-04-17 21:42:16 UTC

Description Rich Megginson 2023-04-17 21:31:49 UTC 
When the role was changed to use the module with the dbus interface, the user is unable to provide environment names, because the dbus interface cannot do the name to id mapping.  The user must provide environment ids instead
Comment 7 RHEL Program Management 2023-08-10 22:43:04 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.
Note You need to log in before you can comment on or make changes to this bug.