Description of problem: In the classic Node we kept many of the dependencies in the kickstart files. This is not very scalable. The better way is to express the dependencies of the image as dependencies of an rpm installed within the image. The idea of this bug is to create an ovirt-releaseXY-host-node subpackage, which has the mandatory dependencies, and also includes some necessary files for integration (i.e. /etc/os.release.d/50-ovirt-node-host). See [1] for the current dependencies [1] https://gerrit.ovirt.org/gitweb?p=ovirt-appliance.git;a=blob;f=node-appliance/ovirt-node-appliance.ks;h=f3e3f6deb60c333ff4d247024f437289ce703a8b;hb=HEAD#l36-53
The minimum dependencies are: 40 dracut-config-generic 41 42 # EFI support 43 grub2-efi 44 shim 45 efibootmgr 52 # For image based updates 53 imgbased Once this ovirt-releaseXY-host-node package exists, it should be the only package given in the packages section of the Node kickstart
The /etc/os.release.d/ contents should be similar to echo "VARIANT=\"Cloud Edition\"" >> $RPM_BUILD_ROOT/usr/lib/os.release.d/os-release-cloud echo "VARIANT_ID=cloud" >> $RPM_BUILD_ROOT/usr/lib/os.release.d/os-release-cloud sed -i -e "s|(%{release_name})|(Cloud Edition)|g" $RPM_BUILD_ROOT/usr/lib/os.release.d/os-release-cloud from http://pkgs.fedoraproject.org/cgit/fedora-release.git/tree/fedora-release.spec#n117
Fixed in https://gerrit.ovirt.org/gitweb?p=ovirt-release.git;a=commit;h=fefc35cb4d6e9eda90d34a12fef44db64ba37127