Bug 741215 - Scheduling package removal in RHN webui fails when package have epoch
Scheduling package removal in RHN webui fails when package have epoch
Status: NEW
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Backend (Show other bugs)
RHN Stable
Unspecified Unspecified
high Severity high
: ---
: ---
Assigned To: rhn-dev-list
Red Hat Network Quality Assurance
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-09-26 05:55 EDT by Martin Minar
Modified: 2016-07-03 20:59 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Martin Minar 2011-09-26 05:55:45 EDT
Description of problem:
Package removal action in RHN WebUI of package samba-swat-3.5.10-104.el6:0 does not remove package.

Version-Release number of selected component (if applicable):
yum-rhn-plugin-0.9.1-36.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Register RHEL6.2 Client into RHN
2. yum install samba-swat
3. Go to rhn.redhat.com
4. Find package samba-swat on your machine and schedule package removal
5. On client run rhn_check
  
Actual results:
Action is moved from pending to histrory with:

This action will be executed after 2011-09-26 02:36:53 PDT.

This action's status is: Failed.
This action has not yet been picked up.
Packages to be removed:

    samba-swat-3.5.10-104.el6:0


Expected results:
Package is removed.

Additional info:
1. It is not clear whether it is problem in yum-rhn-plugin or in RHN itself.
2. Problem is NOT PRESENT on Satellite.
3. Problem is not present with package zsh-4.3.10-4.1.el6 (no epoch), but is present with package smartmontools-5.39.1-5.el6:1 (epoch 1).
Comment 3 Miroslav Suchý 2011-09-26 07:46:53 EDT
Since this does not reach rhn_check, this is problem of hosted.

Note You need to log in before you can comment on or make changes to this bug.