Bug 1219151

Summary: [New] - When user tries to schedule a snapshot with the current date and time it says operational cancelled
Product: [Retired] oVirt Reporter: RamaKasturi <knarra>
Component: ovirt-engine-webadminAssignee: Shubhendu Tripathi <shtripat>
Status: CLOSED CURRENTRELEASE QA Contact: Stanislav Graf <sgraf>
Severity: high Docs Contact:
Priority: medium    
Version: 3.6CC: bugs, ecohen, gklein, lsurette, mgoldboi, rbalakri, sabose, yeylon
Target Milestone: ---   
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: gluster
Fixed In Version: ovirt-engine-3.6.0-0.0.master.20150514172356.git1f1cc88 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-04 11:44:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1187461    

Description RamaKasturi 2015-05-06 16:59:03 UTC 
Description of problem:
When user tries to schedule a snapshot with the current date and time, it throws Operation cancelled dialog with error start date cannot be less than current date.

Version-Release number of selected component (if applicable):
ovirt-engine-3.6.0-0.0.master.20150429182702.git939c2e8.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a volume and click on snapshot -> New
2. Click on schedule tab and select the recurrence as minutely.
3. Now select the time zone and set the end date.
4. click on 'OK'

Actual results:
UI throws internal engine error and displays a message says "Start date cannot be less than current date"

Expected results:
Snapshot scheduling should be successful.

Additional info:
Comment 1 Stanislav Graf 2015-05-19 11:01:57 UTC 
Retested with
ovirt-engine-3.6.0-0.0.master.20150518173633.gitcf0f078.el6.noarch

using scenario from Comment 0

--> VERIFIED
Comment 2 Sandro Bonazzola 2015-11-04 11:44:19 UTC 
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.