Bug 1083519

Summary:	(spacecmd) softwarechannel_removepackages and different package checksums
Product:	[Community] Spacewalk	Reporter:	Jeremy Maes <jma>
Component:	Clients	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.1	CC:	jma
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	spacecmd-2.2.10-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-17 08:41:14 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:	1119298

Description Jeremy Maes 2014-04-02 11:50:36 UTC

Description of problem: When trying to remove packages with the same name, version number, ... but different checksums the spacecmd implementation of softwarechannel_removepackages fails to remove the packages.

When using a * wildcard it will list all packages correctly, but due to the way the tool builds its package id list (packagelist -> namelist -> request id's from result) I figure it isn't able to build a correct list because multiple id's are possible for "duplicate" packages.


Version-Release number of selected component (if applicable): 2.1.25


How reproducible: always


Steps to Reproduce:
1. Add 2 packages with identical name, version and arch but different checksums to a channel
2. Try to delete them using spacecmd and softwarechannel_removepackages
3. None are removed

Actual results: No packages are removed


Expected results: Either both are removed or a warning/error is given that there is ambiguity. When wildcards are used any match should be removed.


Additional info: Removal works fine from webui or via direct API removal using the id's.

Comment 1 Jeremy Maes 2014-06-10 14:15:32 UTC

I had almost forgotten about this bug, but upon further testing after filing it I found out that one version gets deleted on the first run, none get deleted afterwards.

So it's not exactly "none are removed", but one only gets removed on first execution. (which kinda surprised me as I expected it to delete just one version every run.

Comment 2 Milan Zázrivec 2014-06-24 15:33:26 UTC

Fixed in spacewalk.git master: f185a0ec027ddcf2dcdfae5d9a15691d37ecd509

Thank you for a quite interesting bug report.

Comment 3 Milan Zázrivec 2014-07-17 08:41:14 UTC

Spacewalk 2.2 has been released:

    https://fedorahosted.org/spacewalk/wiki/ReleaseNotes22