Bug 1030444 - Schedule kickstart doesn't accept date of pick up in virtualization tab
Schedule kickstart doesn't accept date of pick up in virtualization tab
Status: CLOSED CURRENTRELEASE
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server (Show other bugs)
560
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jan Dobes
Red Hat Satellite QA List
:
Depends On:
Blocks: 462714
  Show dependency treegraph
 
Reported: 2013-11-14 08:12 EST by Pavel Studeník
Modified: 2018-04-09 07:03 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-09 07:03:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Pavel Studeník 2013-11-14 08:12:08 EST
Description of problem:
I create kickstart (virtualization) and I set date for "schedule kickstart". On the server osad is run and this event was picked up right away. The same problem is on Satellite 5.5. 

Schedule provisioning works correct, problem is only in virtualization (webui tab). 


Version-Release number of selected component (if applicable):
spacewalk-java-2.0.2-46.el6sat.noarch


How reproducible:
always

Steps to Reproduce:
1. install osad and create kickstart for provisioning (kvm or xen)
2. provision virtual system - set "kickstart schedule" to "Schedule kickstart no sooner than" and set date from future. 


Actual results:
Event was pick up right away

Expected results:
Event will be pick up in future
Comment 2 Tomas Lestach 2018-04-09 07:03:37 EDT
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

We believe this bug has been fixed in the latest Satellite 5 version (5.8), so closing the bug as CURRENTRELEASE. Please feel free to re-open in case you discover any issues.

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