[OMN-DEF] Dual-stack row without IB_IPV6 silently accepted
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- ansible, python, yaml
- Domain
- backend, networking
Research direction
Find the orchestrator validation for ib_addr_mode and PXE mapping rows, starting from the validation entry point used when running orchestrator validation. Check how dual-stack rows handle missing IB_IPV4, then make the missing-IB_IPV6 case produce a validation error when IB_NIC_NAME is set. Done means the reproduced row is rejected with an error like the one in the issue.
Written by the indexing model from the issue text.
Description
Defect
When ib_addr_mode is dual-stack, a PXE mapping row that has IB_NIC_NAME and IB_IPV4 set but IB_IPV6 empty is accepted without error. This results in an asymmetric cluster where some nodes have dual-stack IB addresses and others have only IPv4 despite the mode requiring both.
Steps to Reproduce
- Set ib_addr_mode to dual-stack in network_spec.yml
- Create a PXE mapping row with IB_NIC_NAME and IB_IPV4 set, but IB_IPV6 empty
- Run orchestrator validation
Expected Result
In dual-stack mode, every row that has IB_NIC_NAME set should also require both IB_IPV4 and IB_IPV6 to be set. Validation should reject rows missing either:
orchestrator_config: Mapping row 4 must set IB_IPV6 when ib_addr_mode is dual-stack and IB_NIC_NAME is set.
Actual Result
Validation returns rc=0 with zero errors. The row is silently accepted with only IPv4.
- 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 72/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
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
FinanceFlash/unvibecode#577 · 1 comment ·
Maintainers usually reply within 1 day
-
area/test type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Clodmony/starship-coop#70 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
punitarani/fli#270 ·
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
jumpserver/jumpserver#17980 ·
Maintainers usually reply within 1 day
-
community enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day