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

Unable to start a machine on Exoscale #2818

Closed
vincentbernat opened this issue Nov 25, 2015 · 5 comments
Closed

Unable to start a machine on Exoscale #2818

vincentbernat opened this issue Nov 25, 2015 · 5 comments
Assignees
Labels
area/machine Issues that deal with rancher-machine kind/bug Issues that are defects reported by users or that we know have reached a real release

Comments

@vincentbernat
Copy link

Hey!

When starting a new host on Exoscale. we get the following error: Unsupported type: []string. This is because the securityGroup configuration parameter should be a string and not an array. In go-machine-service, the generated JSON is incorrect:

        "securityGroup": {
            "type": "array[string]",
            "nullable": true
        },

This should be:

        "securityGroup": {
            "type": "string",
            "nullable": true
        },

I didn't understand how this file is generated. The copy in rancher/machine repository is up-to-date but somehow, when the files are regenerated with scripts/generate, they are still wrong.

@deniseschannon deniseschannon added kind/bug Issues that are defects reported by users or that we know have reached a real release area/machine Issues that deal with rancher-machine labels Nov 25, 2015
@deniseschannon deniseschannon added this to the Milestone 12/2/2015 milestone Nov 25, 2015
@wlan0
Copy link

wlan0 commented Nov 25, 2015

The generation code is correct. It correctly interpreted the type []string from this flag exoscale.go#L78. This is a bug in go-machine-service. We are not parsing flags correctly - create.go#L242

@vincentbernat
Copy link
Author

Thanks for the pointer. I'll try to fix that then (unless you already have some kind of solution).

@wlan0
Copy link

wlan0 commented Nov 25, 2015

Don't worry about it. I'll fix it before the end of the day today. It'll be added to the next release.

@wlan0
Copy link

wlan0 commented Nov 26, 2015

@vincentbernat - This PR fixes it - rancher/go-machine-service#69

@vincentbernat
Copy link
Author

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/machine Issues that deal with rancher-machine kind/bug Issues that are defects reported by users or that we know have reached a real release
Projects
None yet
Development

No branches or pull requests

3 participants