| Summary: | make "ok" and "error: http connect: Connection refused" less cryptic | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Jaša <djasa> | ||||
| Component: | dnssec-trigger | Assignee: | Paul Wouters <pwouters> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 26 | CC: | laurent.rineau__fedora, pj.pandit, pwouters, thozza | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-05-29 11:54:49 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: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1182488 | ||||||
| Attachments: |
|
||||||
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'. Not sure what is the needinfo about. This needs investigation and working with upstream... This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 1136211 [details] example NM + dnssec-trigger log Description of problem: my dnssec-trigger writes into log this error occasionally: dnssec-triggerd[25460]: [25460] error: http connect: Connection refused It is neither self-explaining, nor specific enough to find out what's wrong. It makes more sense in context of NM log (example log) where 4 instances of failure would probably map to failure to reach login generation & internet connectivity urls over v6 provided by 1st and 2nd upstream DNS servers (and "ok"s would mean that v4 servers could be reached). It would be worthwhile to make both "[<PID>] error: http connect: Connection refused" and "ok" log messages less cryptic and probably less scary (do v6 failures warrant warning when v4 works ok - and vice versa?) Version-Release number of selected component (if applicable): dnssec-trigger-0.11-21.el7.x86_64 (assignee asked for reporting in Fedora) How reproducible: always Steps to Reproduce: 1. enable connection that doesn't provide full IPv6 connectivity 2. 3. Actual results: "error: http connect: Connection refused" lines are in dnssec-trigger log Expected results: errors are marked as errors only when they are actual errors and they are self-explaining - containing url and dns server, e.g.: error: http connection to <server> translated by <dns> to <ip>: Connection refused Additional info: