Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 79985

Summary: don't schedule the same task if there's a pending request already scheduled
Product: Red Hat Network Reporter: Alexandre Oliva <aoliva>
Component: RHN/Web SiteAssignee: Todd Sanders <tsanders>
Status: CLOSED WONTFIX QA Contact: Red Hat Satellite QA List <satellite-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: RHN StableCC: alikins, bretm, cturner, gafton, jturner, robin.norwood
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-11 17:04:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Alexandre Oliva 2002-12-18 12:56:54 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
When I visit the web site, it says a few of my machines that have been down for
the past few days need immediate update.  I have already scheduled the updates
of the corresponding errata, but the only place where this fact is displayed is
in the schedule web page.  It would be nice if it would decrease the `alert
levelĀ“ for a machine as soon as the updates are scheduled, but it should only
get back to normal when they're actually installed.  I imagine the System
Overview web page, as well as the top-level Errata and System Set Manager ->
Errata, could display not only the list of relevant errata, but also the number
of systems for which the errata install has not been scheduled.

Ideally, RHN would refuse to schedule a task (or at least warn about it) if
there's an identical task already scheduled for the same server, otherwise, if
you run rhn_check by hand on the client, you get messages that the requested
packages were already installed or so for every duplicate.

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

How reproducible:

Steps to Reproduce:
1.Schedule some updates for systems that are down, so that they're installed
when the system comes back up
2.A few days go by, and you visit the web page again, and see a number of
pending errata, so you schedule all updates again
3.When the server comes back up, you're impatient and run rhn_check by hand

Actual Results:  You get an `errorĀ“ message from rhn_check for every update
scheduled more than once.

Expected Results:  The RHN web pages should warn in advance, or even prevent,
the duplicate scheduling of tasks.  In particular, the default behavior should
not be of creating duplicates, but rather of scheduling actions only for systems
that don't have the action already scheduled.

Additional info:

Comment 1 Fanny Augustin 2006-11-14 20:38:22 UTC
Reassigning  bugs from gdk (old RHN engineering Manager) to tsanders (current
RHN engineering manager)

Comment 2 Bill C. Riemers 2008-02-11 17:04:50 UTC
This is a good idea, but there is not a good way for RHN to recognize the task
as an unwanted duplicate.