Description of problem: When using F10 live iso install , and defining users to been resolved via yp domain as opposed to local /etc files, network is not started upon boot, therefore yp cannot bind and yp users cannot login How reproducible: very Steps to Reproduce: 1. install F10 via iso live CD 2. define users accounts to user NIS(yp) rather than /etc 3. reboot, note network not started Actual results: Non-root users cannot log in Expected results: yp domain users should be able to log in Additional Information: autofs (bug 476306) also suffer from similar issue
Hi Jon, I don't understand why you opened this issue against ypbind component, ypbind is not liable for starting network... But I tried to do fresh F-10 from Live CD install, setup NIS during first boot process, setup firewall, reboot and was able to log as NIS user without problem. Let me know more details and/or consider changing component to something more appropriate.
Hi, I wasn't sure what to open it against to be honest, ypbind seem a logical option. WRT the installation, thats interesting. I did 2 installs and I could not get either to work against NIS after the install as I always found that network was not started and that I had to chkconfig on network. Never worried about the firewall side of things I have to say though, hadn't occured to me, though that doesn't explain the lack of network. Understand that this is not ypbind's issue per se though. I suppose the main query here was would it not be sane for the ypbind rpm to verify network is running?? Not sure, but it would have saved me a lot of grief.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.