Bug 1445725 - spacecmd always and only asks for MD5 hash of package
Summary: spacecmd always and only asks for MD5 hash of package
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat58-nth sat5-cfu
TreeView+ depends on / blocked
 
Reported: 2017-04-26 11:47 UTC by Lukáš Hellebrandt
Modified: 2018-06-01 13:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-01 13:13:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.