Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 641019

Summary: Individual actions are created while scheduling VERIFY and UPGRADE on number of Systems using SSM
Product: Red Hat Satellite 5 Reporter: Petr Sklenar <psklenar>
Component: WebUIAssignee: Tomas Lestach <tlestach>
Status: CLOSED DEFERRED QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 540   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-04 13:25:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 462714    

Description Petr Sklenar 2010-10-07 14:47:12 UTC 
Description of problem:
Scheduling a UPGRADE and VERIFY packages on a group of system (using SSM) we see the actions are displayed separately for each system.


Version-Release number of selected component (if applicable):
Satellite-5.4.0-RHEL5-re20101001.1

How reproducible:
always

Steps to Reproduce:

1. Select 10 systems which are having provisioning entitlement as well as
subscribed to same config channel

2. Go to system set manager -> configuration -> schedule a config file to be
deployed on those systems.
### here you can see only one action, this step can be skipped

3. Go to system set manager -> packages -> schedule a package to be UPGRADE
on them

4. Go to system set manager -> packages -> schedule a package to be VERIFY
on them

5. Go to Schedule tab

  
Actual results:

There is 10 actions for UPGRADE and 10 action for VERIFY

Expected results:
one action for upgrade and one action for verify


Additional info:
Its similar like in:
Bug 616041  - Individual actions are created while scheduling 'Config File Deploy' on number of Systems using SSM