Controllers with small disks have issues adding new filesystems
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Stefan Dinescu |
Bug Description
Brief Description
-----------------
The default controller filesystem sizes are based on the underlying root disk size and currently targets a virtual disk and varying disk sizes (<120GB). The current small disk size is a lab specific restriction and is problematic when adding new file system since there is insufficient room to support all file systems. To simplify future changes the checks should be based on a small disk size (not virtual or physical) of only consider small disks that are <240GB or large disks (>240GB). This will simplify the logic to support the new lab restriction of disks that are 240GB and our standard deployment requirement of >500GB.
Severity
--------
Minor
Steps to Reproduce
------------------
n/a
Expected Behavior
------------------
It should be easy to add a new filesystem even on smaller disks
Actual Behavior
----------------
Sometimes the system prevents adding a new filesystem on smaller disks even when there is room.
Reproducibility
---------------
Reproducible on labs with smaller disks or on a virtual environment.
System Configuration
-------
Any system config where the controller is using a small disk
Branch/Pull Time/Commit
-------
n/a
Timestamp/Logs
--------------
n/a
Changed in starlingx: | |
assignee: | StefanF (stefan) → nobody |
assignee: | nobody → Stefan Dinescu (stefandinescu) |
Changed in starlingx: | |
importance: | Undecided → Medium |
summary: |
- Labs with small disks have issues adding new filesystems + Controllers with small disks have issues adding new filesystems |
tags: | added: stx.2018.10 |
tags: |
added: stx.1.0 removed: stx.2018.10 |
Fix proposed to branch: master /review. openstack. org/600743
Review: https:/