On 02/28/2013 04:00 PM, Van Pelt, Cheri wrote:
We have our autotest server setup to boot RHEL 6.x and 7.x kernels. Now we are
attempting to boot SLES11 SP2 kernels.
I am getting errors like this:
02/27 17:52:16 INFO | boottool:0498| Installing grubby because it was not
found on this system
02/27 17:52:16 ERROR| boottool:0598| _run_get_output error while running:
"/sbin/grubby --version"
02/27 17:52:16 WARNI| boottool:1180| Could not run grubby to fetch its version
02/27 17:52:16 WARNI| boottool:0571| Could not detect current grubby version.
It may be that you are running an unsupported version of grubby
02/27 17:52:16 ERROR| boottool:0620| _run_get_output_err error while running:
"/sbin/grubby --bootloader-probe"
02/27 18:17:31 ERROR| job:1330| JOB ERROR: Unable to instantiate boottool
It appears that /sbin/grubby exists on RHEL system but not SLES systems. Is
there some switch we can throw so that we can boot kernels on SLES systems?
I can boot the SLES kernel manually on the SLES machines, so I know I'm
starting with a good kernel.
To make a long story short, if there is no suitable grubby version
installed, we'll try to push a tarball and build it. RHEL grubby
versions are not recent enough, so we have to build it from source, so
it's not like we're trying to favor RHEL here. The only systems where
this will work out of the box are Fedora 17 and 18.
There are a bunch of packages that you need to have installed in your box:
PKGS = ['gcc', 'make', 'libpopt-dev', 'libblkid-dev']
Boottool will even try to do its best to install things, but right now
we have build deps classes only for Debian/Ubuntu and RHEL/Fedora. Look in
client/tools/boottool.py
We have
class DebianBuildDeps(object):
class RPMBuildDeps(object):
So we'd need to create a SUSEBuildDeps class that uses zypper and
installs the right packages.
So, would you please open an issue on our issue tracker?
https://github.com/autotest/autotest/issues/new
If you could send a patch with the class, even better :) In case you
don't have time for it, I'll create one. Another thing you can do is to
ensure the libpopt-dev and libblkid-dev equivalent packages are
installed on your test machine.
Cheers,
Lucas
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
