Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 973331
Description of problem: I have built a new Fedora 19 Beta VM, applied all available updates, rebooted, and installed freeipa-server. The scripts all completed without error, but the VM will not reboot after installing freeipa-server. When I try to connect to the VM console the last line of text on the display says "Starting Network Manager Wait Online". I am unable to connect with SSH: "ssh: connect to host ipa port 22: Connection refused". Where do I start? Version-Release number of selected component (if applicable): freeipa-server How reproducible: Consistent
See information from Michal Sekletar in the Bugzilla:
ipa.service should include ordering dependency After= on all of its dependencies. When stopping services, ipactl should call systemctl using --no-block option in order to remedy deadlock during shutdown transaction.
Note: as we further discussed this issue with Michal, he also advised that --ignore-dependencies option may work for fixing the reboot deadlock and it would have a benefit of properly waiting until the services are stopped (in contrary with --no-block).
--ignore-dependencies
--no-block
Can you tell me anything about when this problem might be resolved?
It seems that patch is on the list but we are experiencing a bit of slow down due to vacations and conferences. I suspect it will be pushed within a week or so. Is this OK?
Committed to master and ipa-3-2:
master: fb166e8
ipa-3-2: f99bbb9
What does the strike through of the milestone mean? Is the June(3.2.x bug fixing) to be merged with the July(3.2.x bug fixing)? When will I see this fix in Fedora 19?
Replying to [comment:9 deanhunter]:
It has been released in 3.2.2 today. It will take a bit of time for package to show in Fedora. You might want to enable updates-testing repo to get it earlier.
Metadata Update from @mkosek: - Issue assigned to akrivoka - Issue set to the milestone: FreeIPA 3.2.x - 2013/06 (bug fixing)
Login to comment on this ticket.