Actions
Issue #1244
closed
Unexpected log statement about schedule run count being reset when not dealing with schedules
Start date:
Due date:
Estimated time:
Severity:
1. Low
Version:
2.7.0 Beta
Platform Release:
2.7.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
I did a publish using the API, and I saw the following log statement. I wasn't doing anything schedule related. It seems like it shouldn't be here.
pulp[3206]: pulp.server.async.tasks:INFO: resetting consecutive failure count for schedule None
I expected two behaviors:
1. To not reset the failure count when not dealing with a schedule.
2. To not log about a schedule related feature when schedule_id is None
Actions
.
check that schedule exists before attempting to use it
closes #1244