Ubuntu OpenStack Single-Server Install network connectivity between host and main OpenStack container fails after reboot

asked 2015-09-14 10:37:24 -0500

AlexV gravatar image

I setup the Canonical distribution of openstack using the single server method, so that I could learn OpenStack before having to deploy and maintain it in production. I'm running into an issue with single server installation after a reboot of the main host that runs the primary LXC container that the openstack services run nested under. After a reboot, I'm no longer able to ping or ssh to any of the nested containers running within the main container. In order to connect to any of those machines, I first need to lxc-attach -n openstack-single-root, then I'm able to ssh to any other container from there.

Here is the output of the juju status:

ubuntu@openstack-single-root:~$ juju status
environment: local
machines:
  "0":
    agent-state: started
    agent-version: 1.24.5.1
    dns-name: localhost
    instance-id: localhost
    series: trusty
    state-server-member-status: has-vote
  "1":
    agent-state: started
    agent-version: 1.24.5.1
    instance-id: ubuntu-local-machine-1
    series: trusty
    containers:
      1/lxc/0:
        agent-state: started
        agent-version: 1.24.5.1
        dns-name: 10.0.6.53
        instance-id: ubuntu-local-machine-1-lxc-0
        series: trusty
        hardware: arch=amd64
      1/lxc/1:
        agent-state: started
        agent-version: 1.24.5.1
        dns-name: 10.0.6.24
        instance-id: ubuntu-local-machine-1-lxc-1
        series: trusty
        hardware: arch=amd64
      1/lxc/2:
        agent-state: started
        agent-version: 1.24.5.1
        dns-name: 10.0.6.105
        instance-id: ubuntu-local-machine-1-lxc-2
        series: trusty
        hardware: arch=amd64
      1/lxc/3:
        agent-state: started
        agent-version: 1.24.5.1
        dns-name: 10.0.6.222
        instance-id: ubuntu-local-machine-1-lxc-3
        series: trusty
        hardware: arch=amd64
      1/lxc/4:
        agent-state: started
        agent-version: 1.24.5.1
        dns-name: 10.0.6.94
        instance-id: ubuntu-local-machine-1-lxc-4
        series: trusty
        hardware: arch=amd64
      1/lxc/5:
        agent-state: started
        agent-version: 1.24.5.1
        dns-name: 10.0.6.188
        instance-id: ubuntu-local-machine-1-lxc-5
        series: trusty
        hardware: arch=amd64
      1/lxc/6:
        agent-state: started
        agent-version: 1.24.5.1
        dns-name: 10.0.6.49
        instance-id: ubuntu-local-machine-1-lxc-6
        series: trusty
        hardware: arch=amd64
      1/lxc/7:
        agent-state: started
        agent-version: 1.24.5.1
        dns-name: 10.0.6.64
        instance-id: ubuntu-local-machine-1-lxc-7
        series: trusty
        hardware: arch=amd64
    hardware: arch=amd64 cpu-cores=3 mem=6144M root-disk=20480M
  "2":
    agent-state: started
    agent-version: 1.24.5.1
    dns-name: 10.0.6.76
    instance-id: ubuntu-local-machine-2
    series: trusty
    hardware: arch=amd64 cpu-cores=1 mem=4096M root-disk=40960M
  "3":
    agent-state: started
    agent-version: 1.24.5.1
    dns-name: 10.0.6.25
    instance-id: ubuntu-local-machine-3
    series: trusty
    hardware: arch=amd64 cpu-cores=1 mem=2048M root-disk=20480M
  "4":
    agent-state: started
    agent-version: 1.24.5.1
    dns-name: 10.0.6.155
    instance-id: ubuntu-local-machine-4
    series: trusty
    hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
services:
  glance:
    charm: cs:trusty/glance-20
    can-upgrade-to: cs:trusty/glance-24
    exposed: false
    service-status:
      current: unknown
      since: 11 Sep 2015 14:17:47-04:00
    relations:
      amqp:
      - rabbitmq-server
      cluster:
      - glance
      identity-service:
      - keystone
      image-service:
      - nova-cloud-controller
      - nova-compute
      shared-db:
      - mysql
    units:
      glance/0:
        workload-status:
          current: unknown
          since: 11 Sep 2015 14:17:47-04:00
        agent-status:
          current: idle
          since: 14 Sep 2015 09:20:23-04:00
          version: 1.24.5.1
        agent-state: started
        agent-version: 1.24.5.1
        machine: 1/lxc/7
        open-ports:
        - 9292/tcp
        public-address: 10.0.6.64
  glance-simplestreams-sync ...
(more)
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-11-22 17:04:26 -0500

lmatter gravatar image

I ran into the same thing deploying kilo with openstack-install. I believe it is a known issue. https://github.com/Ubuntu-Solutions-Engineering/openstack-installer/issues/644#issuecomment-130664619 (This suggestion) allowed me to work around the issue.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-09-14 10:37:24 -0500

Seen: 600 times

Last updated: Sep 14 '15