public-address change to internal bridge post juju-upgrade

[James Page]

After upgrading a running openstack deployment from 1.17.7 to 1.18.0, the private address on the compute nodes changed to the internal libvirt bridge:

environment: jamespage
machines:
  "12":
    agent-state: started
    agent-version: 1.18.0
    dns-name: 192.168.122.1
    instance-id: f682e0f4-d4c1-4995-b461-5339f7680ef5
    instance-state: ACTIVE
    series: trusty
    hardware: arch=amd64 cpu-cores=2 mem=4096M root-disk=40960M
  "13":
    agent-state: started
    agent-version: 1.18.0
    dns-name: 192.168.122.1
    instance-id: 3da6fd73-92e8-456a-8aca-a0c3e6dc7471
    instance-state: ACTIVE
    series: trusty
    hardware: arch=amd64 cpu-cores=2 mem=4096M root-disk=40960M
  "14":
    agent-state: started
    agent-version: 1.18.0
    dns-name: 192.168.122.1
    instance-id: 201fcec6-984e-4456-9b9b-115c3949a77e
    instance-state: ACTIVE
    series: trusty
    hardware: arch=amd64 cpu-cores=2 mem=4096M root-disk=40960M
services:
  ceilometer-agent:
    charm: local:trusty/ceilometer-agent-20
    exposed: false
    relations:
      ceilometer-service:
      - ceilometer
      nova-ceilometer:
      - nova-compute
    subordinate-to:
    - nova-compute
  nova-compute:
    charm: local:trusty/nova-compute-132
    exposed: false
    relations:
      amqp:
      - rabbitmq-server
      ceph:
      - ceph
      cloud-compute:
      - nova-cloud-controller
      compute-peer:
      - nova-compute
      image-service:
      - glance
      nova-ceilometer:
      - ceilometer-agent
      shared-db:
      - mysql
    units:
      nova-compute/0:
        agent-state: started
        agent-version: 1.18.0
        machine: "12"
        public-address: 192.168.122.1
        subordinates:
          ceilometer-agent/0:
            upgrading-from: local:trusty/ceilometer-agent-20
            agent-state: started
            agent-version: 1.18.0
            public-address: 192.168.122.1
      nova-compute/1:
        agent-state: started
        agent-version: 1.18.0
        machine: "13"
        public-address: 192.168.122.1
        subordinates:
          ceilometer-agent/2:
            upgrading-from: local:trusty/ceilometer-agent-20
            agent-state: started
            agent-version: 1.18.0
            public-address: 192.168.122.1
      nova-compute/2:
        agent-state: started
        agent-version: 1.18.0
        machine: "14"
        public-address: 192.168.122.1
        subordinates:
          ceilometer-agent/1:
            upgrading-from: local:trusty/ceilometer-agent-20
            agent-state: started
            agent-version: 1.18.0
            public-address: 192.168.122.1

[James Page (james-page)]

machine log - http://paste.ubuntu.com/7216535/

[James Page (james-page)]

unit log - http://paste.ubuntu.com/7216537/

[Launchpad Janitor (janitor)]

This bug was fixed in the package juju-core - 1.18.1-0ubuntu1

---------------
juju-core (1.18.1-0ubuntu1) trusty; urgency=medium

  * New upstream point release, including fixes for:
    - Upgrading juju 1.16.6 -> 1.18.x fails (LP: #1299802).
    - Peer relation disappears during juju-upgrade (LP: #1303697).
    - public-address of units changes to internal bridge post upgrade
      (LP: #1303735).
    - Unable to deploy local charms without series (LP: #1303880).
    - juju scp no longer allows multiple extra arguments to be passed
      (LP: #1306208).
    - juju cannot downgrade to same major.minor version with earlier
      patch number (LP: #1306296).
 -- James Page <email address hidden> Sat, 12 Apr 2014 07:04:37 +0100