node can't be list by magnumclient

Bug #1446198 reported by FenghuaFang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Medium
Hua Wang

Bug Description

I success to create the bay which has two nodes.
The node can be fount by "nova list".

But when i issue the "magnum node-list", no any node is listed.

"
[stack@localhost magnum(keystone_admin)]$ magnum bay-list
+--------------------------------------+------------+------------+-----------------+
| uuid | name | node_count | status |
+--------------------------------------+------------+------------+-----------------+
| b24059e7-6f33-4f23-aa42-e7dea5f7f3cd | testbay100 | 2 | CREATE_COMPLETE |
+--------------------------------------+------------+------------+-----------------+
[stack@localhost magnum(keystone_admin)]$ magnum node-list
+------+------+----------+
| uuid | type | image_id |
+------+------+----------+
+------+------+----------+
[stack@localhost magnum(keystone_admin)]$ sudo virsh list
 Id Name State
----------------------------------------------------
 5 instance-00000004 running
 6 instance-00000005 running
 7 instance-00000006 running

[stack@localhost magnum(keystone_admin)]$ nova list
+--------------------------------------+-------------------------------------------------------+--------+------------+-------------+--------------------------------------------------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------------------------------------------------------+--------+------------+-------------+--------------------------------------------------------------------------+
| 4ecee3f7-c870-48a3-aba2-b0adb4ec56f4 | te-4e2g3i4wewyw-0-52p5ctz4gtch-kube_node-kqrpzt75twcy | ACTIVE | - | Running | testbay100-owitpilme5u5-fixed_network-7bdfzpua3icd=10.0.0.4, 172.24.4.11 |
| b4bc8db2-1cf2-43a9-844a-a7610eb6cfd6 | te-4e2g3i4wewyw-1-py6q6tggep3q-kube_node-zfrbpz2ks6ow | ACTIVE | - | Running | testbay100-owitpilme5u5-fixed_network-7bdfzpua3icd=10.0.0.5, 172.24.4.12 |
| 3d608162-818f-4bee-bf3c-6675e6758900 | testbay100-owitpilme5u5-kube_master-5t7pqeqipgqq | ACTIVE | - | Running | testbay100-owitpilme5u5-fixed_network-7bdfzpua3icd=10.0.0.3, 172.24.4.10 |
+--------------------------------------+-------------------------------------------------------+--------+------------+-------------+--------------------------------------------------------------------------+
"

Changed in magnum:
assignee: nobody → FenghuaFang (449171342-q)
Steven Dake (sdake)
Changed in magnum:
status: New → Confirmed
importance: Undecided → Medium
Hua Wang (humble00)
Changed in magnum:
assignee: FenghuaFang (449171342-q) → Hua Wang (humble00)
Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
Revision history for this message
Hua Wang (humble00) wrote :

node is removed from magnum now, so this bug is fixed.

Changed in magnum:
status: Confirmed → Fix Committed
Changed in magnum:
status: Fix Committed → Fix Released
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.