keystone-manage: error: argument command: invalid choice: 'db' from postinst
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
keystone (Ubuntu) |
Fix Released
|
Critical
|
Martin Pool |
Bug Description
Precise A2 updated at time of this bug.
Just done an install of OpenStack and Keystone now has changed to an interactive session (breaking all previous unattended installs) due to introduction of dbconfig. The install fails due to what looks like a syntax error creating entries in the database.
Replacing config file /etc/dbconfig-
granting access to database keystone for keystone@localhost: success.
verifying access for keystone@localhost: success.
creating database keystone: success.
verifying database keystone exists: success.
dbconfig-common: flushing administrative password
usage: keystone-manage [-h]
keystone-manage: error: argument command: invalid choice: 'db' (choose from 'create_
dpkg: error processing keystone (--configure):
subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
keystone
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@openstack2
iF keystone 2012.1~
ii python-keystone 2012.1~
Also:
1) Is this auto create necessary / can it be optional?
2) What does it create so I know what can be catered for with an unattended install?
Related branches
- Ubuntu branches: Pending requested
-
Diff: 26 lines (+7/-1)2 files modifieddebian/changelog (+6/-0)
debian/keystone.postinst (+1/-1)
summary: |
- Keystone Ubuntu Precise dbconfig install broken - show stopper + keystone-manage: error: argument command: invalid choice: 'db' from + postinst |
Changed in keystone (Ubuntu): | |
importance: | Undecided → Critical |
Changed in keystone (Ubuntu): | |
status: | Confirmed → In Progress |
Status changed to 'Confirmed' because the bug affects multiple users.