Red Hat Bugzilla – Bug 817876
firstboot crashes when trying to join ipav2 at install time
Last modified: 2013-08-01 08:38:22 EDT
When trying to join an IPAv2 domain in F17 beta.
After you give admin creds to join the ipa domain firstboot is stuck for a few minutes then suddendly crashes or exits leaving a blank screen.
Isn't there any traceback?
I haven't seen any.
So it just exits? Can you look inside /tmp if there aren't any files starting with "traceback" ?
Sorry I blowed away the VM already. I will try to check /tmp the next time, let me know if there is any other data you need me to look for.
Anything it spits out when exiting. :)
The IPAv2 thing is done in the Network login screen?
(In reply to comment #5)
> Anything it spits out when exiting. :)
It doesn't spit anything.
> The IPAv2 thing is done in the Network login screen?
Can you please give me some details how to reproduce it? Do I need to have the domain set up, or will it be enough to just try to fill out the details in Network login?
(In reply to comment #7)
> Can you please give me some details how to reproduce it? Do I need to have the
> domain set up, or will it be enough to just try to fill out the details in
> Network login?
You may need the domain set up, I haven't tried w/o an IPA install available.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17'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 17 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, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.