No this is not expected and may represent a misconfiguration or a bug. Something is returning a 404 when it shouldn’t. You might get more luck running the nova command with —debug to see what specifically is 404ing. You could also see if anything is reporting NotFound in the nova-consoleauth or nova-api or nova-compute logs
Vish On Oct 14, 2014, at 10:45 AM, Danny Choi (dannchoi) <[email protected]> wrote: > Hi, > > 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:~/devstack$ nova hypervisor-servers q > +--------------------------------------+-------------------+---------------+---------------------+ > | ID | Name | Hypervisor ID | > Hypervisor Hostname | > +--------------------------------------+-------------------+---------------+---------------------+ > | 48b16e7c-0a17-42f8-9439-3146f26b4cd8 | instance-0000000e | 1 | > qa4 | > | 3eadf190-465b-4e90-ba49-7bc8ce7f12b9 | instance-0000000f | 1 | > qa4 | > | 056d4ad2-e081-4706-b7d1-84ee281e65fc | instance-00000010 | 2 | > qa5 | > +--------------------------------------+-------------------+---------------+---------------------+ > localadmin@qa4:~/devstack$ nova list > +--------------------------------------+------+--------+------------+-------------+---------------------------------+ > | ID | Name | Status | Task State | Power > State | Networks | > +--------------------------------------+------+--------+------------+-------------+---------------------------------+ > | 3eadf190-465b-4e90-ba49-7bc8ce7f12b9 | vm1 | ACTIVE | - | Running > | private=10.0.0.17 | > | 48b16e7c-0a17-42f8-9439-3146f26b4cd8 | vm2 | ACTIVE | - | Running > | private=10.0.0.16, 172.29.173.4 | > | 056d4ad2-e081-4706-b7d1-84ee281e65fc | vm3 | ACTIVE | - | Running > | private=10.0.0.18, 172.29.173.5 | > +--------------------------------------+------+--------+------------+-------------+---------------------------------+ > localadmin@qa4:~/devstack$ nova get-vnc-console vm3 novnc > ERROR (CommandError): No server with a name or ID of 'vm3' exists. > <<<<<<<[ERROR] > > > This does not happen if the VM resides at the Controlller (qa5). > > localadmin@qa4:~/devstack$ nova get-vnc-console vm2 novnc > +-------+-------------------------------------------------------------------------------------+ > | Type | Url > | > +-------+-------------------------------------------------------------------------------------+ > | novnc | > http://172.29.172.161:6080/vnc_auto.html?token=f556dea2-125d-49ed-bfb7-55a9a7714b2e > | > +-------+-------------------------------------------------------------------------------------+ > > Is this expected behavior? > > Thanks, > Danny > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
