Bug 668724

Summary:	missing rhnmd in RHN Tools RHEL5@PowerPC or SystemZ channels
Product:	Red Hat Satellite 5	Reporter:	Jan Hutař <jhutar>
Component:	Client	Assignee:	Jan Blazek <jblazek>
Status:	CLOSED DEFERRED	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	540	CC:	cperry, jblazek, jpazdziora, taw
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-04 13:28:30 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:
Bug Depends On:
Bug Blocks:	462714

Description Jan Hutař 2011-01-11 11:49:27 UTC

Description of problem:
Package rhnmd for RHEL5 is only in i386/x86_64/ia64 RHN Tools channels. ppc and s390x variants of the channel are missing this package.


Version-Release number of selected component (if applicable):
rhnmd-5.3.7-1.el5sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Take a look at https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=598760


Actual results:
In section "Available From:" on that page:
Red Hat Network Tools for RHEL Client (v.5 32-bit x86) 
Red Hat Network Tools for RHEL Client (v.5 64-bit x86_64) 
Red Hat Network Tools for RHEL Server (v.5 32-bit x86) 
Red Hat Network Tools for RHEL Server (v.5 64-bit Itanium) 
Red Hat Network Tools for RHEL Server (v.5 64-bit x86_64)
[...]


Expected results:
ppc and s390x channels should be there as well.


Additional info:
Please note also some EUS and LL channels are missing there.

Is rhnmd supported on ppc and s390x archs?

This is related to bug 668491.

Comment 2 Jan Pazdziora (Red Hat) 2011-02-02 10:55:41 UTC

Hello Cliff,

is there any reason we do not have rhnmd (which is noarch) on those arches? I mean, we seem to have the thing built, so it might just as well be a matter of pushing it.

In the past, the package was an arch package ... up until rhnmd-5.3.0-4.el5sat. With rhnmd-5.3.0-5.el5sat, which we shipped in errata

   https://rhn.redhat.com/errata/RHBA-2010-0389.html

we switched to noarch. The thing is, that errata shows that we've pushed the .el4sat packages to those arches (for RHEL 4) but we did *not* ship the .el5sat for RHEL 5. And that presumably set the things for all future pushes.

Do we want the latest noarch pushed to those extra arches?

Do we want to just silently push or do errata?

If errata, it would probably require package respin.

Will it require some QA effort?

Is this really a sat54-errata material?

Jan