No description
6f622fb7c9
I have seem some occasional odd failures coming from the "dnf -y update" done by elements/base/install.d/00-up-to-date. dnf seems to sometimes think a package is not installed when it really is. It then seems to try and re-install them, but notices they are installed, and then bails with a failure exit [1]. The packages that seem to cause this vary, but the common thread is that they seem to have all been installed during the initial phase of installing the package manager in the chroot. I suspect that when we are building the chroot, we do our initial install with the "external" yum & rpm. Then we start using the dnf/yum in the chroot, but we're actually using meta-data created by the *external* tools -- which could be vastly different versions or who-knows-what. While I honestly I don't have an exact root cause, empirically I've found rebuilding the rpm db always seems to fix things up. So this change takes care to rebuild the rpm db with the chroot version of rpm, and clear out the package metadata for a refresh with "update". This should hopefully put us in a consistent state. [1] http://paste.openstack.org/show/487356/ Change-Id: I565df23897ae511356c4861fdbe63823fa6b6ff9 |
||
|---|---|---|
| bin | ||
| diskimage_builder | ||
| doc/source | ||
| elements | ||
| lib | ||
| 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.