cloudbase-init

win2k16 extendvolumes plugin fails when cloudbase-init runs during specialize

Bug #1661725 reported by Adrian Vladu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloudbase-init
Fix Released
Undecided
Adrian Vladu

Bug Description

The WMI api used to enumerate volumes on 2016 is not available during the specialize step.
The wmi namespace in cause is '//./Root/Microsoft/Windows/Storage'

We need to fallback on win2k16 to the previous used storage management (VDS).

Adrian Vladu (avladu)
Changed in cloudbase-init:
assignee: nobody → Adrian Vladu (avladu)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cloudbase-init (master)

Reviewed: https://review.openstack.org/429020
Committed: https://git.openstack.org/cgit/openstack/cloudbase-init/commit/?id=ec8a8cd0d62af7fd8621a437ac19b0b294e62069
Submitter: Jenkins
Branch: master

commit ec8a8cd0d62af7fd8621a437ac19b0b294e62069
Author: Adrian Vladu <email address hidden>
Date: Fri Feb 3 22:04:27 2017 +0200

    Fix win2k16 extend volume during specialize

    The WMI api used to enumerate volumes on 2016 is not available during the
    specialize step.
    The WMI namespace in cause is '//./Root/Microsoft/Windows/Storage'

    We need to fallback on win2k16 to the previous used storage management (VDS).

    Change-Id: Ib082443c34dcba64697f165c9b2902f3f61c7e39
    Closes-bug: #1661725

Changed in cloudbase-init:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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