Bug 2417957
| Summary: | auto-convert-to-yaml FAILED - incoming_ip_to_bind in wrong position | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | customercare |
| Component: | trafficserver | Assignee: | Jered Floyd <jered> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 42 | CC: | jered |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | trafficserver-10.1.0-3.fc43 trafficserver-10.1.0-3.fc42 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-12-12 01:33:13 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: | |||
I share your annoyance at this upstream change :-/ Could I please ask you to open an upstream issue on this, since that's where the update script originates? https://github.com/apache/trafficserver/issues The update script is pretty minimal: https://github.com/apache/trafficserver/blob/master/tools/records/convert2yaml.py I went back-and-forth on if I should write and include an auto-update unit. I felt in the end it was better than always failing, but this was release-noted as a potential breaking change: https://docs.fedoraproject.org/en-US/fedora/f42/release-notes/sysadmin/#trafficserver-10 (Since this is a one-time thing I unfortunately don't expect it'll be improved. Still worth documenting, though. For this reason, I am not updating EPEL 8/9 to ATS 10.) They say, it's fixed : https://github.com/apache/trafficserver/pull/12713 Yes, I've backported this to 10.1.0 and have builds running now. FEDORA-2025-92b5298639 (trafficserver-10.1.0-3.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-92b5298639 FEDORA-2025-3bab371337 (trafficserver-10.1.0-3.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-3bab371337 HMM..i have to do one additional system upgrade TONIGHT where this could be tested, if it would already be in F42 stable. Is that possible? FEDORA-2025-92b5298639 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-92b5298639` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-92b5298639 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-3bab371337 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-3bab371337` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-3bab371337 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-92b5298639 (trafficserver-10.1.0-3.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-3bab371337 (trafficserver-10.1.0-3.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. |
Name : trafficserver Version : 10.1.0 Release : 2.fc42 Architecture: x86_64 Install Date: So 30 Nov 2025 23:38:10 CET Description of problem: ATS 10 has a migrated the records.config to the worst possibe form: yaml. The automigration script in the rpm has wrongfully converted "incoming_ip_to_bind" to proxy. records ... proxy local incoming_ip_to_bind: a.b.c.d instead of: records: accept_threads: 1 incoming_ip_to_bind: a.b.c.d This caused the server setup to fail, because the given ip was not used, instead the server tried to bind on 0.0.0.0 , which was not possible due to httpd running on another ip. In addition, these vaues have also not converted correctly: Warn: Warn: Ignoring field 'connect_attempts_max_retries_dead_server' [proxy.config.http.connect_attempts_max_retries_dead_server] at line=43, col=5. Not registered and Unknown tag type '?' Warn: Ignoring field 'connect_attempts_timeout' [proxy.config.http.parent_proxy.connect_attempts_timeout] at line=60, col=7. Not registered and Unknown tag type '?' Warn: Ignoring field 'post_connect_attempts_timeout' [proxy.config.http.post_connect_attempts_timeout] at line=62, col=5. Not registered and Unknown tag type '?' But those are not as relevant as the incoming_ip_to_bind option.