Bug 2006591

Summary: Trying to restart and hold a job doesn't work
Product: Red Hat Enterprise Linux 8 Reporter: Bryan Mason <bmason>
Component: cupsAssignee: Zdenek Dohnal <zdohnal>
Status: CLOSED ERRATA QA Contact: Petr Dancak <pdancak>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.4CC: pdancak, psklenar
Target Milestone: rcKeywords: AutoVerified, Patch, TestCaseProvided, Triaged
Target Release: ---Flags: pdancak: needinfo+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cups-2.2.6-41.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2006713 (view as bug list) Environment:
Last Closed: 2022-05-10 15:21:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2006713    
Attachments:
Description Flags
Proposed patch none

Description Bryan Mason 2021-09-22 01:22:37 UTC
Description of problem:

  If a job is restarted with a job-held-until attribute that isn't
  no-hold, the job should be restarted and held, but it isn't.

Version-Release number of selected component (if applicable):

   cups-2.2.6-38.el8

How reproducible:

  100%

Steps to Reproduce:

 1. Run a print job that fails.

 2. Try to restart the print job by performing a Restart-Job IPP
    operation with "job-hold-until" set to "indefinite"

Actual results:

  The job does not restart.

Expected results:

  The job should restart.

Additional info:

  This was addressed upstream in PR 250:
    https://github.com/OpenPrinting/cups/pull/250

  I'm working on a test script that uses ipptool to demonstrate the
  problem and verify that it has been fixed.

Comment 2 Bryan Mason 2021-09-22 03:37:42 UTC
Created attachment 1825181 [details]
Proposed patch

Patch from upstream PR

Comment 16 errata-xmlrpc 2022-05-10 15:21:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (cups bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2032