Scrubber exits with 0 even though it didn't work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Undecided
|
Dharini Chandrasekar |
Bug Description
glance-scrubber fails to work with:
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.
08:52:43 2016-02-21 07:52:43.011 16387 ERROR glance.scrubber [req-3200d95d-
(this was due to using keystone v3 API -- but ignore the error itself, just consider that it failed for some reason)
However, when I run it, the exit code of the process is still 0, while it should be 1.
Changed in glance: | |
assignee: | nobody → Dharini Chandrasekar (dharini-chandrasekar) |
So I believe you'd like us to propagate the error at https:/ /github. com/openstack/ glance/ blob/master/ glance/ scrubber. py#L277 but I'm not sure whether that is a great idea. glance-scrubber may run as a daemon, and it feels better to handle errors gracefully like this, since they might happen from time to time.
What do the others think?