Description of problem: Attempting to do an unattended kickstart installation, anaconda fails to find the group "Base". I can select continue, but this defeats the purpose of kickstart in that I expect the installation to be unattended. Additionally, I have tried to include in %packages, either @redhat-storage or "@Red Hat Storage", and again neither is found by anaconda. Version-Release number of selected component (if applicable): How reproducible: Network install from HTTP of the contents of: https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=19269 Steps to Reproduce: 1. loop mount ISO image, and serve over HTTP 2. create a standard kickstart file but point installation at the ISO contents. 3. installation fails with error message regarding not finding Base. Actual results: Installation stalls until user interaction. Expected results: Fully automated installation. Additional info:
Attached you will find where the installer stalls. A continue, and it seems to work. The comps file does not have Base. I have attempted to explicitly remove @ Base with "-@ Base" in the kickstart file, but no luck. Kambiz
Created attachment 847841 [details] screenshot
Also, here is the sanitized kickstart file the host uses: # oh ok # generic kickstart - not specific to any group install url --url http://myhost-that-serves-rhs2-1.internal.redhat.com:8080/distro/RHSS2.1/ lang en_US.UTF-8 selinux --permissive keyboard us skipx network --device em1 --activate --bootproto static --hostname somehost --ip=192.168.100.1 --netmask=255.255.255.0 --gateway=192.168.100.254 --nameserver=192.168.100.200 rootpw --iscrypted somethinggoeshere firewall --service=ssh authconfig --useshadow --enablemd5 timezone UTC bootloader --location=mbr --driveorder=sda --append="nofb quiet splash=quiet" --md5pass=somethingoesheretoo zerombr yes clearpart --all --initlabel part raid.01 --ondisk=sda --size=512 part raid.02 --ondisk=sda --size=65536 part raid.03 --ondisk=sda --size=1 --grow part raid.04 --ondisk=sdb --size=512 part raid.05 --ondisk=sdb --size=65536 part raid.06 --ondisk=sdb --size=1 --grow part raid.07 --size=1 --ondisk=sdc --asprimary --grow part raid.08 --size=1 --ondisk=sdd --asprimary --grow part raid.09 --size=1 --ondisk=sde --asprimary --grow part raid.10 --size=1 --ondisk=sdf --asprimary --grow part raid.11 --size=1 --ondisk=sdg --asprimary --grow part raid.12 --size=1 --ondisk=sdh --asprimary --grow part raid.13 --size=1 --ondisk=sdi --asprimary --grow part raid.14 --size=1 --ondisk=sdj --asprimary --grow part raid.15 --size=1 --ondisk=sdk --asprimary --grow part raid.16 --size=1 --ondisk=sdl --asprimary --grow part raid.17 --size=1 --ondisk=sdm --asprimary --grow part raid.18 --size=1 --ondisk=sdn --asprimary --grow raid /boot --fstype=ext4 --level=1 --device=md0 raid.01 raid.04 raid swap --level=1 --device=md1 raid.02 raid.05 raid / --fstype=ext4 --level=1 --device=md2 raid.03 raid.06 text reboot %packages -@ Base yum-utils wget telnet screen tcpdump ntpdate ntp
This issue is reproducible only when the kickstart installation is done using the RHSS ISO as source tree, and the kickstart file does not specify '%packages --nobase'. When the kickstart installation is done using RH Satellite, as documented in the link given below, the installation is successful. https://access.redhat.com/site/documentation/en-US/Red_Hat_Storage/2.1/html/Installation_Guide/sect-Installation_Guide-Install_RHS-from_Satellite_server.html So editing the summary (title) of this BZ to reflect this difference. Note: * if no yum group is mentioned in the kickstart file %packages section, it defaults to installing the Base group. * if base group is not be used, then the following is to be given in the kickstart file %packages --nobase * the current documented method of installing RHSS 2.1 over the network, is by installing the 'redhat-storage-server' package, over a @Base installation of RHEL 6.4
The group redhat-storage (aka "Red Hat Storage"), as defined in the comps file of the RHS2.1 ISO image is not marked as uservisible. As such, I cannot find it via "yum grouplist", or "yum groupinstall". However, I am able to install the groups referenced via: yum groupinstall core glusterfs-all glusterfs-swift rhs-tools scalable-file-systems
The network kickstart installation of RHSS 2.1 may be performed using source tree from RH Satellite, PXE, or a network shared ISO extract. The %packages section of the kickstart file currently needs to use only the redhat-storage-server package name to install RHSS, as in %packages redhat-storage-server This will pull in all the gluster* packages and their dependencies. In addition to this, the Base yum comps group of packages is by default installed as well, for the underlying OS platform. Currently this works only for RH Satellite based kickstart installations. For PXE, or a network shared ISO extract, the automated kickstart installation breaks due to the issue reported in this BZ. So marking BZ as TestBlocker
(In reply to Rejy M Cyriac from comment #7) > The network kickstart installation of RHSS 2.1 may be performed using source > tree from RH Satellite, PXE, or a network shared ISO extract. > > The %packages section of the kickstart file currently needs to use only the > redhat-storage-server package name to install RHSS, as in > > %packages > redhat-storage-server %packages --nobase @core @rhs-tools @scalable-file-systems @glusterfs-all @glusterfs-swift redhat-storage-server is what I'd expect you'd want if you want to specify a %packages section in a ks pointing at the tree on the RHSS iso. I would not have expected a %packages section to be required at all with the latest isos, however. Cheers, aj
(In reply to Anthony Towns from comment #8) > (In reply to Rejy M Cyriac from comment #7) > > The network kickstart installation of RHSS 2.1 may be performed using source > > tree from RH Satellite, PXE, or a network shared ISO extract. > > > > The %packages section of the kickstart file currently needs to use only the > > redhat-storage-server package name to install RHSS, as in > > > > %packages > > redhat-storage-server > > > %packages --nobase > @core > @rhs-tools > @scalable-file-systems > @glusterfs-all > @glusterfs-swift > redhat-storage-server > > > is what I'd expect you'd want if you want to specify a %packages section in > a ks pointing at the tree on the RHSS iso. I would not have expected a > %packages section to be required at all with the latest isos, however. > > Cheers, > aj The groups specified here, except for 'Core', are all internal groups existing only within RHSS ISO, not used at RHN/RH_Satellite, and not documented anywhere. The network installs from RH Satellite cannot use these groups anyway as well. Either we need to incorporate the Base group in the yum comps for RHSS ISO, or we would have to document that the '--nobase' switch has to used in the %packages section of the kickstart file, for all automated network installs. I would go for the first option, and the RHEL6 ISO already recognizes the Base group as well.
When I've specified "redhat-storage-server", anaconda reports that it doesn't know anything about that group. Do I add it as: @redhat-storage-server or as: redhat-storage-server ? The group is defined in the comps file, but does not have the user-visible xml definition set to true, like the other groups that are included in the comps file.
(In reply to Kambiz Aghaiepour from comment #10) > When I've specified "redhat-storage-server", anaconda reports that it > doesn't know anything about that group. Do I add it as: > > @redhat-storage-server > > or as: > > redhat-storage-server ? No "@" -- it's the package that you want. (It's also part of the @rhs-tools group though) > The group is defined in the comps file, It is? It's not in the comps file I have... Cheers, aj
Base group added mirroring current RHS Core group.
Tested using RHSS-2.1-20140130.0-RHS-x86_64-DVD1.iso Upon specifying the base group, or core group, or no group at all, along with the redhat-storage-server package, in the %packages section of the kickstart file used to install RHSS, the kickstart installation proceeds uninterrupted, and the resultant RHSS system has exactly the same packages installed. Marking as Verified.