Project

General

Profile

Bug #5604

content-host list -> the 'id' listed is the uuid; however, system-group requires the db 'id'

Added by Brad Buckingham almost 5 years ago. Updated 8 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Hammer
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

The following scenario seems like it will be confusing to users:

1. When creating a system-group, if the user provides a list of system-ids, it appears that the server expects those to be the db ids (e.g. 1, 2, 3...etc).

2. When listing the content-hosts (systems), the ID listed is the content-host UUID (which is not the one expected in #1).

hammer> content-host list --organization-id ACME_Corporation
-------------------------------------|--------------------------
ID | NAME
-------------------------------------|--------------------------
aedc1566-9aa8-483d-9c0c-b8a556c6fb87 | dhcp129-51.rdu.redhat.com
-------------------------------------|--------------------------

3. When looking at the content-host info, it requires the user to provide --id which is the UUID, but then lists that as the UUID and the DB ID as ID:

hammer> content-host info --organization-id ACME_Corporation --id aedc1566-9aa8-483d-9c0c-b8a556c6fb87
Name: dhcp129-51.rdu.redhat.com
ID: 2
UUID: aedc1566-9aa8-483d-9c0c-b8a556c6fb87
Description: updated description
Location: None
Lifecycle Environment: Library
Content View: Default Organization View
Entitlement Status: invalid
Release Version:
Autoheal: true

hammer>

History

#1 Updated by dustin tsang almost 5 years ago

  • Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1097858

#2 Updated by dustin tsang almost 5 years ago

  • Status changed from New to Closed

#3 Updated by Eric Helms almost 5 years ago

  • Triaged changed from No to Yes

#4 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) set to 13

Also available in: Atom PDF