Redhat Enterprise Linux 6.2 support

[roldancer]

Hi,

    Is RHEL 6.2 supported right now ? we need to create some appliances on RHEL 6.2

Thanks.

[goldmann]

We haven't tested this exact version, but there shouldn't be any issues with supporting it. It should just work.

--Marek

[roldancer]

Hi Marek

     I'm using the BoxGrinder's Meta Appliance to build appliances, Is it posible to use the Meta Appliance to build appliances based on RHEL 6.2 ?

Thanks.

[goldmann]

Yes, you need to have access to the ISO, for example downloaded via https://access.redhat.com/home, then mount it, and point your repos section to the mounted dir.

--Marek

[roldancer]

Hi Marek

     I'm trying to build a RHEL 6 appliance but I'm getting the following error,

I think I should mount RHEL ISO image and define it as a local repository, right ?

This is my very simple/fisrt appliance definition

name: wasAppliance

summary: WebSphere Appliance

os:

  name: rhel

  version: 6

  password: temporal

hardware:

  partitions:

    "/":

      size: 2

packages:

  - @base

files:

  "/":

    - "scripts/nada.sh"

post:

  base:

    - "echo 'Hi Cristian' > /etc/platform"

    - "/bin/bash /scripts/nada.sh"

[root@localhost appliances]# boxgrinder-build jeos.appl -p vmware --platform-config type:personal,thin_disk:true

