Getting around the anaconda bug

[Arun SAG]

Hi,

I am trying to create live cd using livecd-creator. I found this anaconda
bug https://bugzilla.redhat.com/show_bug.cgi?id=626780 which crashes
anaconda after the device selection stage. Any idea on how to get around
this?

-- 
Arun S.A.G

[James Heather]

You need to downgrade udev on the host machine.

Just 'yum downgrade udev' should sort things out.

On Tue, 2010-08-31 at 21:52 +0100, Arun SAG wrote:
>  Hi,
>  
>  I am trying to create live cd using livecd-creator. I found this
>  anaconda bug https://bugzilla.redhat.com/show_bug.cgi?id=626780 which
>  crashes anaconda after the device selection stage. Any idea on how to
>  get around this?
>  
>  -- 
>  Arun S.A.G

[James Heather]

Sorry--I'm an idiot--wrong bug. You need to downgrade NetworkManager on
the live cd before installing to a hard drive.

On Tue, 2010-08-31 at 21:52 +0100, Arun SAG wrote:
>  Hi,
>  
>  I am trying to create live cd using livecd-creator. I found this
>  anaconda bug https://bugzilla.redhat.com/show_bug.cgi?id=626780 which
>  crashes anaconda after the device selection stage. Any idea on how to
>  get around this?
>  
>  -- 
>  Arun S.A.G

[Arun SAG]

On Wed, Sep 1, 2010 at 2:30 AM, James Heather <j.heather(a)surrey.ac.uk&gt;wrote:

>  >Sorry--I'm an idiot--wrong bug. You need to downgrade
> NetworkManager on
>  >the live cd before installing to a hard drive.
>  
How to do that? In kickstart file?
-- 
Arun S.A.G

[James Heather]

No, boot it up, then

	yum downgrade NetworkManager

as root before you install to hard drive.

Conceivably you will also need

	service NetworkManager restart

James

On Tue, 2010-08-31 at 22:06 +0100, Arun SAG wrote:
>  
>  
>  On Wed, Sep 1, 2010 at 2:30 AM, James Heather <j.heather(a)surrey.ac.uk&gt;
>  wrote:
>          >Sorry--I'm an idiot--wrong bug. You need to downgrade
>          NetworkManager on
>          >the live cd before installing to a hard drive.
>  
>  How to do that? In kickstart file?
>  -- 
>  Arun S.A.G

[Arun SAG]

On Wed, Sep 1, 2010 at 2:38 AM, James Heather <j.heather(a)surrey.ac.uk&gt;wrote:

>  >No, boot it up, then
>
>  >       yum downgrade NetworkManager
>
>  >as root before you install to hard drive.
>
>  >Conceivably you will also need
>
>    >     service NetworkManager restart
>  

Thank you. But i am sorry, i am going to distribute this livecd i cannot ask
people to do this. Is there any way around?

--
Arun S.A.G

[James Heather]

On Tue, 2010-08-31 at 22:12 +0100, Arun SAG wrote:
>  
>  
>  On Wed, Sep 1, 2010 at 2:38 AM, James Heather <j.heather(a)surrey.ac.uk&gt;
>  wrote:
>          >No, boot it up, then
>          
>          >       yum downgrade NetworkManager
>          
>          >as root before you install to hard drive.
>          
>          >Conceivably you will also need
>          
>            >     service NetworkManager restart
>  
>  
>  Thank you. But i am sorry, i am going to distribute this livecd i
>  cannot ask people to do this. Is there any way around? 
You could try adding the following to your kickstart file. I haven't
tried it, but it must be at least roughly right:

%post --nochroot
yum -y --installroot="$INSTALL_ROOT" downgrade NetworkManager
%end

Let me know how you get on...

[Arun SAG]

On Wed, Sep 1, 2010 at 2:53 AM, James Heather <j.heather(a)surrey.ac.uk&gt;wrote:

>  >%post --nochroot
>  >yum -y --installroot="$INSTALL_ROOT" downgrade NetworkManager
>  >%end
>
>  >Let me know how you get on...
>
>
>  
Tried this sadly the dependency has failed http://fpaste.org/c6ya/



-- 
Arun S.A.G

[Jerry Vonau]

On Wed, 2010-09-01 at 12:44 +0530, Arun SAG wrote:
>  
>  
>  On Wed, Sep 1, 2010 at 2:53 AM, James Heather <j.heather(a)surrey.ac.uk&gt;
>  wrote:
>          
>          
>          
>          >%post --nochroot
>          >yum -y --installroot="$INSTALL_ROOT" downgrade NetworkManager
>          >%end
>          
>          >Let me know how you get on...
>          
>          
>          
>          
>  
>  Tried this sadly the dependency has failed http://fpaste.org/c6ya/ 
You could try
yum -y --installroot="$INSTALL_ROOT" downgrade NetworkManager*
note the wildcard, should cover NetworkManager-glib

