Azure / Azure/cyclecloud-gridengine
RHEL Scheduler Provisioning Fails
- Lingua principale
- Python
- Stelle
- 7
- Fork
- 18
- Merge medio
- 5g 21h
- PR unite (30g)
- 2
Descrizione
Provisioning version cyclecloud-gridengine 2.0.13 fails on a RHEL scheduler due to the [scheduler.rb](https://github.com/Azure/cyclecloud-gridengine/blob/66dfc1ae837d8198a1bed53b15c0e4f57c4e35ae/specs/default/chef/site-cookbooks/gridengine/recipes/scheduler.rb#L32) 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](https://github.com/Azure/cyclecloud-gridengine/commit/66dfc1ae837d8198a1bed53b15c0e4f57c4e35ae) 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](https://docs.fedoraproject.org/en-US/epel/#_el7) 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)
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Inizia dalla riga 32 di specs/default/chef/site-cookbooks/gridengine/recipes/scheduler.rb e rivedi il ramo package-install per RHEL insieme ai casi AlmaLinux/CentOS/Rocky. Usa l’errore di Jetpack.log e i dettagli della RHEL 7_9 scheduler image per riprodurre o convalidare il problema. Il lavoro è completato quando il provisioning non fallisce più durante la configurazione di EPEL su RHEL.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- ruby
- Ambito
- devops, infrastructure
- Tipo di issue
- Bug
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Stato di attività
- Ferma
- Chiarezza
- Specificata chiaramente
- Idoneità per principianti
- 45/100