keystone-manage db_sync fails in a dual-stacked environment

Bug #1275615 reported by Thiago Martins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Invalid
Low
Morgan Fainberg

Bug Description

Hello Stackers!

I'm trying to install IceHouse-2 in a dual-stacked environment (Ubuntu 14.04) but, "keystone-manage db_sync" doesn't work if db connection points to a IPv6 address, like this:

My /etc/network/interfaces contains:

---
# The loopback network interface
auto lo
iface lo inet loopback
iface lo inet6 loopback

auto eth0
# IPv6
iface eth0 inet6 static
        address 2001:1291:XXXX:fffa::aaaa
        netmask 64
        gateway 2001:1291:XXXX:fffa::1
       # dns-* options are implemented by the resolvconf package, if installed
        dns-search domain.com
        dns-nameservers 2001:4860:4860::8844

# IPv4
iface eth0 inet static
       address 192.168.XX.100
       netmask 24
       gateway 192.168.XX.1
       # dns-* options are implemented by the resolvconf package, if installed
       dns-nameservers 8.8.4.4 8.8.8.8
       dns-search domain.com
---

My /etc/hosts contains:

---
2001:1291:XXXX:fffa::aaaa controller-1.domain.com controller-1
192.168.XX.100 controller-1.domain.com controller-1
---

MySQL binds on both IPv4 and IPv6, my.cnf have this:

---
bind-address = ::
---

My /etc/keystone/keystone.conf contains:

---
connection = mysql://keystoneUser:<email address hidden>/keystone
---

But, this way, "keystone-manage db_sync" does not work and, if I replace keystone.conf connection line into this:

---
connection = mysql://keystoneUser:keystonePass@192.168.XX.100/keystone
---

Then, "keystone-manage db_sync" works! So, after db_sync finishes, I return it back to the FQDN, where it resolves to IPv6 address and it works fine (keystone user-list, etc, via IPv6)...

I tried it 3 times, always re-installing Ubuntu 14.04 from scratch, same result... "keystone-make db_sync" doesn't start its operations... I'll try again tomorrow, to see if it is just me, or not... =)

Best!
Thiago

Tags: ipv6
Dolph Mathews (dolph)
tags: removed: ipv4 lts openstack ubuntu
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

Hmm, what version of SQLAlchemy are you using?

Revision history for this message
Thiago Martins (martinx) wrote :

I'm using: "python-sqlalchemy 0.8.4-1"

Just plain Ubuntu 14.04 (fresh install) + IceHouse-2.

Dolph Mathews (dolph)
Changed in keystone:
milestone: none → icehouse-3
importance: Undecided → Medium
status: New → Triaged
Changed in keystone:
assignee: nobody → Morgan Fainberg (mdrnstm)
Revision history for this message
Morgan Fainberg (mdrnstm) wrote :

I've tried to duplicate this issue and have been unsuccessful in duplicating the problem. The caveat to my duplication attempts is that I have been unable to utilize 14.04 as it will not install in a VM. 14.04 is also (afaict) classified as alpha, meaning that I am unsure what the state of any package is. I have attempted to duplicate this problem ~3 times now, and keep ending with success.

With:

pip freeze | grep sql -i

MySQL-python==1.2.3
SQLAlchemy==0.8.5
sqlalchemy-migrate==0.8.2

I have consistently seen db_sync to an IPv6 address work.

Does this occur with a released version of Ubuntu? Is there anything else in the repro steps missing?

Changed in keystone:
status: Triaged → Incomplete
Changed in keystone:
importance: Medium → Low
Revision history for this message
Thiago Martins (martinx) wrote : Re: [Bug 1275615] Re: keystone-manage db_sync fails in a dual-stacked environment

I'll try it again tonight (max tomorrow), to make sure.

I tried it lots of times and every time I ended up with a frozen "db_sync"
when it resolves to an IPv6 address.

Tks for you time!

Regards,
Thiago

On 20 February 2014 23:42, Morgan Fainberg <email address hidden> wrote:

> I've tried to duplicate this issue and have been unsuccessful in
> duplicating the problem. The caveat to my duplication attempts is that I
> have been unable to utilize 14.04 as it will not install in a VM. 14.04
> is also (afaict) classified as alpha, meaning that I am unsure what the
> state of any package is. I have attempted to duplicate this problem ~3
> times now, and keep ending with success.
>
> With:
>
> pip freeze | grep sql -i
>
> MySQL-python==1.2.3
> SQLAlchemy==0.8.5
> sqlalchemy-migrate==0.8.2
>
> I have consistently seen db_sync to an IPv6 address work.
>
> Does this occur with a released version of Ubuntu? Is there anything
> else in the repro steps missing?
>
> ** Changed in: keystone
> Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1275615
>
> Title:
> keystone-manage db_sync fails in a dual-stacked environment
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/keystone/+bug/1275615/+subscriptions
>

Revision history for this message
Thiago Martins (martinx) wrote :

Morgan,

You're right, I just created a Ubuntu 14.04 IPv6-Only environment and it is working like a charm.

The command "keystone-manage db_sync" works perfectly when FQDN points to AAAA (IPv6 addr), my mistake.

Sorry about the buzz...

Best!
Thiago

Revision history for this message
Morgan Fainberg (mdrnstm) wrote :

Not a worry! Happy to work on debugging this. Going to mark this as invalid. Thanks for the report and 2x checking in on it.

Changed in keystone:
status: Incomplete → Invalid
milestone: icehouse-3 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.