Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#223 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
30/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
ruby
Domínio
cli, networking

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Ruby
Estrelas
2
Forks
12
Merge médio
1d 23h
PRs com merge (30d)
3

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de simp/rubygem-simp-cli

Todas as issues de simp/rubygem-simp-cli

Issues semelhantes

Mais issues de Ruby

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.