ironcore-dev / ironcore-dev/FeDHCP
Fix subnet detection for plugin `ipam`
Open
Nobody has claimed this yet.
area/metal-automation
bug
- Dominant language
- Go
- Stars
- 3
- Forks
- 8
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 7
Description
Subnet detection fails, it seems it depends on the subnet order in the config map.
It could be IPAM bug also, investigate and fix
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing subnet detection with the subnets in different config-map orders, then inspect the plugin ipam entry point and determine whether the fault is in FeDHCP or IPAM. Done means subnet detection no longer depends on ordering, with a regression test covering reordered configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100