Bug 1644023 - Update images with new kernel for more 4 Gb UEFI
Summary: Update images with new kernel for more 4 Gb UEFI
Keywords:
Status: CLOSED DUPLICATE of bug 1637671
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director-images
Version: 10.0 (Newton)
Hardware: x86_64
OS: All
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Mike Burns
QA Contact: Gurenko Alex
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-29 19:01 UTC by Edu Alcaniz
Modified: 2021-12-10 18:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 12:32:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3661541 0 None None None 2018-10-29 19:01:13 UTC

Description Edu Alcaniz 2018-10-29 19:01:13 UTC 
Description of problem:
We found an issue with Huawei HW that RHEL 7.5.x 7.6.x 7.7.x can't support more 4 Gb UEFI

Error deploying new node 
EFI stub: ERROR: Failed to alloc highmem for initrd


https://bugzilla.redhat.com/show_bug.cgi?id=1608955

We have a hotfix for the different kernels. We need to update the rhos-director-images 

Version-Release number of selected component (if applicable):
RHOSP10.
rhosp-director-images-10.0-20180821.1.el7ost.noarch
rhosp-director-images-ipa-10.0-20180821.1.el7ost.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
New compute nodes can't be deployed by kernel restriction on EFI memory

Expected results:
Update the director images with the new kernels.


Additional info:
Comment 2 Edu Alcaniz 2018-10-30 06:29:34 UTC 
It is necessary a new agent.ramdisk or build the ramdisk for new kernel.
Comment 3 Mike Burns 2018-10-30 12:32:42 UTC 
The following bugs track respins for RHEL 7.6 are scheduled to ship in the next couple days.  Closing this as a duplicate

Bug 1636214 OSP 10
Bug 1637671 OSP 13

*** This bug has been marked as a duplicate of bug 1637671 ***
Note You need to log in before you can comment on or make changes to this bug.