Bug 1280394 - rhel-osp-director: 8.0 - unable to build the agent-ramdisk image.
Summary: rhel-osp-director: 8.0 - unable to build the agent-ramdisk image.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: diskimage-builder
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: 8.0 (Liberty)
Assignee: Mike Burns
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-11 16:15 UTC by Alexander Chuzhoy
Modified: 2016-04-07 21:11 UTC (History)
6 users (show)

Fixed In Version: diskimage-builder-1.2.0-1.el7ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-07 21:11:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0603 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 Enhancement Advisory 2016-04-08 00:53:53 UTC

Description Alexander Chuzhoy 2015-11-11 16:15:14 UTC
rhel-osp-director: 8.0 - unable to build the agent-ramdisk image.


Environment:
instack-undercloud-2.1.3-1.el7ost.noarch
python-tripleoclient-0.0.11-5.el7ost.noarch

Steps to reproduce:
1. Deploy the undercloud
2. Attempt to build the images with "openstack overcloud image build --all"

Result:
ironic-python-agent.initramfs  doesn't get created.


Attempt to build just the agent-ramdisk type with: "openstack overcloud image build --type=agent-ramdisk"

Exits with error:
Could not open requirements file: [Errno 2] No such file or directory: '/tmp/ironic-python-agent/requirements.txt'

Expected result:
All the required images should be created with no issues.

Comment 2 Mike Burns 2015-11-11 17:19:08 UTC
Need to pull in newer diskimage-builder.

Comment 4 Amit Ugol 2015-11-22 01:17:24 UTC
I was able to build everything and later deploy using those images

Comment 6 errata-xmlrpc 2016-04-07 21:11:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0603.html


Note You need to log in before you can comment on or make changes to this bug.