Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1231934 - Size of generated image is too small for CDH and can not be configured
Size of generated image is too small for CDH and can not be configured
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: sahara-image-elements (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
unspecified Severity medium
: ga
: 7.0 (Kilo)
Assigned To: Elise Gafford
Luigi Toscano
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-06-15 12:09 EDT by Luigi Toscano
Modified: 2015-08-05 09:26 EDT (History)
4 users (show)

See Also:
Fixed In Version: sahara-image-elements-2015.1.0-3.el7ost.src.rpm
Doc Type: Bug Fix
Doc Text:
Previously, CDH image generation sometimes failed, because the image creation wrapper script specified too small a space for generation of the CDH image on some systems. Now, the image generation space is increased for CDH images, and images are generated successfully.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-05 09:26:39 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:1548 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2015-08-05 13:07:06 EDT

  None (edit)
Description Luigi Toscano 2015-06-15 12:09:37 EDT
Description of problem:
The sahara-disk-image-create utility script currently hard-codes the size of the temporary image created by diskimage-builder during the process:
export DIB_IMAGE_SIZE=5


It's quite easy to hit failures when generating CDH images (-p cloudera) as the total amount of data is really close to the 5 GB limit. A subscription with more channels than usual can use a relevant amount of disk space while caching the repositories which leads to a failure (not enough disk space) in the 'install-packages grub-pc' step when running /tmp/in_target.d/finalise.d/51-bootloader.


Nevertheless, the image size can't be configured. Workaround: manual editing of the script file; this is not a blocker as the generation scripts requires root privileges, but it is less flexible.


Version-Release number of selected component (if applicable):
sahara-image-elements-2015.1.0-2.el7ost.noarch
diskimage-builder-0.1.46-2.el7ost.noarch
dib-utils-0.0.9-1.el7ost.noarch
Comment 4 Luigi Toscano 2015-06-22 09:10:55 EDT
The size required for CDH images has been increased from 5 to 7 GiB, which is enough to build a CDH 5.3.0 image (it's still 5 for HDP 2.0.6 images, which was enough).

Both values are hard coded. This is not a long term solution, I hope, but validating the bug for now nevertheless.

Verified on:
sahara-image-elements-2015.1.0-3.el7ost.noarch
Comment 5 Elise Gafford 2015-06-22 14:05:15 EDT
@ Luigi: Because the disk image size set in DIB is not reflected in the final image size, I am uncertain that configurability is a feature in this case: the images require a certain reserved disk size to generate, and no more. If you see a use case for configurable disk image size in this case, I'd be happy to provide it, but I intentionally attempted to keep the flow fairly minimal. Let me know what you think.

Thanks,
Ethan
Comment 6 Luigi Toscano 2015-06-22 14:11:22 EDT
Sure(In reply to Ethan Gafford from comment #5)
> @ Luigi: Because the disk image size set in DIB is not reflected in the
> final image size, I am uncertain that configurability is a feature in this
> case

In fact, if the CDH image generation for 5.3.0 would need more space, that would mean that something strange changed on the CDH repositories, which would be a much bigger issue.
The limit just needs to be checked properly when new plugin versions will be introduced in future releases. So no strong point in fact for changing it.
Comment 8 errata-xmlrpc 2015-08-05 09:26:39 EDT
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://access.redhat.com/errata/RHEA-2015:1548

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