or (all on one line)
yum -y --installroot="$INSTALL_ROOT" downgrade 
NetworkManager  NetworkManager-glib

Jerry

[James Heather]

On Wed, 2010-09-01 at 10:16 +0100, Jerry Vonau wrote:
>  On Wed, 2010-09-01 at 12:44 +0530, Arun SAG wrote:
>  > 
>  > 
>  > On Wed, Sep 1, 2010 at 2:53 AM, James Heather <j.heather(a)surrey.ac.uk&gt;
>  > wrote:
>  >         
>  >         
>  >         
>  >         >%post --nochroot
>  >         >yum -y --installroot="$INSTALL_ROOT" downgrade NetworkManager
>  >         >%end
>  >         
>  >         >Let me know how you get on...
>  >         
>  >         
>  >         
>  >         
>  > 
>  > Tried this sadly the dependency has failed http://fpaste.org/c6ya/
>  
>  You could try
>  yum -y --installroot="$INSTALL_ROOT" downgrade NetworkManager*
>  note the wildcard, should cover NetworkManager-glib
>  
>  or (all on one line)
>  yum -y --installroot="$INSTALL_ROOT" downgrade 
>  NetworkManager  NetworkManager-glib 
You want to cover NetworkManager-gnome too, so either use the wildcard
or append that to the second option. (This rings a bell. I think I had
to use a wildcard.)

I'm a bit bothered by the umount failure in your paste. Are you using
akmods or anything like that (from rpmfusion)? If so, you might need the
following hack at the end of your kickstart file to avoid the
(intermittent) umount problem:

%post --nochroot
#hack to try to stop umount probs
while (/usr/sbin/lsof /dev/loop* 2>/dev/null | grep -v "$0" 2>/dev/null |
grep -q "$INSTALL_ROOT")
do
	sleep 5s
done
%end

That's completely unrelated to the NetworkManager, though, so don't
worry about it unless you also hit this issue.

James

[Arun SAG]

On Wed, Sep 1, 2010 at 3:29 PM, James Heather <j.heather(a)surrey.ac.uk&gt;wrote:

>  >I'm a bit bothered by the umount failure in your paste. Are you using
>  >akmods or anything like that (from rpmfusion)? If so, you might need the
>  >following hack at the end of your kickstart file to avoid the
>  >(intermittent) umount problem:
>
>  >%post --nochroot
>  >#hack to try to stop umount probs
>  >while (/usr/sbin/lsof /dev/loop* 2>/dev/null | grep -v "$0"
> 2>/dev/null |
>  grep -q "$INSTALL_ROOT")
>  >do
>  >       sleep 5s
>  >done
>  >%end
>
>  >That's completely unrelated to the NetworkManager, though, so don't
>  >worry about it unless you also hit this issue.
>
>  
Thank you. I will try this.



-- 
Arun S.A.G

[James Heather]

>          >I'm a bit bothered by the umount failure in your
> paste. Are
>          you using
>          >akmods or anything like that (from rpmfusion)? If so, you
>          might need the
>          >following hack at the end of your kickstart file to avoid the
>          >(intermittent) umount problem:
>          
>          >%post --nochroot
>          >#hack to try to stop umount probs
>          >while (/usr/sbin/lsof /dev/loop* 2>/dev/null | grep -v "$0"
>          2>/dev/null | grep -q "$INSTALL_ROOT")
>          >do
>          >       sleep 5s
>          >done
>          >%end
>          
>          >That's completely unrelated to the NetworkManager, though, so
>          don't
>          >worry about it unless you also hit this issue.
>          
>  
>  Thank you. I will try this.  
By the way, you'll need to make sure you have lsof installed on the
host.

[Arun SAG]

On Wed, Sep 1, 2010 at 2:46 PM, Jerry Vonau <jvonau(a)shaw.ca&gt; wrote:

>  >You could try
>  >yum -y --installroot="$INSTALL_ROOT" downgrade NetworkManager*
>  >note the wildcard, should cover NetworkManager-glib
>
>  >or (all on one line)
>  >yum -y --installroot="$INSTALL_ROOT" downgrade
>  >NetworkManager  NetworkManager-glib
>
>  
Tried this and created an iso. System crashed as GDM starts.
-- 
Arun S.A.G

[James Heather]

