Bug 1646733
Summary: | hammer hostgroup info --output json returns json including non unique keys | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Mike McCune <mmccune> |
Component: | Host Group | Assignee: | Rahul Bajaj <rabajaj> |
Status: | CLOSED ERRATA | QA Contact: | jcallaha |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3.0 | CC: | adujicek, akarsale, apatel, inecas, jhutar, kgaikwad, mmccune, pcreech, rabajaj, tbrisker, zhunting |
Target Milestone: | 6.4.1 | Keywords: | PrioBumpQA, Regression, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | tfm-rubygem-hammer_cli_foreman-0.13.2.2-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1596504 | Environment: | |
Last Closed: | 2018-12-06 22:32:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mike McCune
2018-11-05 22:38:58 UTC
Verified in Satellite 6.4.1 Snap 1. the returned output now correctly nests the operating system information. [root@host ~]# hammer --output json -v -u admin -p changeme hostgroup info --id 1 { "Id": 1, "Name": "test", "Title": "test", "Description": "", "Network": { }, "Operating system": { "Architecture": { "Name": "x86_64", "Id": 1 }, "Operating System": { "Name": "RHEL Server 7.6", "Id": 1 }, "PXE Loader": "PXELinux BIOS" }, "Puppetclasses": [ ], "Parameters": [ ], "Organizations": [ { "Name": "Default Organization", "Id": 1 } ], "OpenSCAP Proxy": null, "Content View": { "ID": 1, "Name": "Default Organization View" }, "Lifecycle Environment": { "ID": 1, "Name": "Library" }, "Content Source": { "ID": 1, "Name": "sat.domain" }, "Kickstart Repository": { "ID": null, "Name": null } } Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3799 |