ce410de834
Because we are using the building platform's "yum" to do the initial install into the chroot, it is affected by the base-system's /etc/yum.conf. pip-and-virtaulenv in I82acb865378a0fa5903a6267bfcee0e2962eced0 added "exclude=python-pip..." in /etc/yum.conf to stop the package manager overwriting the installed pip. Now our CI images have built with this, we are now picking up this exclude on centos. Since on F24 dnf->python->python-pip we end up failing to build the the chroot because python-pip can not be satisifed. In a general sense, however, this could be caused by any configuration put into /etc/yum.conf that is incompatible with installing into the chroot. yum has the option to disable all excludes which is used here. This seems to be the best way to isolate the chroot install from any excludes that may have been done on the base system for various reasons. I did consider using a completely separate yum.conf we ship with dib ... but let's start simple. This should fix the current gate failures on centos Change-Id: I4e4cc8ed09a29c4057ade34ea93025139e191bf5 |
||
---|---|---|
bin | ||
diskimage_builder | ||
doc/source | ||
elements | ||
lib | ||
releasenotes | ||
tests | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
babel.cfg | ||
LICENSE | ||
MANIFEST.in | ||
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.