Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RHEL 8 needs to be added #322

Closed
WingsLikeEagles opened this issue Jul 30, 2019 · 1 comment
Closed

RHEL 8 needs to be added #322

WingsLikeEagles opened this issue Jul 30, 2019 · 1 comment

Comments

@WingsLikeEagles
Copy link

Expected behavior

Option for RHEL 8

Actual behavior

Only RHEL 6 and 7 are available

Steps to reproduce behavior

No steps required to reproduce. See file ChrootBuild.sh for most of the difference.

Context/Specifications

Latest RHEL 8 AMI (not beta) appears to be ami-f2641e93 in GovCloud

Suggestions for fix

The following packages seem to be unavailable in RHEL 8 include grub, libudev, sysvinit-tools
Repos have changed names and naming format.
yum-config-manager is now dnf config-manager
This specifically effects the file (but maybe more)
ChrootBuild.sh

Relevant references

  • How to list the latest available RHEL images on Amazon Web Services (AWS) https://access.redhat.com/solutions/15356
  • aws ec2 describe-images --owners 219670896067 --query 'sort_by(Images, &CreationDate)[*].[CreationDate,Name,ImageId]' --filters "Name=name,Values=RHEL-8*" --region us-gov-west-1 --output table
@ferricoxide
Copy link
Member

Hello. Thank you for expressing interest in EL8 support. Note that, while we plan to update spel to include EL8 builders, we won't begin to work on that functionality until

  • CentOS.Org has officially released CentOS 8 (see CO8 Build-Status). Our primary development and testing platform for each ELx release is CentOS. Thus, we cannot begin work until CentOS has released their EL8 derivative.
  • Fedora has made EL8 repositories available (see EPEL 8 Support Status). Because the AMIs are enabled with AWS utilities and those utilities have, historically, had dependencies on the EPEL project, we cannot begin work on an EL8 release until those (potential) dependencies have been tested and resolved.

As of today's date, neither of the above is true.

Initial efforts around supporting EL8 within spel will be managed through the AMIgen8 project. Suggest you follow the progress of that project if you wish to be kept apprised of the EL8-related activities that will underpin EL8-support within this project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants