[OMN-DEF] IPv6-only mode fails to assign IB addresses due to netmask check
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- ansible, python
- Domain
- infrastructure, networking
Research direction
Start with configure-ib-network.sh.j2, especially the unconditional NETMASK_BITS check at lines 68–71, and trace how ib_addr_mode selects IPv4 or IPv6 configuration. Check the related network configuration tests if available. Done when ipv6-only mode with empty IPv4 settings configures the IB IPv6 address without failing the IPv4 netmask check.
Written by the indexing model from the issue text.
Description
Defect
When ib_addr_mode is set to ipv6-only, the configure-ib-network.sh script fails to assign IPv6 addresses to IB interfaces. The script exits early with an error about missing IPv4 netmask before reaching the IPv6 configuration section.
Steps to Reproduce
- Set ib_addr_mode to ipv6-only in network_spec.yml
- Set ipv6_subnet and ipv6_netmask_bits
- Leave ipv4_subnet and ipv4_netmask_bits empty
- Run orchestrator provision
- Check node IB interface — no IPv6 address is assigned
Expected Result
In ipv6-only mode, the script should only require ipv6_netmask_bits and configure IPv6 addresses on the IB interface.
Actual Result
The script exits with error: "ERROR: IB network netmask_bits is not configured in network_spec.yml" because it unconditionally requires IPv4 netmask even in ipv6-only mode. The IB interface exists but has no IP address.
Root Cause
Line 68-71 in configure-ib-network.sh.j2 unconditionally checks NETMASK_BITS (IPv4 netmask) without considering ib_addr_mode. In ipv6-only mode, ipv4_netmask_bits is empty, causing the script to exit before IPv6 configuration.
- Dominant language
- Python
- Stars
- 9
- Forks
- 175
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 171
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dell/omnia
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
`src/telemetry/containers/build_images.sh` should have localcopy build_actionMay be free again @priti-parate claimed this 28 days ago, and no pull request is open. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
dell/omnia#5425 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Warning: SLURM_REPO_URL and SLURM_REPO_NAME must be provided.May be free again @priti-parate claimed this 28 days ago, and no pull request is open. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dell/omnia#5423 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
Similar issues
-
docs size:S
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
strawberry-graphql/strawberry#4794 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dataforgoodfr/cetolog#21 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
btclib-org/btclib#2932 ·
Maintainers usually reply within 1 day