"Failure in step 02_get-kubectl after-deploy" #1457
Comments
I have no idea how to attach a file here for the requested files. |
Yep I'll have a go at that in the next day or so - I hacked the kube config out for now and I'm still using the cluster. It would be interesting to see if you can recreate this. As an aside I tried to run the after-deploy script manually and it failed because the python script that it calls was trying to import yaml, however the python3-yaml package was not installed. I did try again after installing that package but it still failed. Dunno if it's related but worth mentioning. |
@battlemidget |
Have the similar issue with conjure-up 2.6.4 from edge
|
Same issue:
|
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
?Please 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 Users
Which version of MAAS?
Commands ran
Please outline what commands were run to install and execute conjure-up:
Just "conjure-up" and select appropriate options.
Additional Information
Here's the error in the log. Very hard to figure out from this where the script is failing.
The text was updated successfully, but these errors were encountered: