Storage group type conversion getting failed

Bug #1837464 reported by sathish subramanian
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Invalid
Low
Bob Church

Bug Description

Brief Description
-----------------
This test validates that the user can convert between different storage types. But when modifying instance_backing as image type conversion using system host-lvg-modify getting error.

Severity
--------
Provide the severity of the defect.
Critical: System/Feature is not usable due to the defect

Steps to Reproduce
------------------
 1. Lock a worker that is hosting VMs
 2. Modify the worker nova-local backend from remote storage to image.
CMD:
 system host-lvg-modify -b image compute-0 nova-local
Error:
 system: error: unrecognized arguments: -b nova-local

So let me know, what is the alternate command for remote to image type change?

Expected Behavior
------------------
It should be possible to modify the nova-local backend

Actual Behavior
----------------
system: error: unrecognized arguments: -b nova-local

Reproducibility
---------------
Reproducible/100%
System Configuration
--------------------
- MN-External (2+2+2)

Branch/Pull Time/Commit
-----------------------
BUILD_DATE="2019-07-18 01:30:00 +0000"

Test Activity
-------------
Feature Testing, Regression Testing

Revision history for this message
Bob Church (rchurch) wrote :

Current help text from the command shows this option has been removed.

[sysadmin@controller-0 ~(keystone_admin)]$ system help host-lvg-modify
usage: system host-lvg-modify [-l <lvm_type>]
                              <hostname or id> <lvg name or uuid>Modify the attributes of a Local Volume Group.

Positional arguments:
  <hostname or id> Name or ID of the host [REQUIRED]
  <lvg name or uuid> Name or UUID of lvg [REQUIRED]

Optional arguments:
  -l <lvm_type>, --lvm_type <lvm_type>
                        Determines the thick or thin provisioning format of
                        the LVM volume group. [cinder-volumes]

We currently support local ephemeral storage (QCOW2) image backing by default on a compute worker. The other option is to use RBD backed ephemeral storage from the Ceph cluster. To do this, you need to lock the compute worker and add a Kubernetes label 'remote-storage'(system host-label-assign <worker> remote-storage=enabled) and unlock.

Revision history for this message
Ghada Khalil (gkhalil) wrote :

Marking as Invalid based on Bob's comment above

tags: added: stx.storage
Changed in starlingx:
importance: Undecided → Low
assignee: nobody → Bob Church (rchurch)
status: New → Invalid
Revision history for this message
sathish subramanian (sathis5x) wrote :

Is there any option to modify compute nova-local backend types ?
Note: This CLI not supported(system host-lvg-modify -b remote compute-0 nova-local)
As per commands above, used below steps for label assignment to compute.
And It is not changing nova-local backend.

 >> system host-lock compute-0
 >> system host-lock compute-1
 >> system host-label assign compute-0 remote-storage=enabled
 >> system host-label assign compute-1 remote-storage=enabled
 >> System unlock compute-0
 >> System unlock compute-1

 To remove remote-storage label list from compute-1 and add image label
 >> system host-label-remove compute-1 remote-storage
 >> system host-label-assign compute-1 image=enabled
 >> unlock compute-1

Expected behavior of the test:
 Modify the worker nova-local backend from remote storage to image

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.