dpkg --configure keystone fails on install

Bug #1247342 reported by David Marshall
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Invalid
Medium
Thomas Goirand

Bug Description

-----------------------------------
Built: 2013-11-01T23:01:37 00:00
git SHA: 0dd2d310b7acfe1aa0079286c36ba06b8168f264
URL: http://docs.openstack.org/havana/install-guide/install/apt-debian/content/keystone-install.html
source File: file:/home/jenkins/workspace/openstack-install-deploy-guide-debian/doc/install-guide/section_keystone-install.xml
xml:id: keystone-install

root@manager:~# dpkg --configure keystone
Setting up keystone (2013.2-2~bpo70+1) ...
PKG-Openstack now calling: dbc_go keystone configure
Usage: ip addr {add|change|replace} IFADDR dev STRING [ LIFETIME ]
                                                      [ CONFFLAG-LIST ]
       ip addr del IFADDR dev STRING
       ip addr {show|flush} [ dev STRING ] [ scope SCOPE-ID ]
                            [ to PREFIX ] [ FLAG-LIST ] [ label PATTERN ]
IFADDR := PREFIX | ADDR peer PREFIX
          [ broadcast ADDR ] [ anycast ADDR ]
          [ label STRING ] [ scope SCOPE-ID ]
SCOPE-ID := [ host | link | global | NUMBER ]
FLAG-LIST := [ FLAG-LIST ] FLAG
FLAG := [ permanent | dynamic | secondary | primary |
           tentative | deprecated | dadfailed | temporary |
           CONFFLAG-LIST ]
CONFFLAG-LIST := [ CONFFLAG-LIST ] CONFFLAG
CONFFLAG := [ home | nodad ]
LIFETIME := [ valid_lft LFT ] [ preferred_lft LFT ]
LFT := forever | SECONDS
dpkg: error processing keystone (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 keystone
root@manager:~#

Changed in openstack-manuals:
assignee: nobody → Thomas Goirand (thomas-goirand)
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Thomas Goirand (thomas-goirand) wrote :

Hi,

I haven't seen this happen at all, so it surprises me. That I believe happens is that you don't have a default route configured on your server. Could you confirm that fact? What is the output of:

LC_ALL=C /sbin/route | grep default |awk -- '{ print $8 }'

for you?

Cheers,

Thomas

Changed in openstack-manuals:
status: Confirmed → Incomplete
Revision history for this message
David Marshall (t-david-0) wrote : Re: [Bug 1247342] Re: dpkg --configure keystone fails on install

Thank you Thomas,

You were right. I didn't have a default route configured on my machine.

I update /etc/network/interfaces to create one and this fixed the problem.

Here is the output you requested from before:

root@manager:~# LC_ALL=C /sbin/route | grep default |awk -- '{ print $8 }'
root@manager:~# /sbin/route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.8.0 * 255.255.248.0 U 0 0 0 eth0
192.168.46.0 * 255.255.255.0 U 0 0 0 eth1
root@manager:~#

And from after:

root@manager:~# LC_ALL=C /sbin/route | grep default |awk -- '{ print $8 }'
eth0
root@manager:~# /sbin/route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default manager.marshal 0.0.0.0 UG 0 0 0 eth0
192.168.8.0 * 255.255.248.0 U 0 0 0 eth0
192.168.46.0 * 255.255.255.0 U 0 0 0 eth1
root@manager:~#

Regards,
Dave
On 03/11/13 00:55, Thomas Goirand wrote:
> LC_ALL=C /sbin/route | grep default |awk -- '{ print $8 }'

Revision history for this message
Thomas Goirand (thomas-goirand) wrote :

Hi,

Thanks for confirming this.

It really should be considered as a bug and shall
be fixed. I'll work this out asap, checking for the
emptyness output of the route command before using
it.

Next time, when this is about Debian packages, could
you please report the bug against the Debian BTS?
If you don't know how to, there's a link here:

http://wiki.debian.org/OpenStack

cheers,

Thomas (from my phone)

On Sun Nov  3 2013 09:01:38 AM HKT, David Marshall <email address hidden> wrote:

> Thank you Thomas,
>
> You were right.  I didn't have a default route configured on my machine.
>
> I update /etc/network/interfaces to create one and this fixed the
> problem.
>
> Here is the output you requested from before:
>
> root@manager:~# LC_ALL=C /sbin/route | grep default |awk -- '{ print $8
> }' root@manager:~# /sbin/route
> Kernel IP routing table
> Destination        Gateway                Genmask                Flags Metric Ref Use
> Iface 192.168.8.0        *                            255.255.248.0    U        0 0              0
> eth0 192.168.46.0      *                            255.255.255.0    U        0 0              0
> eth1 root@manager:~#
>
>
> And from after:
>
> root@manager:~# LC_ALL=C /sbin/route | grep default |awk -- '{ print $8
> }' eth0
> root@manager:~# /sbin/route
> Kernel IP routing table
> Destination        Gateway                Genmask                Flags Metric Ref Use
> Iface default                manager.marshal 0.0.0.0                UG      0 0              0
> eth0 192.168.8.0        *                            255.255.248.0    U        0 0              0
> eth0 192.168.46.0      *                            255.255.255.0    U        0 0              0
> eth1 root@manager:~#
>
>
> Regards,
> Dave
> On 03/11/13 00:55, Thomas Goirand wrote:
> > LC_ALL=C /sbin/route | grep default |awk -- '{ print $8 }'
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1247342
>
> Title:
>    dpkg --configure keystone fails on install
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-manuals/+bug/1247342/+subscriptions

Revision history for this message
Andreas Jaeger (jaegerandi) wrote :

Thomas, is this a bug in the Debian packaging? In that case please mark the bug as invalid for the manual.

tags: added: install-guide
Tom Fifield (fifieldt)
Changed in openstack-manuals:
status: Incomplete → Invalid
Revision history for this message
Thomas Goirand (thomas-goirand) wrote :

Hi,

This bug can be closed, as the necessary logic has been added to handle the case where no default gateway is set.

Thomas

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.