Red Hat Bugzilla – Bug 446269
Unable to remove packages for a client via the webui if the channel is not subscribed
Last modified: 2009-09-10 16:25:19 EDT
Description of problem:
you have rhncfg from the tools channel installed on a system.
However the tools channel is not subscribed.
In the webui if you go to list/remove packages in the sdc..
and remove the package.
then run rhn_check on the client..
no jobs are found, and nothing is picked up..
if you subscribe the channel.. then you can remove the package.
I suspect due to dependency resolution this may be a problem... however it looks
like we allow it in the webui.. so we need to fix something.
<parthonista> cliff: I just chatted with weshay on
<weshay> ya .. that can move to 5.2
<parthonista> cliff: sounds like the behviour was identical in 5.02 to 5.10
<parthonista> cliff: so its not a 'regression' per se
Made removal work now if the package is not in any of the systems subscribed channels.
We now throw this warning:
One or more of the packages you have selected for removal below are not contained in a software channel that this system is subscribed to. If you choose to continue with the removal you will not be able to rollback this system to this snapshot or any prior snapshot.
If the system has a provisioning entitlement and one of the packages selected for removal isn't in any of the channels the system is subscribed to.
Tested with RHEL 4 and RHEL 5 clients.
Basically had to split up the 'update' and 'remove' actions into 2 different queries in the backend. One that restricted based on server channels and one that didn't.
tree e46d8630ee265022a711706ee9e157768496eb2c tree | snapshot
parent 1e2fad3293b836a96ce3c1c71ddb626cc14ca6b2 commit | diff
verified on 4/20
Verified in stage -> RELEASE_PENDING
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.