Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

simp config network setup depends on the archived pupmod-simp-network (ifcfg), which can't work on EL10

Ouverte
  • Quelque chose ne va pas ?
#223 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
30/100
Type d'issue
Bug
Clarté
À clarifier
Activité
Active
Stack technique
ruby
Domaine
cli, networking

Piste de recherche

Start with Item::ConfigureNetworkAction in lib/simp/cli/config/items/action/configure_network_action.rb and the dependency entries in build/rubygem-simp-cli.spec. Compare the three proposed approaches for EL8–EL10 support, then update the action and release dependencies after a decision is made. Done means the chosen network setup works on supported EL versions and the RPM dependencies match the current release set.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

needs-attention

Problem

When simp config is asked to configure the network (cli::network::* items), Item::ConfigureNetworkAction (lib/simp/cli/config/items/action/configure_network_action.rb, around line 38) runs a puppet apply of network::eth{'<interface>': …} from pupmod-simp-network:

  • pupmod-simp-network is archived on GitHub, and it is not part of the current release set (it isn't in simp-core's metadata.json).
  • It manages interfaces through /etc/sysconfig/network-scripts/ifcfg-* files. EL10 removed ifcfg support from NetworkManager (EL9 only deprecated it), so on EL10 network::eth writes files that nothing reads.
  • The CLI RPM still Requires:/Recommends: pupmod-simp-network >= 6.0.3 (build/rubygem-simp-cli.spec lines 79 and 105). A release built from the current module set can't satisfy that dependency.

So on an EL10 SIMP server, simp config's network step can't work, and the CLI RPM can't be installed from a repository that contains only current components.

Options (needs a decision)

  1. Configure with NetworkManager directly. Have the action run nmcli connection modify/up (or write a keyfile under /etc/NetworkManager/system-connections/) instead of applying a Puppet class. That needs no module dependency, and it works on EL8, EL9 and EL10.
  2. Use a maintained community module. The CLI's apply step would then depend on, for example, an NetworkManager-capable Vox Pupuli module, which would have to be added to the release set.
  3. Drop network configuration from simp config. It would assume the network was configured at install time (kickstart/anaconda, or cloud-init), keeping only the hostname/DNS/resolv items.

Whichever is chosen, the spec's pupmod-simp-network dependency (and the pupmod-simp-simp_grub / pupmod-herculesteam-augeasproviders_grub entries next to it) needs updating to match the release set.

Langage dominant
Ruby
Étoiles
2
Forks
12
Merge moyen
6 j 6 h
PR mergées (30 j)
3

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de simp/rubygem-simp-cli

Toutes les issues de simp/rubygem-simp-cli

Issues similaires

Plus d'issues Ruby

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.