NSX: After failed deploy Configure disks option doesn't show anything
Bug #1399591 reported by
Tatyana Dubyk
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Invalid
|
Medium
|
Fuel Python (Deprecated) | ||
| 6.0.x |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
Bug Description
1. create lab from 5.1.1-48.iso
2. create env with configuration:
centos, ha, qemu, nsx plugin, storages by default
3. in settings tab
NSX_USERNAME= admin
NSX_PASSWORD= admin
NSX_TRANSPORT_ZONE= 0f12c1f7-
L3_SERVICE_UUID= aa153851-
NSX_CONTROLLER_
URL_TO_NSX_BITS= http://
4.NSX network -> management ->
untag and set 172.16.1.0/24 on eth2
5. Node with roles:
3 controllers
1 compute
1 cinder
6. Click on deploy
7. Error appears about that there not enough space for cinder on controller
8. Click on first controller and select "configure disks"
9. There is nothing to configure - disks info not shown.
Revision history for this message
| Tatyana Dubyk (tdubyk) wrote | #1 |
Revision history for this message
| Tatyana Dubyk (tdubyk) wrote | #2 |
| description: | updated |
| Changed in fuel: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Fuel Python Team (fuel-python) |
| status: | New → Confirmed |
| Changed in fuel: | |
| milestone: | none → 5.1.2 |
| tags: | added: nsx partner |
Revision history for this message
| Andrey Danin (gcon-monolake) wrote | #3 |
| summary: |
- NSX. After failed deploy Configure disks option doesn't show anything + NSX: After failed deploy Configure disks option doesn't show anything |
Revision history for this message
| Dmitry Pyzhov (dpyzhov) wrote | #4 |
| Changed in fuel: | |
| milestone: | 5.1.2 → 7.0 |
| tags: | added: volumes |
Revision history for this message
| Aleksey Kasatkin (alekseyk-ru) wrote | #5 |
| Changed in fuel: | |
| milestone: | 7.0 → 6.0.2 |
| Changed in fuel: | |
| assignee: | Fuel Python Team (fuel-python) → Fuel Partner Integration Team (fuel-partner) |
| assignee: | Fuel Partner Integration Team (fuel-partner) → Fuel Python Team (fuel-python) |
| milestone: | 6.0.2 → 6.1 |
| status: | Confirmed → Invalid |
| tags: |
added: module-volumes removed: volumes |
Revision history for this message
| Vitaly Sedelnik (vsedelnik) wrote | #6 |
To post a comment you must log in.
The node from the screenshot appears in logs as node-4 and node-12. Errors occurred when it was node-4.
Here are logs from VolumeManager with error: http://
The node has 3 disks with 50GB each. The node had 2 disks almost free but didn't allocate a space for the Volume Storage.