ClusterLabs / ClusterLabs/resource-agents
awsvip monitor returns success when it shall not
- Dominant language
- Shell
- Stars
- 519
- Forks
- 608
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
currently the aws_monitor returns sucess when it can grep the secondary_ip from the awscli describe instance response.
However, if the secondary private ip is a substring of the current primary private ip, it returns incorrectly success even when the secondary private ip is not attached to the instance.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the aws_monitor implementation and inspect how the awscli describe-instance response is matched for the secondary_ip. Reproduce the case where that value is a substring of the primary private IP, then verify that monitor success occurs only when the secondary IP is actually attached.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, shell
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100