overcloud-full ramdisk being rebuilt twice

Bug #1660824 reported by Ben Nemec on 2017-01-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ben Nemec

Bug Description

We previously had https://github.com/openstack/instack-undercloud/blob/master/elements/overcloud-full/post-install.d/90-rebuild-ramdisk to force a rebuild with some extra modules enabled by packages we install.

Recently we also added https://github.com/openstack/tripleo-image-elements/blob/master/elements/overcloud-dracut/finalise.d/98-regenerate-initramfs which does essentially the same thing except it adds a couple more modules.

Both of these elements are included in the overcloud-full image, and as a result every image build wastes time rebuilding the ramdisk twice.

Tags: ci Edit Tag help

Fix proposed to branch: master
Review: https://review.openstack.org/427475

Changed in tripleo:
status: Triaged → In Progress
Changed in tripleo:
milestone: none → ocata-rc1

Reviewed: https://review.openstack.org/427475
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=f6771acae346a3bcdf913e1602d1e91589f6c868
Submitter: Jenkins
Branch: master

commit f6771acae346a3bcdf913e1602d1e91589f6c868
Author: Ben Nemec <email address hidden>
Date: Tue Jan 31 21:45:17 2017 +0000

    Remove ramdisk rebuild from overcloud-full element

    I1b0dd384a1981acffd64652708ec21323f5e795a in tripleo-image-elements
    added another forced ramdisk rebuild after this one, which makes
    this one redundant and a not-insignificant waste of time.

    Change-Id: I8f975ae661426be64887922dedd48b93774e3231
    Closes-Bug: 1660824

Changed in tripleo:
status: In Progress → Fix Released

This issue was fixed in the openstack/instack-undercloud release candidate.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers