Bug 741215

Summary: Scheduling package removal in RHN webui fails when package have epoch
Product: Red Hat Network Reporter: Martin Minar <mminar>
Component: RHN/BackendAssignee: rhn-dev-list
Status: CLOSED EOL QA Contact: Red Hat Network Quality Assurance <rhn-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: RHN StableCC: mkoci, nbronson, slukasik
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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:
Cloudforms Team: ---

Description Martin Minar 2011-09-26 09:55:45 UTC
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 11:46:53 UTC
Since this does not reach rhn_check, this is problem of hosted.

Comment 5 Thomas "Shea" DeAntonio 2017-07-05 15:12:44 UTC
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).

Comment 6 Thomas "Shea" DeAntonio 2017-07-05 15:13:31 UTC
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).