Bug 1353634 - Extjs URL no longer valid
Summary: Extjs URL no longer valid
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: sahara-image-elements
Version: 9.0 (Mitaka)
Hardware: All
OS: Linux
high
medium
Target Milestone: ga
: 9.0 (Mitaka)
Assignee: Elise Gafford
QA Contact: Luigi Toscano
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-07 15:39 UTC by Elise Gafford
Modified: 2016-08-15 07:18 UTC (History)
2 users (show)

Fixed In Version: sahara-image-elements-4.0.1-2.el7ost
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
: 1381320 (view as bug list)
Environment:
Last Closed: 2016-08-15 07:18:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:1597 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 9 Release Candidate Advisory 2016-08-11 16:06:52 UTC

Description Elise Gafford 2016-07-07 15:39:36 UTC
Description of problem:

The previous URL for extjs (hosted at sencha) is no longer valid. This issue was repaired upstream in stable/mitaka, but did not make the last stable relese. This bug requires backport of this fix to RHOS 9.


How reproducible: 100%


Steps to Reproduce:
1. Run any image generation script which requires the extjs element.
2. Observe extjs download failure.

Actual results:

Extjs fails to install.

Expected results:

Extjs installs.

Additional info:

This bug can be fixed by setting EXTJS_DOWNLOAD_URL, but we don't want to force this workaround on customers.

Comment 2 Luigi Toscano 2016-07-20 17:38:10 UTC
The wrapper script provided by sahara-image-elements contains the new (working) path to the extjs-2.2 zip, so that generation of CDH 5.5 images works out of the box (no need to export EXTJS_DOWNLOAD_URL as workaround).

Verified on:
sahara-image-elements-4.0.1-2.el7ost.noarch
diskimage-builder-1.13.0-1.el7ost.noarch
dib-utils-0.0.9-1.el7ost.noarch

Comment 4 errata-xmlrpc 2016-08-15 07:18:58 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-1597.html


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