I, [2012-04-05T07:55:10.057834 #1204]  INFO -- : Validating appliance definition from jeos.appl file...

I, [2012-04-05T07:55:10.061849 #1204]  INFO -- : Appliance definition is valid.

I, [2012-04-05T07:55:10.071732 #1204]  INFO -- : Building 'wasAppliance' appliance for x86_64 architecture.

I, [2012-04-05T07:55:10.075775 #1204]  INFO -- : Resolving packages added to wasAppliance appliance definition file...

F, [2012-04-05T07:55:10.300645 #1204] FATAL -- : RuntimeError: Packages curl, grub, kernel, system-config-firewall-base for wasAppliance appliance not found in repositories. Please check package names in appliance definition file.

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/lib/boxgrinder-build/plugins/os/rpm-based/rpm-dependency-validator.rb:62:in `resolve_packages'

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/lib/boxgrinder-build/plugins/os/rpm-based/rpm-based-os-plugin.rb:67:in `build_with_appliance_creator'

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/lib/boxgrinder-build/plugins/os/rhel/rhel-plugin.rb:33:in `build_rhel'

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/lib/boxgrinder-build/plugins/os/rhel/rhel-plugin.rb:57:in `execute'

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/lib/boxgrinder-build/plugins/base-plugin.rb:172:in `run'

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/lib/boxgrinder-build/appliance.rb:184:in `execute_plugin'

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/lib/boxgrinder-build/appliance.rb:207:in `execute_without_userchange'

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/lib/boxgrinder-build/appliance.rb:129:in `execute_plugin_chain'

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/lib/boxgrinder-build/appliance.rb:125:in `each'

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/lib/boxgrinder-build/appliance.rb:125:in `execute_plugin_chain'

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/lib/boxgrinder-build/appliance.rb:164:in `create'

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/bin/boxgrinder-build:202

/usr/bin/boxgrinder-build:19:in `load'

/usr/bin/boxgrinder-build:19

Thanks!!!!

[goldmann]

Yes, you need to mount it and add appropriate lines in repos section in your appliance definition file.

--Marek

[bigfatflea]

Hello,

Must the repo be on the meta appliance?

I created a RHEL 6.3 repo from iso and put it on its own vm. I verified I can install packages from this repo, (http) but when I try to use it in a definition file it fails.

In the log I see this:

...

D, [2012-08-08T20:37:58.179686 #28907] DEBUG -- : Mounting /dev/loop01 at /root/appliances/build/appliances/x86_64/rhel/6/rhel6.3-basic/1.5/rhel-plugin/tmp/imgcreate-YLbw9k/install_root/

D, [2012-08-08T20:37:58.236958 #28907] DEBUG -- : Writing mkinitrd config /root/appliances/build/appliances/x86_64/rhel/6/rhel6.3-basic/1.5/rhel-plugin/tmp/imgcreate-YLbw9k/install_root/etc/sysconfig/mkinitrd

D, [2012-08-08T20:37:58.489559 #28907] DEBUG -- : Retrieving http://benzene/repos/rhel6.3ws_x86-64/repodata/repomd.xml ...OK

D, [2012-08-08T20:37:58.648740 #28907] DEBUG -- : Skipping missing group 'core'

D, [2012-08-08T20:38:06.817407 #28907] DEBUG -- : warning: libgcc-4.4.6-4.el6.x86_64: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY

D, [2012-08-08T20:38:06.857722 #28907] DEBUG -- : ['/']

D, [2012-08-08T20:38:06.900028 #28907] DEBUG -- : Installing: libgcc                       ##################### [  1/113]

D, [2012-08-08T20:38:07.280345 #28907] DEBUG -- : Installing: setup                        ##################### [  2/113]

...

T, [2012-08-08T20:39:52.999209 #28907] TRACE -- : GFS: mount --bind /sys /sysroot/sys

T, [2012-08-08T20:39:53.094504 #28907] TRACE -- : GFS: /bin/sh -c /usr/bin/passwd -d root

T, [2012-08-08T20:39:53.988199 #28907] TRACE -- : GFS: /bin/sh: /usr/bin/passwd: No such file or directory

T, [2012-08-08T20:39:53.993092 #28907] TRACE -- : GFS: umount /sysroot/sys

T, [2012-08-08T20:39:54.156223 #28907] TRACE -- : GFS: umount /sysroot/selinux

T, [2012-08-08T20:39:54.207666 #28907] TRACE -- : GFS: umount /sysroot/proc

T, [2012-08-08T20:39:54.258302 #28907] TRACE -- : GFS: umount /sysroot/dev/pts

T, [2012-08-08T20:39:54.309083 #28907] TRACE -- : GFS: umount /sysroot/dev

T, [2012-08-08T20:39:54.361082 #28907] TRACE -- : GFS: guestfsd: error: /bin/sh: /usr/bin/passwd: No such file or directory

guestfsd: main_loop: proc 111 (sh) took 1.50 seconds

D, [2012-08-08T20:39:54.361382 #28907] DEBUG -- : GFS: sh = NULL (error)

F, [2012-08-08T20:39:54.365658 #28907] FATAL -- : Guestfs::Error: sh: /bin/sh: /usr/bin/passwd: No such file or directory

/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.2/lib/boxgrinder-build/plugins/os/rpm-based/rpm-based-os-plugin.rb:223:in `sh'

...

and the build fails.

Are these two things related? I tried swapping '@Base' for '@core' in the definition file but got the same failure.

[msavy]

Edward,

Can you please run reposync again, with the following flag enabled

{code}--download-metadata{code}

By default, I believe that meta-data such as groups (e.g. @core, @base) are not imported.

[bigfatflea]

I wasn't able to make that work, but I was able to use this:

[root@benzene rhel6.3ws_x86-64]# createrepo . -g rhel-workstation-6.3-x86_64-dvd/repodata/20988aba66e9981de0d1cca7058e9b9d138f226e8fee912f1c96a4a757e9059f-comps-rhel6-Workstation.xml

and it was your clue that led me to it. Thank you.

The repodata directory now has:

[root@benzene rhel6.3ws_x86-64]# \ls -l repodata

total 6860

-rw-r--r--. 1 root root 1153153 Aug  9 21:17 20988aba66e9981de0d1cca7058e9b9d138f226e8fee912f1c96a4a757e9059f-comps-rhel6-Workstation.xml

-rw-r--r--. 1 root root  211946 Aug  9 21:17 20988aba66e9981de0d1cca7058e9b9d138f226e8fee912f1c96a4a757e9059f-comps-rhel6-Workstation.xml.gz

-rw-r--r--. 1 root root 3311828 Aug  9 21:17 filelists.xml.gz

-rw-r--r--. 1 root root  919475 Aug  9 21:17 other.xml.gz

-rw-r--r--. 1 root root 1414244 Aug  9 21:17 primary.xml.gz

-rw-r--r--. 1 root root    2093 Aug  9 21:17 repomd.xml

[root@benzene rhel6.3ws_x86-64]#

Is this complete? What other kinds of things can go in there?

[msavy]

That looks great, did you encounter any other issues? Or was it smooth sailing?

The usual sort of stuff that goes into the meta-data is groups, package-lists etc. You probably have everything of importance there already.