08d6a9f93d
It seems in the grub cleanup in Iafe3611f4eec3c6357587a6cae6a30a261686ead I managed to unintentionally drop systemd from the yum-minimal builds. By not pre-installing grub we dropped some dependencies; the path is tortured ... grub2 -> os-prober -> udev -> systemd-udev -> systemd (we don't even want os-prober! So this whole thing was working by accident). This manifests in *very* confusing ways. Currently centos-minimal builds are failing late in the build with services unable to enabled. dib-init-system was actually trying to tell us that it didn't know what init was installed (because systemd wasn't actually installed), but unfortunately it was not really failing. This meant the service files were not copied correctly from other elements, and thus fail to be enabled. I have corrected this with I076c08190d40c315ad6a6d96a3823e9fc52630be which would at least alert us earlier. For Fedora 24, due to a bug in dracut dependencies [1], missing the systemd-udev package fails the build of the initrd during the kernel install. This then results in an initrd-less, unbootable system (see also Ibaaa81124098f3c6febe48e455d3e1cd0a5f1761). Add these dependencies explicitly. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1398505 Change-Id: I24ce648485c3d6f3c27ab8f87a638516b3727017 |
||
---|---|---|
bin | ||
diskimage_builder | ||
doc/source | ||
elements | ||
lib | ||
releasenotes | ||
tests | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
babel.cfg | ||
bindep.txt | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Image building tools for OpenStack ================================== ``diskimage-builder`` is a flexible suite of components for building a wide-range of disk images, filesystem images and ramdisk images for use with OpenStack. This repository has the core functionality for building such images, both virtual and bare metal. Images are composed using `elements`; while fundamental elements are provided here, individual projects have the flexibility to customise the image build with their own elements. For example:: $ DIB_RELEASE=trusty disk-image-create -o ubuntu-trusty.qcow2 vm ubuntu will create a bootable Ubuntu Trusty based ``qcow2`` image. ``diskimage-builder`` is useful to anyone looking to produce customised images for deployment into clouds. These tools are the components of `TripleO <https://wiki.openstack.org/wiki/TripleO>`__ that are responsible for building disk images. They are also used extensively to build images for testing OpenStack itself, particularly with `nodepool <http://docs.openstack.org/infra/system-config/nodepool.html>`__. Platforms supported include Ubuntu, CentOS, RHEL and Fedora. Full documentation, the source of which is in ``doc/source/``, is published at: * http://docs.openstack.org/developer/diskimage-builder/ Copyright ========= Copyright 2012 Hewlett-Packard Development Company, L.P. Copyright (c) 2012 NTT DOCOMO, INC. All Rights Reserved. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.