Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 625349

Summary:	RFE for yum-plugins (protectbase) functionality on spacewalk servers...
Product:	[Community] Spacewalk	Reporter:	Chris Donovan <alienresidents>
Component:	Server	Assignee:	Michael Mráka <mmraka>
Status:	CLOSED WONTFIX	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-01-24 15:01:39 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:	653453

Description Chris Donovan 2010-08-19 06:57:29 UTC

Description of problem:
Currently all of my client systems use the yum plugin protectbase.  I use various repos for several specific packages (instead of creating my own repo).  While this is a good thing for the client, the spacewalk kserver doesn't acknowledge these protections.

I would like to see my system list according to protected packages, so that I know if I'm "really" up to date or not.  Currently I have to login and run yum check-update to figure out if I am really up to date according to protectbase.


Version-Release number of selected component (if applicable):
1.0.4-1.el5


How reproducible:
Add the protectbase yum plugin.  Add several repos.  Ensure there are conflicting rpm's, or at least mutliple versions of the same package, and protect some of the lower verion repos.  register client into the correct org with the correct channels configured.  check system status, and notice that there are "packages to update", and then run an update packages command, and you'll see it won't install the conflicting packages on the client.


Thanks,

Chris-

Comment 1 Jan Pazdziora (Red Hat) 2010-10-27 08:32:22 UTC

Mass-aligning under space12, so that we don't lose track of this bugzilla. This however does not mean that we plan (will be able to) address this bug in Spacewalk 1.2.

Comment 2 Jan Pazdziora (Red Hat) 2010-11-19 16:05:01 UTC

Mass-moving to space13.

Comment 3 Michael Mráka 2011-01-24 15:01:39 UTC

Mixing spacewalk repos and other defined directly on the client is known to cause this kind of mis-reports for essentially any other yum plugin. 
There's nothing to fix on spacewalk side because it has zero knowledge about repos setup directly on client so it can't take them into account.

Additional packages can be synced into child channel(s) from external repositories via spacewalk-repo-sync + using cloned channels you should be able to achieve the same results without protectbase plugin.