RHEL Scheduler Provisioning Fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- ruby
- Domain
- devops, infrastructure
Research direction
Start at specs/default/chef/site-cookbooks/gridengine/recipes/scheduler.rb line 32 and review the package-install branch for RHEL alongside the AlmaLinux/CentOS/Rocky cases. Use the Jetpack.log error and the RHEL 7_9 scheduler image details to reproduce or validate the failure. Done means provisioning no longer fails while setting up EPEL on RHEL.
Written by the indexing model from the issue text.
Description
Provisioning version cyclecloud-gridengine 2.0.13 fails on a RHEL scheduler due to the scheduler.rb file line 32 where it tries to install the epel-release package. Jetpack.log error messages:
2022-09-12 18:16:48,120 ERROR Software configuration failed: Chef::Exceptions::Package: yum_package[epel-release] (gridengine::scheduler line 32) had an error: Chef::Exceptions::Package: No candidate version available for epel-release
2022-09-12 18:16:48,120 ERROR Recommendation: Review local log files on the VM at /opt/cycle/jetpack/logs
The prior change to this file for almalinux support changed the switch from 'centos' to 'rhel'. In moving from version 2.0.11 to 2.0.12+ this code now executes on a rhel VM whereas previously it was disabled. However, to install the EPEL repos on Red Hat the repository must be added manually instead of installing the epel-release package as in Alma/CentOS/Rocky.
Cluster Information:
cyclecloud-gridengine version: 2.0.13
scheduler image: RedHat:RHEL:7_9:latest
gridengine version: 2011.11j (DRMAA Java API added)
base template: altair-grid-engine (we are using a customized template built off the base altair template)
- Dominant language
- Python
- Stars
- 7
- Forks
- 18
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/cyclecloud-gridengine
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
All issues in Azure/cyclecloud-gridengine
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
canonical/paas-charm#368 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
StevenBlack/hosts#3256 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
qualcomm/qai-appbuilder#275 ·