Bug 607556
Summary: | funcd dies if the network is down when it starts | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Scott Schmit <i.grok> |
Component: | func | Assignee: | Seth Vidal <skvidal> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | alikins, brett.lentz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-06-27 18:51:44 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
Scott Schmit
2010-06-24 11:14:15 UTC
hmm - I suspect the problem is it needs to do a name lookup to know if it knows who it is. Is your hostname for func not defined in your /etc/hosts? If you define it there does func work again? Actually, it is, though maybe not the way it would think. On my home network, I've configured DHCP to always assign my laptop with a particular IP address by MAC (so wired & wireless will get different IPs). In my local DNS forward zone, I have: nameA.domain A IP-wireless nameB.domain A IP-wireless nameC.domain A IP-wired nameD.domain A IP-wired My hostname is nameB.domain In the reverse zone, I have: IP-wireless PTR nameA.domain IP-wired PTR nameC.domain In /etc/hosts, I have: 127.0.0.1 localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 IP-wireless nameA.domain nameB.domain nameB IP-wired nameC.domain nameD.domain nameD Kerberos works, and my ssh server ticket has host/nameA.domain@REALM as its principal. Func generated the certificate as nameA.domain. Right so it generated nameA. when funcd loads it's looking for it's name and then for a key matching that name. If it cannot find one it is generating a new key and csr and attempting to send that to the certmaster. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed. |