Bug 1224691 - Internal Engine Error is seen while setting snapshot schedule
Summary: Internal Engine Error is seen while setting snapshot schedule
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: RHGS 3.1.0
Assignee: Shubhendu Tripathi
QA Contact: Stanislav Graf
URL:
Whiteboard:
Depends On:
Blocks: 1202842 1224288
TreeView+ depends on / blocked
 
Reported: 2015-05-25 11:13 UTC by Arthy Loganathan
Modified: 2015-07-29 05:29 UTC (History)
6 users (show)

Fixed In Version: rhsc-3.1.0-59
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-29 05:29:34 UTC
Embargoed:


Attachments (Terms of Use)
Screenshot for Internal engine error (205.27 KB, image/png)
2015-05-25 11:13 UTC, Arthy Loganathan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:1494 0 normal SHIPPED_LIVE Red Hat Gluster Storage Console 3.1 Enhancement and bug fixes 2015-07-29 09:24:02 UTC
oVirt gerrit 41822 0 master MERGED gluster: Propagate the scheduler error to UI Never
oVirt gerrit 42278 0 ovirt-engine-3.5-gluster MERGED gluster: Propagate the scheduler error to UI Never

Description Arthy Loganathan 2015-05-25 11:13:22 UTC
Created attachment 1029415 [details]
Screenshot for Internal engine error

Description of problem:
Internal Engine Error is seen, while setting the snapshot schedule, with the below mentioned options. 

    Recurrence - monthly
    Time zone - Asia/Calcutta
    Start schedule by - 05/25/2015 14:30
    Days of month : selected 9 and 10 
    End by date : 05/26/2015 14:30
Note: Have selected the days of month which is not between the start and end date

Version-Release number of selected component (if applicable):
rhsc-3.1.0-0.0.scratch.master.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a volume.
2. Create a snapshot, by clicking Snapshot-> New
3. Schedule the snapshot with the above mentioned options.

Actual results:
Operation Calncelled: Error while executing action ScheduleGlusterVolumeSnapshot: Internal Engine Error is seen.

Expected results:
If the user selected the days of month, which is not between the start and end date, then proper error message should be shown

Additional info:
Screenshot Attached

Engine Logs:

2015-05-25 19:48:10,815 INFO  [org.ovirt.engine.core.bll.gluster.ScheduleGlusterVolumeSnapshotCommand] (ajp-/127.0.0.1:8702-4) [1de4f3ed] Running command: ScheduleGlusterVolumeSnapshotCommand internal: false. Entities affected :  ID: fa2bf8e9-7a52-4dc6-8ec1-13598d18cdb9 Type: GlusterVolumeAction group MANIPULATE_GLUSTER_VOLUME with role type ADMIN
2015-05-25 19:48:10,826 ERROR [org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImpl] (ajp-/127.0.0.1:8702-4) failed to schedule job: Based on configured schedule, the given trigger will never fire.
2015-05-25 19:48:10,831 ERROR [org.ovirt.engine.core.bll.gluster.ScheduleGlusterVolumeSnapshotCommand] (ajp-/127.0.0.1:8702-4) [1de4f3ed] Transaction rolled-back for command: org.ovirt.engine.core.bll.gluster.ScheduleGlusterVolumeSnapshotCommand.
2015-05-25 19:48:10,848 INFO  [org.ovirt.engine.core.bll.gluster.ScheduleGlusterVolumeSnapshotCommand] (ajp-/127.0.0.1:8702-4) [1de4f3ed] Lock freed to object EngineLock [exclusiveLocks= key: fa2bf8e9-7a52-4dc6-8ec1-13598d18cdb9 value: GLUSTER_SNAPSHOT
, sharedLocks= ]

Comment 3 Ramesh N 2015-06-15 05:39:56 UTC
Moving back to MODIFIED as the build is not ready but errata has moved the bugs to ON_QA.

Comment 4 Stanislav Graf 2015-06-28 18:51:14 UTC
Tested rhsc-3.1.0-0.61.el6.noarch

After similar scenario from Comment 0, following error is displayed:
~~~
Operation Canceled
Error while executing action Schedule gluster volume snapshots: java_lang_RuntimeException: org_quartz_SchedulerException: Based on configured schedule, the given trigger will never fire_
~~~

--> VERIFIED

Comment 6 errata-xmlrpc 2015-07-29 05:29:34 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-1494.html


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