Bug 688509 - System status is always shown as up to date if its base channel was cloned using API
Summary: System status is always shown as up to date if its base channel was cloned us...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: API
Version: 540
Hardware: Unspecified
OS: Linux
urgent
medium
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Šimon Lukašík
URL:
Whiteboard:
Depends On:
Blocks: sat541-blockers
TreeView+ depends on / blocked
 
Reported: 2011-03-17 09:25 UTC by Paresh Mutha
Modified: 2018-11-14 15:07 UTC (History)
4 users (show)

Fixed In Version: spacewalk-java-1.2.39-55
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Red Hat Network Satellite v5.4
Last Closed: 2011-06-17 02:30:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Legacy) 48111 0 None None None Never

Description Paresh Mutha 2011-03-17 09:25:43 UTC
Description of problem:
If a system is subscribed to a base channel which had been cloned using API, then inspite of having errata's applicable to the system, its status is always shown as up to date.
If we change the system's base channel to a base channel cloned from web-ui then the behavior is corrected and it shows the errata updates as applicable.

Version-Release number of selected component (if applicable):
Red Hat Network Satellite v5.4

How reproducible:
Always

Steps to Reproduce:
1. Clone a channel (test-clone-api) using channel.software.clone API
2. Subscribe a system (which is not fully updated) to the newly created cloned channel (test-clone-api)
3. Check System's Overview page

Actual results:
System status is shown as up to date

Expected results:
System status shows "Count of applicable errata's should be displayed"

Additional info:
If we create a clone a channel (test-clone-web-ui) through web interface and subscribe the same system to it then it shows the count of errata/packages applicable to the system.

Comment 3 Tomas Lestach 2011-04-07 09:36:42 UTC
I let compute channel newest packages and errata cache for the cloned channel, but  rhn_channel.refresh_newest_package took about 2,5minutes for channels with 11000 packages (like current rhel5 x86_64 channel).
After trying several options I decided to 'clone' the rhnChannelNewestPackage content of the original channel as well. My speed expectations were met.

spacewalk.git: 60b95f765093ab8ee73c36289f5fd6b1c66b969f

Comment 6 Šimon Lukašík 2011-05-11 07:02:51 UTC
Changing to Verified:

Testing procedure:
 - As per comment 0. (Compared behaviour on sat540 to Sat541)
 - clone rhel6 base channel via API
 - subscribe a system
 - check the updates on WebUI

Verified against:
spacewalk-java-1.2.39-68.el6sat.noarch

Comment 7 Milan Zázrivec 2011-06-01 09:56:30 UTC
Verified in stage w/ spacewalk-java-1.2.39-82 -> release pending.

Comment 8 Clifford Perry 2011-06-17 02:30:09 UTC
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.

https://rhn.redhat.com/errata/RHSA-2011-0879.html


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