node ls: clarify the meaning of 'status', availability and 'manager status' fields
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
The following is from a customer installation:
[ec2-user@ucp-replica-YnGeKNVo-17601 ~]$ sudo docker node ls
ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS
2o3j1q70ejfop2uqauedqrdvf nginx-member-C41eas7i-20816 Ready Active
4kpmve4w1ur9724xn869d3t7r ucp-replica-YnGeKNVo-19623 Down Active Reachable
For the one in bold, STATUS and MANAGER STATUS fields give contradictory info, at least at first look. This should be addressed.
Contributor 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.
Research direction
Start with the docker node ls entry point and the STATUS, AVAILABILITY, and MANAGER STATUS fields shown in the report. Trace where their meanings are documented or presented, then clarify how the fields relate so that the example's Down and Reachable values are understandable; done means the documentation or output no longer appears contradictory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100