glance-api and glance-registry will not be started on transition from runlevel 1 to 2
Bug #820688 reported by
Clint Byrum
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| glance (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
start on (local-filesystems and net-device-up IFACE!=lo)
stop on runlevel [016]
These criteria for starting will not be met when transitioning from runlevel 1 to 2, but the stop on will be met when the admin transitions to runlevel 1 for maintenance.
| Changed in glance (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in glance (Ubuntu): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package glance - 2012.2~
---------------
glance (2012.2~
[ Chuck Short ]
* New upstream version.
* drop debian/
* debian/rules: Re-activate tests.
* debain/control: Add depends on python-swiftclient.
* debian/*.usptart: make glance start from runlevel 1 to runlevel
2. (LP: #820688)
[ Soren Hansen ]
* Update debian/watch to account for symbolically named tarballs and
use newer URL.
* New snapshot.
* Refresh disable-
* Fix Launchpad URLs in debian/watch.
-- Chuck Short <email address hidden> Fri, 07 Sep 2012 12:17:46 -0500