Bug 1781546

Summary: Hammer cli unable to show complete n/w ID
Product: Red Hat Satellite Reporter: vijsingh
Component: Compute Resources - AzureAssignee: Aditi Puntambekar <apuntamb>
Status: CLOSED ERRATA QA Contact: vijsingh
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: pcreech
Target Milestone: 6.7.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-hammer_cli-0.19.1-1, tfm-rubygem-hammer_cli_foreman-0.19.5-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 13:28:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1775890    

Description vijsingh 2019-12-10 09:09:42 UTC 
Description of problem:

Hammer cli unable to show complete n/w ID


Version-Release number of selected component (if applicable):

@Satellite 6.7.0 snap 4.0

How reproducible:
Always

Steps to Reproduce:

# hammer compute-resource networks --id 10
---------------------------------------------------------------------------------|--------
ID | NAME
---------------------------------------------------------------------------------|--------
/subscriptions/c9e72cc-b20e-48bd-a0c8-fgh879b/resourceGroups/Automation... | default
/subscriptions/c9e72cc-b20e-48d-a0c8-fgh879c/resourceGroups/TUKSAE/prov... | default


Expected results:

 N/w IDs should show the complete details.

Additional info:
Comment 3 Bryan Kearney 2019-12-10 11:02:36 UTC 
Upstream bug assigned to apuntamb
Comment 4 vijsingh 2020-01-16 07:38:55 UTC 
ON_QA Verified 

@Satellite 6.7.0 snap 8.0
Comment 8 errata-xmlrpc 2020-04-14 13:28:06 UTC 
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/RHSA-2020:1454