Bug 497301
| Summary: | ServerName not treated as acceptable Host: value | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Marek Greško <gresko> |
| Component: | cups | Assignee: | Tim Waugh <twaugh> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 9 | CC: | matt.castelein, twaugh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 1.3.10-5.fc10 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-05-12 03:53:51 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Marek Greško
2009-04-23 09:45:25 UTC
You need to add 'ServerAlias clientfqdn', as mentioned in the update notes: https://www.redhat.com/archives/fedora-package-announce/2009-April/msg00510.html https://admin.fedoraproject.org/updates/F9/FEDORA-2009-3753 Are you still seeing problems after doing that and restarting cups on the server? Works for me. Thank you. But I have two questions. Why the ServerName is not known to the server and ServerAlias should be also specified? I would expect cupsd.conf.rpmnew to be created if a configuration change is required. Should not it appear in the next update of cups? 1. Why ServerName is not sufficient. It ought to be. Do you mean that you need to add a 'ServerAlias' line with exactly the same hostname as the 'ServerName' line? 2. Automatic adjustment of cupsd.conf. I don't think this is possible with rpm. The exact change needed to preserve compatibility is to add "ServerAlias *" to cupsd.conf, *once*, on upgrade from cups < 1.3.10. I was unable to find any way to do this. 1. Yes exactly. 2. OK. I accept. Reported upstream with patch. cups-1.3.10-2.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/cups-1.3.10-2.fc9 cups-1.3.10-2.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/cups-1.3.10-2.fc10 cups-1.3.10-4.fc10 should now also adjust cupsd.conf automatically. cups-1.3.10-4.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing-newkey update cups'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2009-4052 cups-1.3.10-4.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update cups'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-4056 cups-1.3.10-5.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update cups'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-4056 cups-1.3.10-5.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing-newkey update cups'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2009-4052 cups-1.3.10-5.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report. cups-1.3.10-5.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. |