Bug 893435

Summary: Incorrect units are displayed in operation schedule detail
Product: [JBoss] JBoss Operations Network Reporter: Filip Brychta <fbrychta>
Component: Operations, UIAssignee: Jirka Kremser <jkremser>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.1.2CC: jkremser, myarboro
Target Milestone: ---   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-02 20:35:37 UTC Type: Bug
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: 860818    
Bug Blocks:    
Attachments:
Description Flags
new schedule
none
operation schedule detail
none
operation history none

Description Filip Brychta 2013-01-09 10:39:48 UTC
Created attachment 675411 [details]
new schedule

Description of problem:
Value of 'Repeat every' field in operation schedule detail is displayed with incorrect units.

Version-Release number of selected component (if applicable):
3.1.2.CR1

How reproducible:
Always

Steps to Reproduce:
1. import RHQ Agent to your inventory
2. schedule a new 'Execute availability scan' operation according to newSchedule.png
3. view detail of this schedule operation 
  
Actual results:
see opScheduleDetail.png - 'Repeat every' field is 6000 seconds

Expected results:
'Repeat every' field is 60 seconds

Additional info:
Operation is launched correctly each 60 seconds (see opHistory.png) so only problem is incorrect 'Repeat every' field displayed in operation schedule detail

Comment 1 Filip Brychta 2013-01-09 10:40:33 UTC
Created attachment 675414 [details]
operation schedule detail

Comment 2 Filip Brychta 2013-01-09 10:40:58 UTC
Created attachment 675415 [details]
operation history

Comment 3 Jirka Kremser 2013-01-31 11:57:27 UTC
This was fixed in master branch by commit 88e982cc45e152fc2025bd73f7e8f7a6ed9d52bb (Bug 860818) => should be present in 3.2.0 release. Changing status to MODIFIED.

Comment 4 Jirka Kremser 2013-02-08 15:09:20 UTC
As discussed during today's hangout, bugs with 3.2.0 release should go to ON_QA, so I am moving it to ON_QA.

Comment 5 Filip Brychta 2013-02-11 09:59:19 UTC
Verified on 
Version: 4.6.0-SNAPSHOT
Build Number: 73a33d5