image-store-proxy reports failure to start while it starts correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
image-store-proxy (Ubuntu) |
Fix Released
|
Low
|
Mathias Gug |
Bug Description
python-
Sometimes the image-store-proxy will report failure to start, while it is indeed started:
$ sudo service image-store-proxy start
* Starting Image Store Proxy image-store-proxy [fail]
$ sudo service image-store-proxy status
* Checking status of Image Store Proxy image-store-proxy [ OK ]
This comes from the way STARTTIME is used in /etc/init.
If STARTTIME is undefined (or equal to 0) then its a race between the init script and the pidfile creation in the backgrounded process, which the shell sometimes wins.
This should be changed to either:
- always report success if STARTTIME is undefined and start-stop-daemon succeeded (no pidfile check)
- set STARTTIME to at least 1 second to have the race won by python most of the time
Changed in image-store-proxy (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in image-store-proxy (Ubuntu): | |
assignee: | nobody → Mathias Gug (mathiaz) |
status: | Triaged → In Progress |
This bug was fixed in the package image-store-proxy - 1.0-0ubuntu1
---------------
image-store-proxy (1.0-0ubuntu1) karmic; urgency=low
* New upsream release (LP: #434185)
+ Enable image signature checking. Add gnupg dependency. Import image
store GPG armored key in its keyring at install time.
+ Renable all tests.
* Set STARTTIME to 1 second to avoid false start failure report from the
init script (LP: #433863).
-- Mathias Gug <email address hidden> Wed, 23 Sep 2009 20:17:44 -0400