>          >You could try
>          >yum -y --installroot="$INSTALL_ROOT" downgrade
>          NetworkManager*
>          >note the wildcard, should cover NetworkManager-glib
>          
>          >or (all on one line)
>          >yum -y --installroot="$INSTALL_ROOT" downgrade
>          
>          >NetworkManager  NetworkManager-glib
>          
>  
>  Tried this and created an iso. System crashed as GDM starts. 
That's a bit mad. Can you build it again, redirecting output to a file,
and then paste here?

Did you fix the '%end' bug?

James

[Arun SAG]

On Wed, Sep 1, 2010 at 7:39 PM, James Heather <j.heather(a)surrey.ac.uk&gt;wrote:

>  >Did you fix the '%end' bug?
>  
I did. I will build it and post you the output.


-- 
Arun S.A.G

[Arun SAG]

On Wed, Sep 1, 2010 at 7:39 PM, James Heather <j.heather(a)surrey.ac.uk&gt;wrote:

>  >That's a bit mad. Can you build it again, redirecting output to a file,
>  >and then paste here?
>
>  >Did you fix the '%end' bug? 


When downgrading i get this error http://fpaste.org/Ga3M/
-- 
Arun S.A.G

[Bruno Wolff III]

On Wed, Sep 01, 2010 at 02:42:03 +0530,
  Arun SAG <sagarun(a)gmail.com&gt; wrote:
>  
>  Thank you. But i am sorry, i am going to distribute this livecd i cannot ask
>  people to do this. Is there any way around? 
Use a custom set of repos to build it.
The simplest immediate way is probably to download the source rpm for the
working NetworkManager and use it to build a new rpm with a slightly higher
version than the broken one (by editing the spec file), put it in a directory
by itself and run createrepo. Then edit the kickstart file to use that
repo in addition to the others you are using. 

If you aren't in a big hurry, you might wait for a fixed version of
NetworkManager to become available.

[Tom Atkinson]

On Tue, 2010-08-31 at 16:24 -0500, Bruno Wolff III wrote:
>  On Wed, Sep 01, 2010 at 02:42:03 +0530,
>    Arun SAG <sagarun(a)gmail.com&gt; wrote:
>  > 
>  > Thank you. But i am sorry, i am going to distribute this livecd i cannot ask
>  > people to do this. Is there any way around?
>  
>  Use a custom set of repos to build it.
>  The simplest immediate way is probably to download the source rpm for the
>  working NetworkManager and use it to build a new rpm with a slightly higher
>  version than the broken one (by editing the spec file), put it in a directory
>  by itself and run createrepo. Then edit the kickstart file to use that
>  repo in addition to the others you are using. 
There's a simpler way than that. Add --excludepkgs=NetworkManager* to
the updates repo line in the kickstart file and put the older
NetworkManager rpms in the custom repo unchanged.

[James Heather]

On Wed, 2010-09-01 at 18:57 +0100, Tom Atkinson wrote:
>  On Tue, 2010-08-31 at 16:24 -0500, Bruno Wolff III wrote:
>  > On Wed, Sep 01, 2010 at 02:42:03 +0530,
>  >   Arun SAG <sagarun(a)gmail.com&gt; wrote:
>  > > 
>  > > Thank you. But i am sorry, i am going to distribute this livecd i cannot ask
>  > > people to do this. Is there any way around?
>  > 
>  > Use a custom set of repos to build it.
>  > The simplest immediate way is probably to download the source rpm for the
>  > working NetworkManager and use it to build a new rpm with a slightly higher
>  > version than the broken one (by editing the spec file), put it in a directory
>  > by itself and run createrepo. Then edit the kickstart file to use that
>  > repo in addition to the others you are using.
>  
>  There's a simpler way than that. Add --excludepkgs=NetworkManager* to
>  the updates repo line in the kickstart file and put the older
>  NetworkManager rpms in the custom repo unchanged. 
Nice--didn't know you could exclude packages on a per repo basis.

In that case, it's even easier. If you --excludepkgs=NetworkManager*
from the updates repo line, it'll presumably just pick the packages up
from the release repo, and everything in the garden will be lovely.

[Arun SAG]

On Wed, Sep 1, 2010 at 11:32 PM, James Heather <j.heather(a)surrey.ac.uk&gt;wrote:

>  >Nice--didn't know you could exclude packages on a per repo
> basis.
>
>  >In that case, it's even easier. If you --excludepkgs=NetworkManager*
>  >from the updates repo line, it'll presumably just pick the packages up
>  >from the release repo, and everything in the garden will be lovely.
>  
I excluded NetworkManager from updates repo, NetworkManager* stuff from
release repo got installed. I tried to test the live-DVD with virtualbox

while loading gnome the virtualbox crashes and the guest os goes to aborted
mode. Tried with runlevel 3 , everything worked fine, switched to root and
started X server, it showed the regular root user warning, on closing the
warning message again guest os crashes and goes to aborted mode. Is it
possible to get the log messages from a live-cd that crashes completely?

