Bug 1445725

Summary: spacecmd always and only asks for MD5 hash of package
Product: Red Hat Satellite 5 Reporter: Lukáš Hellebrandt <lhellebr>
Component: ServerAssignee: Tomáš Kašpárek <tkasparek>
Status: CLOSED WONTFIX QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: rdrazny, tlestach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-01 13:13:52 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: 1450940, 1582457    

Description Lukáš Hellebrandt 2017-04-26 11:47:22 UTC 
Description of problem:
spacecmd has hard-coded displaying MD5 hash of a package in package_details call. However, we can (and usually do) have other hashes (like SHA256). In that case, "MD5: None" is shown and no other hash is shown.

How reproducible:
Deterministic

Steps to Reproduce:
1. Have some package with SHA256 hash in Satellite
2. spacecmd -- package_details <package_name>

Actual results:
[...]
MD5:     None
[...]

Expected results:
[...]
SHA256:  <SHA256hash>
[...]
Comment 2 Tomáš Kašpárek 2018-02-26 14:20:41 UTC 
spacewalk.git(master): 4f64a5840b0a4d2c5f9fa889002734a685f39d7f