Resize glance failing when done before controller-1 configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Daniel Badea |
Bug Description
Brief Description
-----------------
If a resize of the glance filesystem is done after controller-0 is configured but before controller-1 is configured then the resize fails to occur and services fail to stay enabled after the controller-0 reboot that is done as part of the resize procedure.
Severity
--------
Major: While the resize does work if done when both controller-0 and controller-1 are configured, if a user attempts to resize before controller-1 is configured the system becomes unusable as the services fail to enable.
Steps to Reproduce
------------------
1. install and config controller-0
2. unlock controller-0
3. increase glance storage size
4. after out-of-config is cleared, check glance storage size by 'system storage-usage-list' and 'df -h'
Expected Behavior
------------------
The glance filesystem should change to the new size and all services should go enabled.
Actual Behavior
----------------
The glance filesystem fails to resize and the services (as evidenced by sudo sm-dump command) fail to go enabled.
Reproducibility
---------------
100% reproducible
System Configuration
-------
All configurations except for the One Node System.
Branch/Pull Time/Commit
-------
Timestamp/Logs
--------------
tags: | added: stx.2018.10 stx.config |
Changed in starlingx: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Daniel Badea (daniel.badea) |
tags: |
added: stx.1.0 removed: stx.2018.10 |
Fix proposed to branch: master /review. openstack. org/596739
Review: https:/