Project

Profile

Help

Issue #1244

closed

Unexpected log statement about schedule run count being reset when not dealing with schedules

Added by bmbouter about 7 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Category:
-
Sprint/Milestone:
-
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 #1

Updated by mhrivnak about 7 years ago

  • Priority changed from Normal to High
  • Triaged changed from No to Yes
Actions #2

Updated by dkliban@redhat.com about 7 years ago

  • Platform Release set to 2.7.0
Actions #3

Updated by amacdona@redhat.com about 7 years ago

  • Status changed from NEW to POST
Actions #4

Updated by amacdona@redhat.com about 7 years ago

  • Assignee set to amacdona@redhat.com

Added by Austin Macdonald almost 7 years ago

Revision e4ef6312

check that schedule exists before attempting to use it

closes #1244

Added by Austin Macdonald almost 7 years ago

Revision e4ef6312

check that schedule exists before attempting to use it

closes #1244

Actions #5

Updated by Anonymous almost 7 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #6

Updated by dkliban@redhat.com almost 7 years ago

  • Status changed from MODIFIED to 5
Actions #7

Updated by amacdona@redhat.com almost 7 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE
Actions #8

Updated by bmbouter over 3 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF