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
salt-cloud deployment fails when deploy: True #34547
Comments
@sebw what versions of pvmomi and httplib are you using? Also to be clear this only occurs when using a custom script correct? |
@Ch3LL yes it happens with any script actually, not only custom. pyvmomi (6.0.0.2016.6) Regarding httplib, this is what I find:
This is the latest version of the package available on RHEL7:
|
I have a custom grain module polling our CMDB to retrieve information using httplib. |
I disabled my custom grains so they don't interfere and I'm still getting the same trace. I tried to install httplib2 (pip install httplib2) but it doesn't help. |
Would you mind attempting to install an older version of pyvmomi I just want to rule out that this is not the issue you are running into. Also you state that you are deploying from a redhat7 template with salt already installed. Have you attempted to build this out from a different OS template and do you still see the same error? |
I have a similar error as @sebw using:
when switch to using:
also has issues.. because the salt vmware driver is using some keywords that are not available.
so i removed them from 3 calls.
then after all that... still hit issues... I forget what, just that some calls didn't work. |
@nmadhok perhaps you have feedback. i'm going to install a signed cert today... if this does not resolve the issue then going to have to start some low level debugging. |
note posted a |
Okay I am able to replicate this but ONLY when using the python api:
When I run it normally with |
this will work because it does not use the cached connection.
try this code listed in #36598 where I have a state file that makes more than one call using cloud
|
@Ch3LL opps i see im already talking to you in the other thread :) |
Thanks for clarifying that for me. Just wanted to make sure the original reporter was not just simply running |
Will do on Monday and report back. Thanks :) |
I'm deploying from a RedHat Enterprise 7 template where salt-minion 2016.3.1 is already installed (from official repositories) with a basic configuration. For different reasons I can't use the bootstrap script.
I use a custom script to finish the deployment, but I get a traceback and the minion key is rejected from the Master. Salt-minion refuses to start as a result. I'm getting the same error using bootstrap-salt.
salt-minion -l debug:
In the template, Salt-minion is set not to start at boot (or I get noname as minion_id). The custom script
/etc/salt/cloud.deploy.d/vmware-finishing.sh
is supposed to enable salt-minion and start it.This is the profile:
This is the stacktrace:
Master:
Minion:
The text was updated successfully, but these errors were encountered: