Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1516838 - Empty "Started" date when VM started
Summary: Empty "Started" date when VM started
Keywords:
Status: POST
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: GA
: 5.11.0
Assignee: Yuri Rudman
QA Contact: Sudhir Mallamprabhakara
Red Hat CloudForms Documentation
URL:
Whiteboard: testathon
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-23 12:22 UTC by Imaan
Modified: 2019-03-28 15:22 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Category: ---
Cloudforms Team: ---


Attachments (Terms of Use)
Image describe the issue (deleted)
2017-11-23 12:22 UTC, Imaan
no flags Details
Start date is empty when state is finished (deleted)
2017-11-24 10:20 UTC, Imaan
no flags Details

Description Imaan 2017-11-23 12:22:40 UTC
Created attachment 1358176 [details]
Image describe the issue

Description of problem:

After starting VM, empty "Started" date is visible under tasks tab

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

5.9.0.9.20171115202245_7429f75

How reproducible:

Always

Steps to Reproduce:

1. Login to CloudForms Operational Portal

2. Navigate to Compute-> Infrastructure-> Virtual Machines-> Start any VM 

3. Click on Administrator|EVM -> Tasks

Actual results:

Displays empty the started date

Expected results:

It should display start date

Additional info:

Its not provider specific as tested on those VM's which belongs to VMware and AWS provider.

Comment 2 Dave Johnson 2017-11-23 12:44:13 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set the severity to Low.

Comment 3 Ladislav Smola 2017-11-24 09:32:08 UTC
Imaan: could you wait for a while until the state changes? This seem like a correct behavior, since the task has not been started yet (it's just queued for being processed). The started date means the task has been taken from a queue and execution started (so it will do the job of starting a VM)

If this is the case, please close as NOTABUG

Comment 4 Imaan 2017-11-24 10:17:43 UTC
Hi Ladislav,

I have checked again when the state "Finished", VM start date is still empty.

Thanks!

Comment 5 Imaan 2017-11-24 10:20:12 UTC
Created attachment 1358610 [details]
Start date is empty when state is finished

Comment 6 Dave Johnson 2017-11-24 10:43:59 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set the severity to Low.

Comment 11 CFME Bot 2019-02-28 19:45:58 UTC
New commit detected on ManageIQ/manageiq/master:

https://github.com/ManageIQ/manageiq/commit/420f92f7de7601115607d675e41925435e73e641
commit 420f92f7de7601115607d675e41925435e73e641
Author:     Yuri Rudman <yrudman@redhat.com>
AuthorDate: Wed Feb 27 17:19:14 2019 -0500
Commit:     Yuri Rudman <yrudman@redhat.com>
CommitDate: Wed Feb 27 17:19:14 2019 -0500

    adding miq_task_id to list of parameters when adding to MiqQueu will allow to automaticly update MiqTask#started_on when ueued item delivered
    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1516838

 app/models/mixins/process_tasks_mixin.rb | 1 +
 app/models/vm_or_template.rb | 2 +
 2 files changed, 3 insertions(+)


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