Image is not available when launch instance

Bug #1710890 reported by Kairat Kushaev
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Critical
Kairat Kushaev

Bug Description

it was reproduced against master.
Steps to reproduce:
1. Go to Horizon-> Images under admin
2. Create public image of any type
3. push [Launch] button on created image.
4. go to source tab.
5. Choose Boot source= Image
6. Try to find image created in "Select one" table
AR: created image is not listed in the table
ER: created image is available in the table.

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/495141

Changed in horizon:
assignee: nobody → Kairat Kushaev (kkushaev)
status: New → In Progress
Revision history for this message
Eugene C (hw.ewchan) wrote :

The image should be pre-selected in the 'Allocated' section of 'Source' tab when Launch Instance is launched from Images page.

Revision history for this message
Kairat Kushaev (kkushaev) wrote :

So it was not,seems that the problem with racy watchers

Changed in horizon:
importance: Undecided → Critical
Changed in horizon:
milestone: none → pike-rc3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/495141
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=48862eb9b7f5789dee3362d9103416628c5d3e76
Submitter: Jenkins
Branch: master

commit 48862eb9b7f5789dee3362d9103416628c5d3e76
Author: kairat_kushaev <email address hidden>
Date: Fri Aug 18 13:30:59 2017 +0400

    do not flush selection on "old" boot source

    This fixes an issue introduced by watchers:
    when page initialized images watchers called before
    select boot source watcher.it leads to sutiation when
    we specify selection from user input and flush it on
    updateBootSource. as a result page come to
    inconsistent state described in the bug.
    Perhaps, this requires big refactoring but in the
    current patch we do not flush selection if boot type
    was not changed. it allows to use image, snapshot,
    volume from context as ctrl.selection.

    Change-Id: I4b23071a2a9e2c02cc1f46713165e5cb5155894f
    Closes-Bug: #1710890

Changed in horizon:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/498465

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (stable/pike)

Reviewed: https://review.openstack.org/498465
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=2fe66f444a35914009a275f7b8880ad12bc062d6
Submitter: Jenkins
Branch: stable/pike

commit 2fe66f444a35914009a275f7b8880ad12bc062d6
Author: kairat_kushaev <email address hidden>
Date: Fri Aug 18 13:30:59 2017 +0400

    do not flush selection on "old" boot source

    This fixes an issue introduced by watchers:
    when page initialized images watchers called before
    select boot source watcher.it leads to sutiation when
    we specify selection from user input and flush it on
    updateBootSource. as a result page come to
    inconsistent state described in the bug.
    Perhaps, this requires big refactoring but in the
    current patch we do not flush selection if boot type
    was not changed. it allows to use image, snapshot,
    volume from context as ctrl.selection.

    Change-Id: I4b23071a2a9e2c02cc1f46713165e5cb5155894f
    Closes-Bug: #1710890
    (cherry picked from commit 48862eb9b7f5789dee3362d9103416628c5d3e76)

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 12.0.0.0rc3

This issue was fixed in the openstack/horizon 12.0.0.0rc3 release candidate.

Revision history for this message
Eugene C (hw.ewchan) wrote :

Could we get the fix ported to ocata release as well?

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 13.0.0.0b1

This issue was fixed in the openstack/horizon 13.0.0.0b1 development milestone.

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

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/598571

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (stable/ocata)

Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/598571
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 merged to horizon (stable/ocata)

Reviewed: https://review.openstack.org/598571
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=2ee37e5ad17204650b99ad981f84dbf2c06ad5d4
Submitter: Zuul
Branch: stable/ocata

commit 2ee37e5ad17204650b99ad981f84dbf2c06ad5d4
Author: kairat_kushaev <email address hidden>
Date: Fri Aug 18 13:30:59 2017 +0400

    do not flush selection on "old" boot source

    This fixes an issue introduced by watchers:
    when page initialized images watchers called before
    select boot source watcher.it leads to sutiation when
    we specify selection from user input and flush it on
    updateBootSource. as a result page come to
    inconsistent state described in the bug.
    Perhaps, this requires big refactoring but in the
    current patch we do not flush selection if boot type
    was not changed. it allows to use image, snapshot,
    volume from context as ctrl.selection.

    Change-Id: I4b23071a2a9e2c02cc1f46713165e5cb5155894f
    Closes-Bug: #1710890
    (cherry picked from commit 48862eb9b7f5789dee3362d9103416628c5d3e76)

tags: added: in-stable-ocata
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon ocata-eol

This issue was fixed in the openstack/horizon ocata-eol release.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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