Tried the ISO with virt-manager i am getting same old "No root device found"
error .

Here is the kick start file
http://psgkriya.org/saga/misc/msec-fedora-remix.ks

-- 
Arun S.A.G

[James Heather]

>  On Wed, Sep 1, 2010 at 11:32 PM, James Heather
>  <j.heather(a)surrey.ac.uk&gt; wrote:
>          >Nice--didn't know you could exclude packages on a per repo
>          basis.
>          
>          >In that case, it's even easier. If you
>          --excludepkgs=NetworkManager*
>          >from the updates repo line, it'll presumably just pick the
>          packages up
>          >from the release repo, and everything in the garden will be
>          lovely.
>  
>  I excluded NetworkManager from updates repo, NetworkManager* stuff
>  from release repo got installed. I tried to test the live-DVD with
>  virtualbox
>  
>  while loading gnome the virtualbox crashes and the guest os goes to
>  aborted mode. Tried with runlevel 3 , everything worked fine, switched
>  to root and started X server, it showed the regular root user warning,
>  on closing the warning message again guest os crashes and goes to
>  aborted mode. Is it possible to get the log messages from a live-cd
>  that crashes completely? 
>  
>  
>  Tried the ISO with virt-manager i am getting same old "No root device
>  found" error .
>  
>  Here is the kick start file
>  http://psgkriya.org/saga/misc/msec-fedora-remix.ks 
I think you're hitting an unrelated bug (that is new to me).

Are you really saying that it crashes when X starts if you
--excludepkgs=NetworkManager*, but if you delete that flag, then X
starts fine? That is very weird.

James

[Arun SAG]

On Thu, Sep 2, 2010 at 3:09 AM, James Heather <j.heather(a)surrey.ac.uk&gt;wrote:

>  >I think you're hitting an unrelated bug (that is new to me).
>  
yes.

>  >Are you really saying that it crashes when X starts if you
>  >--excludepkgs=NetworkManager*, but if you delete that flag, then X
>  >starts fine? That is very weird.
>  
I removed the --excludepkgs=NetworkManager* and used the latest
NetworkManager, still X crashes and Guest goes to aborted mode. Yes it is a
new bug :( ,i see this symptom after the recent kernel update.

-- 
Arun S.A.G

[Arun SAG]

On Thu, Sep 2, 2010 at 10:28 AM, Arun SAG <sagarun(a)gmail.com&gt; wrote:

>  >I removed the --excludepkgs=NetworkManager* and used the latest
>  NetworkManager, still X crashes and Guest goes >to aborted mode. Yes it is a
>  new bug :( ,i see this symptom after the recent kernel update.
>
>  
In my fedora-live-bases.ks file I modified the updates repo to exclude the
stuff mentioned in #comment25
https://bugzilla.redhat.com/show_bug.cgi?id=624028

repo --name=updates --mirrorlist=
http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f13&...

Everything is back to normal now. Thanks Scott,James,Bruno :-)

-- 
Arun S.A.G

[Scott Dowdle]

Greetings,

----- Original Message -----
>  On Thu, Sep 2, 2010 at 10:28 AM, Arun SAG < sagarun(a)gmail.com >
> wrote:
>  In my fedora-live-bases.ks file I modified the updates repo to exclude
>  the stuff mentioned in #comment25
>  https://bugzilla.redhat.com/show_bug.cgi?id=624028
>  
>  repo --name=updates --mirrorlist=
>  http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f13&...
>  --excludepkgs=NetworkManager*,udev,dbus-glib
>  
>  Everything is back to normal now. Thanks Scott,James,Bruno :-) 
That might work for now... but I can definitely imagine that future updates are going to
cause additional dependency conflicts when they can't find the versions of the
excluded packages they expect to be there.

With the way I'm doing it, I get the updates before the broken package.  The way you
are doing it, you are getting the initial distro release versions.  I know there have been
several cycles of updates to NetworkManager and udev too.  Your way does save a lot of
disk space though compared to my way... although I am using symlinks.

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]

[Scott Dowdle]

Greetings,

----- Original Message -----
>  I am trying to create live cd using livecd-creator. I found this
>  anaconda bug https://bugzilla.redhat.com/show_bug.cgi?id=626780 which
>  crashes anaconda after the device selection stage. Any idea on how to
>  get around this? 
As noted in the bug report (which is closed because it is a duplicate of a private bug us
non-redhatters can't get to)... the bug has been fixed in an updated anaconda in
Fedora 14.  I certainly hope they will be updating the Fedora 13 package to fix this too!

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]