[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: keystone (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.lau

[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend

2014-03-07 Thread James Page
Marking fix released in trunk as we don't use dbconfig-common any longer but leave a task up for 12.04 which still does. ** Also affects: keystone (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: keystone (Ubuntu) Status: Confirmed => Fix Released ** Changed in:

[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend

2012-05-06 Thread Paul Belanger
This package needs some serious testing, from what I see dbconfig-common is broken. Not only is dbconfig-common configuration skipped on initial installation, dpkg-reconfigure doesn't even work. --- $ sudo dpkg-reconfigure keystone keystone stop/waiting dbconfig-common: writing config to /etc/dbc

[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend

2012-05-01 Thread Launchpad Bug Tracker
[Expired for keystone (Ubuntu) because there has been no activity for 60 days.] ** Changed in: keystone (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/9446

[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend

2012-03-02 Thread rubiojr
keystone: Installed: 2012.1~e4-0ubuntu1 Candidate: 2012.1~e4-0ubuntu1 Version table: *** 2012.1~e4-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubu

[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend

2012-03-02 Thread rubiojr
Also dpkg-reconfigure keystone and using sqlite3 throws the following error: Traceback (most recent call last): File "/usr/bin/keystone-manage", line 28, in cli.main(argv=sys.argv, config_files=config_files) File "/usr/lib/python2.7/dist-packages/keystone/cli.py", line 147, in main re

[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend

2012-03-02 Thread rubiojr
Thanks Dave, Installing works now, but removing throws an error: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: keystone 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation,

[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend

2012-03-02 Thread Dave Walker
Thanks for this bug report. Today, keystone should have a major change, which has been held back until now. The 'upstream' of keystone has performed a rewrite, which should land today. I'd be interested if you could try to reproduce this after it is uploaded. Thanks. ** Changed in: keystone (U

[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend

2012-03-02 Thread rubiojr
First clean keystone install. ** Branch linked: lp:~openstack-ubuntu-packagers/keystone/ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/944684 Title: Error installing keystone selecting dbconf

[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend

2012-03-02 Thread rubiojr
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/944684 Title: Error installing keystone selecting dbconfig-common and sqlite3 as the backend To manage notifications about this bug go to: https://bug