keystone starts too early

Bug #1153988 reported by Magosányi Árpád
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
keystone (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

In folsom from the ubuntu cloud archive keystone tried to start too early and failed, perhaps because some of its dependencies wasn't up yet.
The fix was adding runlevels to /etc/init/keystone.conf
start on (local-filesystems and net-device-up IFACE!=lo and runlevel [2345] )

I'm reporting it here because - though https://wiki.ubuntu.com/ServerTeam/CloudArchive says the bugs go on the normal ways - ubuntu-bug refused to report it.

Dolph Mathews (dolph)
affects: keystone → keystone (Ubuntu)
Revision history for this message
Yolanda Robla (yolanda.robla) wrote :

Thanks for reporting this. Can you provide us a logfile where we can see the errors in keystone installation?
Thanks
Yolanda

Changed in keystone (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for keystone (Ubuntu) because there has been no activity for 60 days.]

Changed in keystone (Ubuntu):
status: Incomplete → Expired
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.