radvd not starting with IPv6 subnets
Bug #1556204 reported by
Major Hayden
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack-Ansible |
Invalid
|
Medium
|
Major Hayden | ||
Bug Description
Now that radvd is installed in neutron agents containers (see bug #1492080), it doesn't actually start up when it should. According to neutron docs, radvd should start when a network subnet is added with ipvs_address_mode set to `slaac` and ipv6_ra_mode set to `slaac`. That's not the case.
To test:
neutron subnet-create --ip-version 6 --gateway <v6-gateway-
Nothing provides SLAAC functionality at this point, so virtual machines don't know which IPv6 addresses they should have.
This affects Liberty for sure, and possibly Mitaka.
| Changed in openstack-ansible: | |
| assignee: | nobody → Major Hayden (rackerhacker) |
| Changed in openstack-ansible: | |
| milestone: | none → 13.0.0 |
| Changed in openstack-ansible: | |
| milestone: | 13.0.0 → newton-1 |
| Changed in openstack-ansible: | |
| status: | New → Triaged |
| Changed in openstack-ansible: | |
| milestone: | newton-1 → newton-3 |
Revision history for this message
| Major Hayden (rackerhacker) wrote | #1 |
| Changed in openstack-ansible: | |
| status: | Triaged → Invalid |
| Changed in openstack-ansible: | |
| milestone: | newton-3 → none |
To post a comment you must log in.
Neutron moved away from this and started using dnsmasq for everything. This bug is irrelevant now. ;)