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

hostname is not defined correctly in machines #6441

Closed
zetaab opened this issue Feb 3, 2019 · 1 comment · Fixed by #6442
Closed

hostname is not defined correctly in machines #6441

zetaab opened this issue Feb 3, 2019 · 1 comment · Fixed by #6442
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@zetaab
Copy link
Member

zetaab commented Feb 3, 2019

1. What kops version are you running? The command kops version, will display
this information.

master

2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.

1.11.6

3. What cloud provider are you using?
openstack

4. What commands did you run? What is the simplest way to reproduce this issue?

kops create cluster \
  --cloud openstack \
  --name oma.k8s.local \
  --state ${KOPS_STATE_STORE} \
  --zones nova \
  --network-cidr 10.1.0.0/16 \
  --image ubuntu \
  --master-count=3 \
  --node-count=1 \
  --node-size m1.small \
  --master-size m1.small \
  --etcd-storage-type lvmdriver-1 \
  --api-loadbalancer-type public \
  --topology private \
  --bastion \
  --networking weave \
  --os-ext-net public --yes

5. What happened after the commands executed?

After cluster is up and running, each instance hostname is same called oma.

6. What did you expect to happen?

I except that each instance should have its own exact same hostname that exist in cloudprovider api (in this case openstack). Example: oma.k8s.local-master-nova-1-1 or oma.k8s.local-master-nova-2-1 and so on. Should we insert this to cloud-init?

/kind bug

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Feb 3, 2019
@zetaab
Copy link
Member Author

zetaab commented Feb 5, 2019

solved by replacing dots with - in hostnames

@zetaab zetaab closed this as completed Feb 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants