Bug 947205 - SSM: Method to Schedule Commands After Package Installation
Summary: SSM: Method to Schedule Commands After Package Installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: WebUI
Version: 1.10
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Grant Gainey
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On: 606274 950096
Blocks: space20
TreeView+ depends on / blocked
 
Reported: 2013-04-01 20:03 UTC by Grant Gainey
Modified: 2013-08-02 13:01 UTC (History)
8 users (show)

Fixed In Version: spacewalk-java-1.10.43-1
Clone Of: 606274
Environment:
Last Closed: 2013-08-02 13:01:32 UTC
Embargoed:

Attachments (Terms of Use)

Description Grant Gainey 2013-04-01 20:03:25 UTC 
+++ This bug was initially created as a clone of Bug #606274 +++

Description of problem:
Please add 'Method to Schedule Commands After Package Installation' in SSM

How reproducible:
always

Steps to Reproduce:
1. schedule package installation for set of few machine
  
Actual results:
I am not able to see "schedule remote command" for all machines in SSM during package installation

Expected results:
there is schedule remote command for all machines in SSM before/after packages installation

Additional info:
Comment 1 Grant Gainey 2013-04-04 15:33:27 UTC 
Enlarged the scope to cover install, upgrade, and remove.

spacewalk commit 73b66580654e62dd44cae9e90dad4e5f7dc8273d
Comment 2 Grant Gainey 2013-04-09 14:58:09 UTC 
Ignore commit in Comment#1, correct commits are 

9b323f2872082872093624a063af564fdb4c19b3
0a62299142752c970f5f0b26afe667c02c34a1a9

(also note incorrect BZ in commit-msg for 0a62299142752c970f5f0b26afe667c02c34a1a9)
Comment 3 Tomáš Kašpárek 2013-08-02 13:01:32 UTC 
Fix for this bug is present in Spacewalk 2.0, closing this bug as CURRENTRELEASE.
Note You need to log in before you can comment on or make changes to this bug.