search

conjure-up / spells

conjure-up spells registry
79 stars 37 forks source link

conjure-up: no xenial images found #241

Closed tburow closed 5 years ago

tburow commented 5 years ago

ok, Im new to this tool, so my apologies in advance if i missed something obvious

specifically this is for spell canonical-kubernetes

following through this walk through https://docs.conjure-up.io/stable/en/walkthrough

on this run, I chose not to use jaas and the tool failed to find the AMI needed for deployment. I suspect this is releated to AWS moving to ubuntu 18 lts, but it was not obvious If I could specify a specific ami or version.

I did do a search on existing and old issues and faqs etc. and I did not see anything obvious that I may have missed.

conjure-up 2.6.0 Juju 2.5.0-mojave-amd64

2019-01-22 17:41:58,260 [DEBUG] conjure-up/canonical-kubernetes - juju.py:253 - bootstrap cmd: ['/usr/local/bin/juju', 'bootstrap', 'aws/us-east-1', 'conjure-up-aws-dbc', '--default-model', 'conjure-canonical-kubern-d35', '--config', 'image-stream=daily', '--bootstrap-series', 'xenial', '--credential', 'datadev'] 2019-01-22 17:42:05,315 [ERROR] conjure-up/canonical-kubernetes - common.py:60 - Error bootstrapping controller: ['Creating Juju controller "conjure-up-aws-dbc" on aws/us-east-1', 'Looking for packaged Juju agent version 2.5.0 for amd64', 'Launching controller instance(s) on aws/us-east-1...', ' - Verifying availability zone', 'ERROR failed to bootstrap model: cannot start bootstrap instance: no "xenial" images in us-east-1 with arches [amd64]']

thanks in advance

johnsca commented 5 years ago

The error is from Juju and indicates that it couldn't find the instance image to use when creating the controller. Testing it myself now, I was unable to replicate the issue. Considering Juju 2.5 was just recently released, I suspect this was a transient issue with the timing of getting the images out to the image repository. Can you please try this again and see if it has resolved itself? Thanks.

tburow commented 5 years ago

Yea I’ve tried multiple times with the same error.

If I choose jaas for hosted deployment I get past that but it’s constantly failing on the compleation step for kubectl

Same results with core also.

johnsca commented 5 years ago

I'm not really sure what the issue is, since I'm able to bootstrap with Juju 2.5.0 on AWS us-east-1 without issue. I've opened a Juju Discourse thread asking for assistance from the Juju folks.

mitechie commented 5 years ago

Check that if you're using a really old aws account that you have a valid default VPC please.

tburow commented 5 years ago

hmm that brings up a different point, how do I specify a specific vpc and no public IPs? but that's tertiary to the fact I cant seem to get this to work out of the box in basic form.

Two errors that seem to have a common theme are

If I run a deploy in The Jaas web console, things seem to work fine. but running from conjure-up on cli it fails in both deployment scenerios with different errors.

this is out of the box, no custom configs

tburow commented 5 years ago

im going to close this issue as unresolved. I'm going to move on to another tool and dont want to take more of folks time. ty for your suggestions