1

I have openstack-dashboard installed from openstack-base in a MAAS environment and it seems to be working for almost everything. I can view and change networks/routers/ports and start an instance. I have an instance with a floating IP that I can ping and telnet to the ssh port. ssh ubuntu@floatingip connects and then times out.

Trying to access the console from the dashboard returns: console is currently unavailable. Please try again later.

When I do "juju ssh x" to the nova-compute node where my instance is running, a virst list returns:

 Id    Name                           State
----------------------------------------------------
 5     instance-00000002              running

but virsh console 5 returns:

Connected to domain instance-00000002
Escape character is ^]
error: internal error: character device <null> is not using a PTY

I have verified that nova-authconsole is up and running.

When I look at /var/lib/instances/{instance}/console.log it shows a full console log and everything from the boot up looks correct. nova-cloud-controller has console-access-protocl set to novnc. console-proxy-ip is set to local.

I suspect that all three methods of trying to access the instance are caused by a single failure, but don't know where else to look for it.

Any ideas of how to track this one down?

3
  • If you ssh into the compute node (juju ssh nova-compute/X), what do you get when running "ps aux | grep vnc"?, it should match the qemu process for your VM, if you get an empty output then that means qemu didn't launch the VM with vnc enabled and you need to run "nova stop ID" and "nova start ID" ("nova reboot" won't work as it won't stop/start the qemu process with the new command line arguments) Nov 13, 2015 at 17:04
  • Yes, qemu is running with "-vnc 0.0.0:0". Nov 18, 2015 at 15:06
  • I am not sure what I did. vnc /novnc started working while I was playing with different MTU sizes. The MTU settings are all back to normal, but the console access continues to work. Nov 24, 2015 at 3:04

1 Answer 1

0

Did you enable console access in the nova-cloud-controller charm? The configuration key is called console-access-protocol:

Protocol to use when accessing virtual machine console. Supported types
are None, spice, xvpvnc, novnc and vnc (for both xvpvnc and novnc)
2
  • yes, I have it set to novnc. I suspect that it may have something to do with mtu. I saw this in another post, askubuntu.com/questions/486151/…. I started playing with values and the console started working along with inbound networking, but not outbound network access. Then everything went to hell in a handbasket and I am trying to sort through which settings to use and which to discard. I am now back to console access without any network access. Nov 9, 2015 at 17:44
  • Also note that it only applies to instances started after the config change. Nov 12, 2015 at 13:17

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .