cinder does not show bootable flag consistently when when creating a volume w/ --poll

Bug #1855224 reported by Rajat Dhasmana
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-cinderclient
Fix Released
Undecided
Rajat Dhasmana

Bug Description

Description of problem:
$ cinder create 1 --image 0bad7436-9229-4609-953d-c425af2a2525 --poll
Shows “bootable: false”
Then immediately running “cinder show <id>” shows “bootable: true”.

Changed in python-cinderclient:
assignee: nobody → Rajat Dhasmana (whoami-rajat)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-cinderclient (master)

Fix proposed to branch: master
Review: https://review.opendev.org/697411

Changed in python-cinderclient:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-cinderclient (master)

Reviewed: https://review.opendev.org/697411
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=ceddb3cfd033661f63d1245a45e0e197561be19c
Submitter: Zuul
Branch: master

commit ceddb3cfd033661f63d1245a45e0e197561be19c
Author: whoami-rajat <email address hidden>
Date: Thu Dec 5 05:18:38 2019 +0000

    Fix: --poll inconsistency

    When we use `--poll` parameter with cinder create command, it waits
    for the volume to become available but doesn't update the data
    displayed to the user.
    Due to this, there are inconsistency between several parameters
    in the output after 'poll' and 'cinder show' command.
    Eg: cinder create 1 --image <image-id> --poll
    shows 'bootable' flag as false
    whereas, cinder show <vol-id>
    shows 'bootable' as true

    Change-Id: I1502e88f1cd84d225b75c07313e4eb252cc2d645
    Closes-Bug: #1855224

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

This issue was fixed in the openstack/python-cinderclient 6.0.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-cinderclient (stable/train)

Fix proposed to branch: stable/train
Review: https://review.opendev.org/709059

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-cinderclient (stable/train)

Reviewed: https://review.opendev.org/709059
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=8fa0882354c589b17d4502e04344ae00b75369d5
Submitter: Zuul
Branch: stable/train

commit 8fa0882354c589b17d4502e04344ae00b75369d5
Author: whoami-rajat <email address hidden>
Date: Thu Dec 5 05:18:38 2019 +0000

    Fix: --poll inconsistency

    When we use `--poll` parameter with cinder create command, it waits
    for the volume to become available but doesn't update the data
    displayed to the user.
    Due to this, there are inconsistency between several parameters
    in the output after 'poll' and 'cinder show' command.
    Eg: cinder create 1 --image <image-id> --poll
    shows 'bootable' flag as false
    whereas, cinder show <vol-id>
    shows 'bootable' as true

    Change-Id: I1502e88f1cd84d225b75c07313e4eb252cc2d645
    Closes-Bug: #1855224
    (cherry picked from commit ceddb3cfd033661f63d1245a45e0e197561be19c)

tags: added: in-stable-train
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-cinderclient 5.0.1

This issue was fixed in the openstack/python-cinderclient 5.0.1 release.

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.