mayadata-io / mayadata-io/cstorpoolauto
bug: use hostname vs. nodename appropriately
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
CStorPoolAuto currently makes use of nodename & node uid. It needs to take into account both hostname as well as nodename based on the environments.
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 locating CStorPoolAuto’s handling of nodename and node uid, then compare the hostname and nodename values used in the relevant environments. Done means the operator selects the appropriate node identifier for each environment; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100