Hi Sean, Thanks for the response. The configuration shared initially were of Kilo, below is the configuration we're using for Mitaka. We are not facing this issue on a single controller environment, its only hitting in HA environment.
Here is the nova.conf of one compute http://paste.ubuntu.com/18295909/ Do you think, this might be due to config issue in nova configuration file? openstack-dashboard: vip: "<DASHBOARD_VIP>" openstack-origin: "cloud:trusty-mitaka" hacluster-dashboard: cluster_count: 3 corosync_transport: unicast monitor_host: "<MONITOR_HOST_IP>" nova-compute: enable-live-migration: "True" enable-resize: "True" openstack-origin: "cloud:trusty-mitaka" migration-auth-type: "ssh" manage-neutron-plugin-legacy-mode: False nova-cloud-controller: network-manager: "Neutron" console-access-protocol: "novnc" openstack-origin: "cloud:trusty-mitaka" region: "serverstack" vip: "<NOVA_CC_VIP>" hacluster-nova-cc: cluster_count: 3 monitor_host: "<MONITOR_HOST_IP>" corosync_transport: unicast ** Changed in: nova Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550422 Title: Failed to connect to server(code:1006) - Console access issue To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1550422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
