-
Notifications
You must be signed in to change notification settings - Fork 73
Failing to conjure-up kubernetes [Errno 113] Connect call failed ('x.x.x.x', 17070) #1476
Comments
I am having the same issue on my setup Is there a work-around for this |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
same issue here is there a fix ? |
Also encountered issue, removed and reinstalled lxd too, no luck |
I have same issue after removing conjure-up, all lxc containers and re-installing conjure-up which juju juju version conjure-up --version |
i have same issue
|
detail for this 2019-04-10 15:56:45,839 [DEBUG] conjure-up/openstack-novalxd - gui.py:78 - Starting watcher for verifying LXD server is available. |
oh, maybe not have juju controller, you can run this code and run choice create a location controller, so successed |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Report
Thank you for trying conjure-up! Before reporting a bug please make sure you've gone through this checklist:
sudo snap refresh conjure-up --edge
? YesPlease provide the output of the following commands
Please attach tarball of ~/.cache/conjure-up:
Sosreport
Please attach a sosreport:
The resulting output file can be attached to this issue.
What Spell was Selected?
kubernetes
What provider (aws, maas, localhost, etc)?
localhost maas
MAAS Users
Which version of MAAS?
Commands ran
Please outline what commands were run to install and execute conjure-up:
Additional Information
I have installed The Canonical Distribution of Kubernetes using conjure-up, came across an issue here https://stackoverflow.com/questions/50970133/installed-kubernetes-on-ubuntu-and-i-see-a-lot-of-nodes-are-getting-created-in-m so I deleted the VMs manually, since then kubernetes does not start.
conjure-down kubernetes and conjure-up kubernetes do not work
The text was updated successfully, but these errors were encountered: