It is possible to assign more disk space to filesystems than physical disk has
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Medium
|
Dmitry Guryanov | ||
Mitaka |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) |
Bug Description
Using the fuel api it is possible to upload a disk configuration that gets used by Fuel but leads to a misconfiguration.
The resulting configuration has allocated more disk space to the filesystems than physically available on the disk.
Configuration:
Uploaded via API:
[
{
"name": "vda",
"size": 101708,
"id": "disk/by-
"volumes": [
{
}
],
"extra": []
}
]
Resulting disk configuration:
- extra: []
id: disk/by-
name: vda
size: 101708
volumes:
- keep_data: false
name: logs
size: 10240
- keep_data: false
name: mysql
size: 20480
- keep_data: false
name: os
size: 101708
See attached screenshot for disk configuration of node.
The expected behaviour would be that Fuel will give an error.
[root@fuel-70 ~]# fuel fuel-version
api: '1.0'
astute_sha: 6c5b73f93e24cc7
auth_required: true
build_id: '301'
build_number: '301'
feature_groups:
- experimental
- mirantis
fuel-agent_sha: 50e90af6e3d560e
fuel-library_sha: 5d50055aeca1dd0
fuel-nailgun-
fuel-ostf_sha: 2cd967dccd66cfc
fuelmain_sha: a65d453215edb02
nailgun_sha: 4162b0c15adb425
openstack_version: 2015.1.0-7.0
production: docker
python-
release: '7.0'
release_versions:
2015.1.0-7.0:
VERSION:
api: '1.0'
astute_sha: 6c5b73f93e24cc7
build_id: '301'
build_number: '301'
feature_
- experimental
- mirantis
fuel-
fuel-
fuel-
fuel-
fuelmain_sha: a65d453215edb02
nailgun_sha: 4162b0c15adb425
openstack
production: docker
python-
release: '7.0'
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
tags: | added: area-python |
Changed in fuel: | |
importance: | Undecided → Medium |
milestone: | none → 8.0-updates |
status: | New → Confirmed |
Changed in fuel: | |
milestone: | 8.0-updates → 8.0 |
tags: | added: module-volumes |
no longer affects: | fuel/newton |
We passed SCF in 8.0. Moving the bug to 9.0.