[Bug 1581598] Re: ipv6 enabled charms don't understand mngtmpaddr flag

[James Page]

** Changed in: ceilometer (Juju Charms Collection)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to cinder in Juju Charms Collection.
Matching subscriptions: charm-bugs
https://bugs.launchpad.net/bugs/1581598

Title:
  ipv6 enabled charms don't understand mngtmpaddr flag

Status in Charm Helpers:
  Fix Committed
Status in ceilometer package in Juju Charms Collection:
  Fix Released
Status in ceph package in Juju Charms Collection:
  Fix Committed
Status in ceph-mon package in Juju Charms Collection:
  Fix Committed
Status in ceph-osd package in Juju Charms Collection:
  Fix Committed
Status in ceph-radosgw package in Juju Charms Collection:
  Fix Committed
Status in cinder package in Juju Charms Collection:
  Fix Committed
Status in glance package in Juju Charms Collection:
  Fix Committed
Status in heat package in Juju Charms Collection:
  Fix Committed
Status in keystone package in Juju Charms Collection:
  Fix Committed
Status in neutron-api package in Juju Charms Collection:
  Fix Committed
Status in nova-cloud-controller package in Juju Charms Collection:
  Fix Committed
Status in nova-compute package in Juju Charms Collection:
  Fix Committed
Status in openstack-dashboard package in Juju Charms Collection:
  Fix Committed
Status in percona-cluster package in Juju Charms Collection:
  Fix Committed
Status in rabbitmq-server package in Juju Charms Collection:
  Fix Committed
Status in swift-proxy package in Juju Charms Collection:
  Fix Committed
Status in swift-storage package in Juju Charms Collection:
  Fix Committed

Bug description:
  In Xenial if you are have an ipv6 address that was created following
  an RA receive it may have the "mngtmpaddr" and/or "noprefixroute" flag
  set e.g.

  2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
      link/ether fa:16:3e:e2:e2:56 brd ff:ff:ff:ff:ff:ff
      inet 10.5.32.212/16 brd 10.5.255.255 scope global ens3
         valid_lft forever preferred_lft forever
      inet6 2001:db8:0:1:f816:3eff:fee2:e256/64 scope global mngtmpaddr dynamic 
         valid_lft 86397sec preferred_lft 14397sec
      inet6 fe80::f816:3eff:fee2:e256/64 scope link 
         valid_lft forever preferred_lft forever

  The charms do not currently parse this properly when validating ipv6
  addresses which causes xenial ipv6 deployments to fail.

  Looks like this has actually been around since Utopic timeframe - more
  info here - http://lists.openwall.net/netdev/2013/12/06/138

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-helpers/+bug/1581598/+subscriptions