Bug 1838455 - ipp/socket backends connect to turned off device for eternity (contimeout is not applied)
Summary: ipp/socket backends connect to turned off device for eternity (contimeout is ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Dohnal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-21 08:11 UTC by Zdenek Dohnal
Modified: 2020-06-07 19:45 UTC (History)
3 users (show)

Fixed In Version: cups-2.3.3-2.fc32 cups-2.2.12-9.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1838449
Environment:
Last Closed: 2020-05-25 02:46:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Patch (506 bytes, patch)
2020-05-21 08:11 UTC, Zdenek Dohnal
no flags Details | Diff

Description Zdenek Dohnal 2020-05-21 08:11:31 UTC
Created attachment 1690548 [details]
Patch

+++ This bug was initially created as a clone of Bug #1838449 +++

It was found out that httpAddrConnect2() now sets errno EINPROGRESS when it tries to connect to a device which is turned off/network is down/ or when any 'device unreachable' scenarios.

It influences ipp and socket backends, which don't catch EINPROGRESS -> contimeout is not applied, resulting into the backend is running with a job till the job is cancelled manually.

Reported upstream here https://github.com/apple/cups/pull/5782

The fix will set 2 different errnos now:

1) ETIMEDOUT when remaining time in httpAddrConnect2() is reached
2) EHOSTDOWN when all addresses are tried and there are no open file descriptors

This will make backends to apply contimeout and the job will be retried/aborted (according print queue error policy) and queue disabled in the future.

Comment 1 Fedora Update System 2020-05-21 08:28:53 UTC
FEDORA-2020-dc949ad479 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-dc949ad479

Comment 2 Fedora Update System 2020-05-21 09:40:59 UTC
FEDORA-2020-167f5dcc7f has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-167f5dcc7f

Comment 3 Fedora Update System 2020-05-22 03:02:15 UTC
FEDORA-2020-167f5dcc7f has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-167f5dcc7f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-167f5dcc7f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2020-05-22 04:23:48 UTC
FEDORA-2020-dc949ad479 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-dc949ad479`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-dc949ad479

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2020-05-25 02:46:36 UTC
FEDORA-2020-dc949ad479 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2020-06-07 19:45:29 UTC
FEDORA-2020-167f5dcc7f has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.