When launching an instance, the initial message should say "Launch Scheduled"

Bug #1287051 reported by tinytmy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Low
Vishal Manchanda

Bug Description

when launch instance failure,first the message is Success ,then appear a error message.
I think change the success message to info message is much better.

Revision history for this message
tinytmy (tangmeiyan77) wrote :
Revision history for this message
tinytmy (tangmeiyan77) wrote :
Changed in horizon:
assignee: nobody → tinytmy (tangmeiyan77)
Revision history for this message
tinytmy (tangmeiyan77) wrote :

When instances is active and running in the compute node,then can pop a success message.

Akihiro Motoki (amotoki)
Changed in horizon:
status: New → Confirmed
milestone: none → juno-1
importance: Undecided → Medium
Julie Pichon (jpichon)
Changed in horizon:
milestone: juno-1 → juno-2
Changed in horizon:
milestone: juno-2 → juno-3
Thierry Carrez (ttx)
Changed in horizon:
milestone: juno-3 → juno-rc1
David Lyle (david-lyle)
Changed in horizon:
milestone: juno-rc1 → kilo-1
Thierry Carrez (ttx)
Changed in horizon:
milestone: kilo-1 → kilo-2
David Lyle (david-lyle)
Changed in horizon:
milestone: kilo-2 → kilo-3
Thierry Carrez (ttx)
Changed in horizon:
milestone: kilo-3 → kilo-rc1
David Lyle (david-lyle)
Changed in horizon:
milestone: kilo-rc1 → liberty-1
tags: added: kilo-rc-potential
David Lyle (david-lyle)
tags: removed: kilo-rc-potential
Rock (rockme004)
Changed in horizon:
assignee: tinytmy (tangmeiyan77) → Rock (rockme004)
Changed in horizon:
milestone: liberty-1 → liberty-2
Changed in horizon:
milestone: liberty-2 → liberty-3
Thierry Carrez (ttx)
Changed in horizon:
milestone: liberty-3 → liberty-rc1
David Lyle (david-lyle)
Changed in horizon:
milestone: liberty-rc1 → none
assignee: Rock (rockme004) → nobody
Kent Wang (k.wang)
Changed in horizon:
assignee: nobody → Kent Wang (k.wang)
Revision history for this message
Kent Wang (k.wang) wrote :

Hi any steps to reproduce? Thanks

Revision history for this message
Timur Sufiev (tsufiev-x) wrote :

Checked it again on Mitaka release. I'm no longer seeing double message in case of insufficient Nova resources, but the initial message indeed should be less promising. Submitting a form to Horizon doesn't mean that VM was successfully launched, it just means that the launch was scheduled.

Kent, are you going to fix that unclear message?

Revision history for this message
Gary W. Smith (gary-w-smith) wrote :

Unassigning due to inactivity

Changed in horizon:
assignee: Kent Wang (k.wang) → nobody
summary: - when launch instance failure,first the message is Success ,then appear a
- error message
+ When launching an instance, the initial message should say "Launch
+ Scheduled"
Ying Zuo (yingzuo)
tags: added: low-hanging-fruit
Changed in horizon:
importance: Medium → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/513518

Changed in horizon:
assignee: nobody → Trygve Vea (trygve-vea-gmail)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (master)

Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/513518
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/632990

Changed in horizon:
assignee: Trygve Vea (trygve-vea-gmail) → Vishal Manchanda (vishalmanchanda)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/632990
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=787ede8d94f2f1e0ef686f7df48040a26fea067f
Submitter: Zuul
Branch: master

commit 787ede8d94f2f1e0ef686f7df48040a26fea067f
Author: manchandavishal <email address hidden>
Date: Thu Jan 24 11:40:08 2019 +0000

    Clarify instance state after launch submission

    After submitting a launch instance-workflow, an instance is technically
    only scheduled for launch - and not yet actually launched. This patch
    reflects this in the message presented in the top right corner.

    Closes-Bug: #1287051

    Change-Id: Ie86e61c0db561eeb64101c55d304b07191f33ea8
    Co-Authored-By: Trygve Vea <email address hidden>

Changed in horizon:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 15.0.0.0b2

This issue was fixed in the openstack/horizon 15.0.0.0b2 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.