Unexpected log statement about schedule run count being reset when not dealing with schedules
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: 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
check that schedule exists before attempting to use it
Please register to edit this issue