yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #23776
[Bug 1381568] [NEW] Cannot start the VM console when VM is launched at Compute node
Public bug reported:
OpenStack version: Juno
localadmin@qa4:/etc/nova$ nova-manage version
2015.1
I used devstack to deploy multi-node OpenStack, with Controller + nova-compute + Network on one physical node (qa4),
and Compute on a separate physical node (qa5).
When I launch a VM which spun up on the Compute node (qa5), I cannot
launch the VM console, in both CLI and Horizon.
localadmin@qa4:/etc/nova$ nova list
+--------------------------------------+------+--------+------------+-------------+-------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+------+--------+------------+-------------+-------------------+
| 86c3519d-cd22-4cc9-bac7-6444749ff41b | vm1 | ACTIVE | - | Running | private=10.0.0.6 |
| 1642393c-edce-4af2-837c-ca61d464688b | vm5 | ACTIVE | - | Running | private=10.0.0.10 |
+--------------------------------------+------+--------+------------+-------------+-------------------+
localadmin@qa4:/etc/nova$ nova get-vnc-console vm5 novnc
ERROR (BadRequest): Unavailable console type novnc. (HTTP 400) (Request-ID: req-f5944644-46ae-4051-b0cb-7562f1308893)
localadmin@qa4:/etc/nova$ nova get-vnc-console vm5 xvpvnc
ERROR (BadRequest): Unavailable console type xvpvnc. (HTTP 400) (Request-ID: req-3416985d-0b76-4a31-9e48-cc597e8698eb)
This does not happen if the VM resides at the Controlller (qa5).
localadmin@qa4:/etc/nova$ nova get-vnc-console vm1 novnc
+-------+-------------------------------------------------------------------------------------+
| Type | Url |
+-------+-------------------------------------------------------------------------------------+
| novnc | http://172.29.172.161:6080/vnc_auto.html?token=0abd9c75-4a81-4bd2-a802-785dab61c82a |
+-------+-------------------------------------------------------------------------------------+
localadmin@qa4:/etc/nova$ nova get-vnc-console vm1 xvpvnc
+--------+-------------------------------------------------------------------------------+
| Type | Url |
+--------+-------------------------------------------------------------------------------+
| xvpvnc | http://172.29.172.161:6081/console?token=c2cb837f-e4ca-4347-8661-32e55f8adf06 |
+--------+-------------------------------------------------------------------------------+
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1381568
Title:
Cannot start the VM console when VM is launched at Compute node
Status in OpenStack Compute (Nova):
New
Bug description:
OpenStack version: Juno
localadmin@qa4:/etc/nova$ nova-manage version
2015.1
I used devstack to deploy multi-node OpenStack, with Controller + nova-compute + Network on one physical node (qa4),
and Compute on a separate physical node (qa5).
When I launch a VM which spun up on the Compute node (qa5), I cannot
launch the VM console, in both CLI and Horizon.
localadmin@qa4:/etc/nova$ nova list
+--------------------------------------+------+--------+------------+-------------+-------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+------+--------+------------+-------------+-------------------+
| 86c3519d-cd22-4cc9-bac7-6444749ff41b | vm1 | ACTIVE | - | Running | private=10.0.0.6 |
| 1642393c-edce-4af2-837c-ca61d464688b | vm5 | ACTIVE | - | Running | private=10.0.0.10 |
+--------------------------------------+------+--------+------------+-------------+-------------------+
localadmin@qa4:/etc/nova$ nova get-vnc-console vm5 novnc
ERROR (BadRequest): Unavailable console type novnc. (HTTP 400) (Request-ID: req-f5944644-46ae-4051-b0cb-7562f1308893)
localadmin@qa4:/etc/nova$ nova get-vnc-console vm5 xvpvnc
ERROR (BadRequest): Unavailable console type xvpvnc. (HTTP 400) (Request-ID: req-3416985d-0b76-4a31-9e48-cc597e8698eb)
This does not happen if the VM resides at the Controlller (qa5).
localadmin@qa4:/etc/nova$ nova get-vnc-console vm1 novnc
+-------+-------------------------------------------------------------------------------------+
| Type | Url |
+-------+-------------------------------------------------------------------------------------+
| novnc | http://172.29.172.161:6080/vnc_auto.html?token=0abd9c75-4a81-4bd2-a802-785dab61c82a |
+-------+-------------------------------------------------------------------------------------+
localadmin@qa4:/etc/nova$ nova get-vnc-console vm1 xvpvnc
+--------+-------------------------------------------------------------------------------+
| Type | Url |
+--------+-------------------------------------------------------------------------------+
| xvpvnc | http://172.29.172.161:6081/console?token=c2cb837f-e4ca-4347-8661-32e55f8adf06 |
+--------+-------------------------------------------------------------------------------+
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1381568/+subscriptions
Follow ups
References