Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#223 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
30/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
ruby
Bereich
cli, networking

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Ruby
Sterne
2
Forks
12
Ø Merge
7 T. 3 Std.
Gemergte PRs (30 T.)
2

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus simp/rubygem-simp-cli

Alle Issues in simp/rubygem-simp-cli

Ähnliche Issues

Weitere Issues zu Ruby

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.