Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tether should update (instead of appending) containerName in /etc/hosts after changing the VM name in guestinfo #4075

Closed
chengwang86 opened this issue Feb 28, 2017 · 1 comment
Assignees
Labels
kind/defect Behavior that is inconsistent with what's intended priority/p2
Milestone

Comments

@chengwang86
Copy link
Contributor

VIC version:

0.8

Deployment details:

What was the vic-machine create command used to deploy the VCH?
bin/vic-machine-linux create --name=vch-1 --target=root:pwd@192.168.60.162 --thumbprint=... --debug 1 --no-tlsverify --no-tls

Steps to reproduce:

1.	docker run –it –name=t1 busybox
2.	govc vm.change -vm t1* -e guestinfo.vice./common/name=t2
3.	docker stop t1
4.	docker start containerID_of_t1
5.	docker attach containerID_of_t1

Actual behavior:

vi /etc/hosts
127.0.1.1 t1 cb4acd2807e0 t2

Expected behavior:

vi /etc/hosts
127.0.1.1 cb4acd2807e0 t2
@chengwang86 chengwang86 added priority/p2 kind/defect Behavior that is inconsistent with what's intended labels Feb 28, 2017
@chengwang86
Copy link
Contributor Author

By this PR #4134, we have removed containerName from /etc/hosts. So this issue does not exist anymore.

@chengwang86 chengwang86 added this to the Sprint 5 milestone Mar 26, 2017
@chengwang86 chengwang86 self-assigned this Mar 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/defect Behavior that is inconsistent with what's intended priority/p2
Projects
None yet
Development

No branches or pull requests

1 participant