Bug 670542 - list of affected systems by errata is emptied when updating channels
Summary: list of affected systems by errata is emptied when updating channels
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: WebUI
Version: 1.2
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space16
TreeView+ depends on / blocked
 
Reported: 2011-01-18 16:01 UTC by Daniel Robles
Modified: 2011-09-30 13:44 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-09-30 13:44:42 UTC
Embargoed:


Attachments (Terms of Use)

Description Daniel Robles 2011-01-18 16:01:31 UTC
Description of problem:

when uploading new packages in a channel with rhnpush the errata on that channel stop affecting any system ( the "affected systems" list associated with that errata is emptied ), to get again the list of affected systems  back to normal, I have to manage through the webui the  errata and specify again the channels affected by the errata ( although  the channles are already clicked, in fact the only thing I do  is press on "update channels" )

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

Spacewalk version is 1.2
backend is oracle 11g
oracle client libraries are 10.2
os is red hat entreprise linux 5.5

How to reproduce :

-Through the webui go to errata->manage errata->click on a errata->click on channels tab inside the errata-> click on button update channels , this populates again the list of systems affected with the systems contained in the channels affected by that errata
-upload new packages to channels affected by any errata-> then check the webui again and the systems belonging to the channel with new packages are gone in the "affected system list" of the errata, also the systems are not show as affected by any errata aplied to channel whose the system belongs

Comment 1 Miroslav Suchý 2011-04-11 07:34:31 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 2 Miroslav Suchý 2011-04-11 07:37:35 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 3 Jan Pazdziora (Red Hat) 2011-07-20 11:53:16 UTC
Aligning under space16.

Comment 4 Tomas Lestach 2011-09-30 13:44:42 UTC
I admit this might not work on Spacewalk 1.2.

I do not see the issue on Spacewalk 1.5. Closing as CURRENTRELEASE.
Please reopen in case you'd see the behavior on Spacewalk 1.5 or 1.6nightly.


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