Bug 1617942

Summary: drop dmidecode dependency on s390 s390x architectures
Product: Red Hat Enterprise Linux 7 Reporter: Tomáš Kašpárek <tkasparek>
Component: rhn-client-toolsAssignee: Tomáš Kašpárek <tkasparek>
Status: CLOSED ERRATA QA Contact: Jan Hutař <jhutar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: jhutar, liliu, lmiksik, sgraf, smoroney, tkasparek, tlestach
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhn-client-tools-2.0.2-24.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 11:50:25 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: 1509936, 1615433, 1619146    

Description Tomáš Kašpárek 2018-08-16 08:35:55 UTC 
Description of problem:
dmidecode is not present on s390x and s390, therefore there's no need to require python-dmidecode on these architectures

Version-Release number of selected component (if applicable):
rhn-client-tools-2.0.2-21.el7

How reproducible:
always

Steps to Reproduce:
1. # python
2. >> import dmidecode
   >> dmidecode.bios()

Actual results:
rhn-client-tools require python-dmidecode which returns nothing, thus this is redundant dependency

Expected results:
python-dmidecode is not required

Additional info:
python-dmidecode is going to be dropped on s390 s390x, see https://bugzilla.redhat.com/show_bug.cgi?id=1509936
Comment 2 Tomáš Kašpárek 2018-08-16 08:47:44 UTC 
spacewalk.git(master): d193e402bbfeaee081677c426ad371dccd41566b
Comment 6 Jan Hutař 2018-08-22 04:55:35 UTC 
*** Bug 1619146 has been marked as a duplicate of this bug. ***
Comment 7 Jan Hutař 2018-08-30 07:40:38 UTC 
*** Bug 1619146 has been marked as a duplicate of this bug. ***
Comment 15 errata-xmlrpc 2018-10-30 11:50:25 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/RHBA-2018:3328