This repository was archived by the owner on Feb 3, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 3, 2021. It is now read-only.
Aztk throws exception while creating a cluster #626
Description
Hello,
I'm trying to install aztk, but when I try to create a Cluster, it throws the following error:
Any suggestions on how to install Aztk without issue?
The commands that I used to install Aztk on the new machine (just created) are:
sudo apt install python3-pip
pip3 install --upgrade pip
pip install aztk --user
aztk spark init
modified secrets.yaml
aztk spark cluster create --id my_cluster --size 1 --vm-size standard_d2_v2
I'm using an Azure Standard A0 with Ubuntu 16.04 LTS machine.
Regards.
Activity
jafreck commentedon Jul 20, 2018
I was able to reproduce this issue when a
cluster.yamlfile is not present in the.aztkdirectory. Can you verify that you have a.aztk/cluster.yamlfile present in your working (or home) directory?I also was able to reproduce this issue if the
plugins:key incluster.yamlwas commented out. This is a bug, which I will fix. If you have commented this section out, then to mitigate until the fix lands, you can uncomment/add an empty plugins block:josefarinna commentedon Jul 23, 2018
Seems that my cluser.yaml is fine, I didnt modified it because the created one looks good, please find attached cluster.yaml file:
cluser.txt
josefarinna commentedon Jul 23, 2018
I just realize that I have that issue when I try to create the cluster from the .aztk folder, If I move to the user's folder where the .aztk folder is located, I have a different issue:
I have aztk installed on another machine, used the same secrets.yaml configuration and in that machine everything is working fine.
jafreck commentedon Jul 24, 2018
I believe the second error is a result of having an underscore in your cluster name. That is an ugly error we should clean up, though. I will file a separate bug for that issue. I believe that is unrelated to the main issue with the configuration file.
Your configuration file looks good at first glance. I will see if I can reproduce using that config.
josefarinna commentedon Jul 30, 2018
Sorry for the late response.
After doing more checks (creating and destroying the machine) I ended up that this issue happens only if I launch the command from .aztk folder, if I'm on the users folder everything works fine.
jafreck commentedon Jul 30, 2018
Glad you found a mitigation. The error should still be cleaned up, though, so I'll leave this open.