bugfix: fix grep command without -w option causing prefix matched whi…

[yangsenzk]

bugfix: fix grep command without -w option causing prefix matched while adding one etcd member

What type of PR is this?

/kind bug

What this PR does / why we need it:
when add a new etcd member to the existing cluster, the ansible role of etcd will check if the new etcd member ip is already in cluster with grep command **etcdctl member list | grep -q {{ etcd_access_address }} **. There is a chance that the new member ip string is prefix matched one of existing members, then the Configure | Check if member is in etcd cluster task will success with rc=0. For example, if there is a member with ip 192.168.7.84 in the existing cluster and want to add a new etcd member with ip 192.168.7.8, then the check command will pass and won't execute member join command any more. One of the fix method is adding -w option for grep command, which mean whole words matching.
Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Fix grep command without -w option causing prefix matched while adding one etcd member

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: yangsenzk (639a833)

[k8s-ci-robot]

Welcome @yangsenzk!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @yangsenzk. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mzaian]

Thanks a lot @yangsenzk I really like this fix :)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mzaian, yangsenzk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mzaian]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mzaian]

/ok-to-test

[yankay]

Thanks @yangsenzk

Very Nice

/lgtm