Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#223 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
ruby
领域
cli, networking

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Ruby
星标
2
派生
12
平均合并
6 天 6 小时
30 天内合并 PR
3

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

simp/rubygem-simp-cli 的其他 Issue

查看 simp/rubygem-simp-cli 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。