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

--swarm errors when trying to create a new Azure host #6012

Closed
taktran opened this issue Sep 20, 2016 · 4 comments
Closed

--swarm errors when trying to create a new Azure host #6012

taktran opened this issue Sep 20, 2016 · 4 comments

Comments

@taktran
Copy link

taktran commented Sep 20, 2016

Rancher Version:
v1.2.0-pre3

Docker Version:
Docker version 1.11.2, build b9f10c9

OS and where are the hosts located? (cloud, bare metal, etc):
Azure on Ubuntu 14.04

Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node rancher

Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle

Steps to Reproduce:

I upgraded to v1.2.0-pre3 from v1.1.0-dev2 using these instructions (incl creating rancher-data), then tried to create a new Azure instance with the following settings

  • Name: something-2016-09-15
  • Environment: [left blank]
  • Region: West Europe
  • Availability Set: [left blank]
  • Resource Group: [left blank]
  • Subscription ID: my-id
  • Client ID/Client Secret: my-id
  • Network: [left blank]
  • Image: [left blank]
  • Storage: Standard LRS
  • Size: Medium
  • Docker port: 2376
  • Open port: [left blank]
  • SSH user: someone

Results:

I get the error --swarm Configure Machine to join a Swarm cluster.

I've also gotten --swarm-addr addr to advertise for Swarm (default: detect and use the machine IP), and --swarm-experimental Enable Swarm experimental features from changing some of the fields around. Can try and replicate if need be. If I change Environment to AzureCloud, I get exit status 1.

Expected:

Machine to be create.

@tfiduccia
Copy link

@taktran When you say [left blank] do you mean you took out the default information or you just left it alone?

@taktran
Copy link
Author

taktran commented Sep 21, 2016

Yup @tfiduccia, I just left the field blank, and from the logs it seems to take the placeholder text.

From some digging, it seems like the default values are specified here: https://github.com/rancher/ui/blob/master/translations/en-us.yaml#L2265

@tfiduccia
Copy link

tfiduccia commented Sep 22, 2016

So I am unable to reproduce your bug (I am going through the UI) but there are a few suggestion I have for you to try:

  1. Azure machine names must be lowercase alphanumeric and between 4-62 characters. You can't use uppercase characters or less than 4 characters for the name.
  2. I would not leave most of those fields blank. I removed the fields in the UI and they did not use the placeholder info, it sent them through as blank. Here is what my Placement, Network and Instance sections look like.
    image
    image
    image
  3. Check the Access in Azure to make sure you have the proper permissions set.

@tfiduccia
Copy link

@taktran - found a new issue with Azure machine, please see issue #6048. If you find you need to remove that Azure password - Exec into the server container (docker exec -it <container id> bash) and rm -rf ~/.docker/machine/credentials/azure

@will-chan will-chan added this to the Unscheduled milestone Oct 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants