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

KeyError('charm',) #1600

Closed
Coolfeather2 opened this issue May 16, 2019 · 18 comments
Assignees

Comments

@Coolfeather2
Copy link

@Coolfeather2 Coolfeather2 commented May 16, 2019

Report

Thank you for trying conjure-up! Before reporting a bug please make sure you've gone through this checklist:

Please provide the output of the following commands

ubuntu@nathan-ubuntu:~$ which juju
/snap/bin/juju
ubuntu@nathan-ubuntu:~$ juju version
2.6.2-bionic-amd64
ubuntu@nathan-ubuntu:~$
ubuntu@nathan-ubuntu:~$ which conjure-up
/snap/bin/conjure-up
ubuntu@nathan-ubuntu:~$ conjure-up --version
conjure-up 2.6.7
ubuntu@nathan-ubuntu:~$
ubuntu@nathan-ubuntu:~$ which lxc
/usr/bin/lxc
ubuntu@nathan-ubuntu:~$ /snap/bin/lxc config show
-bash: /snap/bin/lxc: No such file or directory
ubuntu@nathan-ubuntu:~$ /snap/bin/lxc version
-bash: /snap/bin/lxc: No such file or directory
ubuntu@nathan-ubuntu:~$
ubuntu@nathan-ubuntu:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
ubuntu@nathan-ubuntu:~$

Please attach tarball of ~/.cache/conjure-up:

tar cvzf conjure-up.tar.gz ~/.cache/conjure-up
[conjure-up.tar.gz](https://github.com/conjure-up/conjure-up/files/3185605/conjure-up.tar.gz)

Sosreport

Please attach a sosreport:

sudo apt install sosreport
sosreport
sosreport (version 3.6)

no valid plugins were enabled

The resulting output file can be attached to this issue.

What Spell was Selected?

Canonical Kubernetes

What provider (aws, maas, localhost, etc)?

vSphere

MAAS Users

Which version of MAAS?

Commands ran

Please outline what commands were run to install and execute conjure-up:

sudo snap install conjure-up --classic
conjure-up

Additional Information

Configured no add-ons

@blinkeye

This comment has been minimized.

Copy link

@blinkeye blinkeye commented May 19, 2019

I can confirm the error with a slightly different setup:

$ which juju
/snap/bin/juju

$ juju --version
2.6.2-bionic-amd64

$ which conjure-up
/snap/bin/conjure-up

$ conjure-up --version
conjure-up 2.6.7

$ which lxc
/snap/bin/lxc

$ /snap/bin/lxc config show
config: {}

$ /snap/bin/lxc --version
3.13

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"

$ uname -a
Linux braindump 5.1.3-050103-generic #201905161442 SMP Thu May 16 18:44:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ dpkg -l maas
ii  maas  2.5.3-7533-g65952b418-0ubuntu1~18.04.1

I'm using MAAS v2.5.3 and conjured-up kubernetes-core with the debug flag:

conjure-up kubernetes-core --debug

please see the zipped ~/.cache/conjure-up: conjure-up.tar.gz

NOTE: this used to work a couple of month ago.

Workaround:

The setup/deployment of the juju-controller works, so I installed a more recent juju with:

sudo snap install juju --classic

which installs juju v2.6.2

NOTE: the conjure-up snap uses an older juju version:

$ conjure-up.juju --version
2.5.0-bionic-amd64

and continued with snap juju v2.6.2:

juju deploy kubernetes-core

successfully.

@battlemidget

This comment has been minimized.

Copy link
Contributor

@battlemidget battlemidget commented May 19, 2019

Will get this upgraded

@gildas

This comment has been minimized.

Copy link

@gildas gildas commented May 21, 2019

Just to make sure. How long should we wait? I tried today and chose "Charned Distribution of Kubernetes" and it still fails the same way.
Even after doing a sudo snap install juju --classic.

@blinkeye

This comment has been minimized.

Copy link

@blinkeye blinkeye commented May 21, 2019

After it fails, did you continue the installation with (in your case):

juju deploy canonical-kubernetes
@gildas

This comment has been minimized.

Copy link

@gildas gildas commented May 21, 2019

After it fails, did you continue the installation with (in your case):

juju deploy canonical-kubernetes

No. Let me try that again.

@gildas

This comment has been minimized.

Copy link

@gildas gildas commented May 21, 2019

After it fails, running juju deploy canonical-kubernetes worked. No need to install juju, as it was already on 2.6.2.
So, is it a conjure-up UI glitch only?

@blinkeye

This comment has been minimized.

Copy link

@blinkeye blinkeye commented May 21, 2019

From what you wrote above:

Just to make sure. How long should we wait? ...
Even after doing a sudo snap install juju --classic.

you installed a snap juju version v2.6.2 - which is newer than the one that comes bundled with conjure-up. And that's exactly what @battlemidget fixed with: 888e1e1

@battlemidget

This comment has been minimized.

Copy link
Contributor

@battlemidget battlemidget commented May 21, 2019

I need to bump up libjuju to 0.11.5 as well. I'll do that in the next hour

@battlemidget battlemidget reopened this May 21, 2019
@gildas

This comment has been minimized.

Copy link

@gildas gildas commented May 21, 2019

I can re-run the test if you need. Just give me a howler.

@battlemidget

This comment has been minimized.

Copy link
Contributor

@battlemidget battlemidget commented May 21, 2019

Just pushed it to the builders, should be available in the next 30 minutes or so

@gildas

This comment has been minimized.

Copy link

@gildas gildas commented May 21, 2019

Thanks, that part is working now.

Now, conjure-up kubernetes fails later with the error:

hostname 'X.Y.Z.O' doesn't match either of 'juju-apiserver', 'juju-mongodb', 'localhost'

But this is another issue, IMO. I will search and maybe open another issue.

@battlemidget

This comment has been minimized.

Copy link
Contributor

@battlemidget battlemidget commented May 22, 2019

Yeah I noticed this late last night as well. Will need to dig into it some more

@gildas

This comment has been minimized.

Copy link

@gildas gildas commented May 22, 2019

Oh ok. So, at least I am not going nuts....

I will use kubeadm in the mean time as I need a k8s cluster, right now.
Will spin up a VM from time to time to check if this is getting there.

@battlemidget

This comment has been minimized.

Copy link
Contributor

@battlemidget battlemidget commented May 22, 2019

@gildas I would try https://microk8s.io before going with kubeadm

@blinkeye

This comment has been minimized.

Copy link

@blinkeye blinkeye commented May 22, 2019

@gildas I would try https://microk8s.io before going with kubeadm

I think by cluster he means a multi-node k8s cluster, not a single node cluster. @gildas: if I'm mistaken and you only need a single node k8s cluster I second @battlemidget recommendation, it's a joy to use! NOTE: in channel >=v1.14.1 dockerd was replaced with containerd, see this link for more information.

@gildas

This comment has been minimized.

Copy link

@gildas gildas commented May 22, 2019

Thanks. I already use microk8s. And I agree it is joy to install and use.
But for it's for dev and test. You cannot use it in production.
And certainly not in multi-nodes, which, as @blinkeye guessed, I want to do.

@battlemidget

This comment has been minimized.

Copy link
Contributor

@battlemidget battlemidget commented May 22, 2019

snap version is updated, feel free to give it another go

@battlemidget battlemidget self-assigned this May 22, 2019
@battlemidget

This comment has been minimized.

Copy link
Contributor

@battlemidget battlemidget commented Jun 5, 2019

This should be resolved now, feel free to reopen if not

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.