Salt failing, all debugs checking out

@100digital wrote:

Hello All,

I'm having some issues activating my instance of virl... this is an esxi deployment. I've reset salt keys a few times, and I continue to receive failure messages via virl administration web UI;

"Failed to collect current salt contact status: 'module' object has no attribute 'config'"

...the following message is displayed via 'http://virlhostname:19400/admin/salt/'

output via 'virl@virl:~$ sudo salt-call -l debug test.ping;

[DEBUG ] Reading configuration from /etc/salt/minion
[DEBUG ] Including configuration from '/etc/salt/minion.d/_schedule.conf'
[DEBUG ] Reading configuration from /etc/salt/minion.d/_schedule.conf
...etc...
[DEBUG ] Including configuration from '/etc/salt/minion.d/openstack.conf'
[DEBUG ] Reading configuration from /etc/salt/minion.d/openstack.conf
[DEBUG ] Initializing new SAuth for ('/etc/salt/pki/minion', '98A60E13.virl.info', 'tcp://173.37.45.136:4506')
[DEBUG ] Decrypting the current master AES key
[DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
[DEBUG ] Loaded minion key: /etc/salt/pki/minion/minion.pem
[DEBUG ] LazyLoaded jinja.render
[DEBUG ] LazyLoaded yaml.render
[DEBUG ] LazyLoaded test.ping
[DEBUG ] Re-using SAuth for ('/etc/salt/pki/minion', '98A60E13.virl.info', 'tcp://173.37.45.136:4506')
[DEBUG ] LazyLoaded nested.output
local:
True

--valid ntp--

virl@virl:~$ ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
+somehostname 128.138.140.44 2 u 27 64 377 1.301 -129459 3.161
+janotherhostname 64.250.229.100 2 u 29 64 377 1.026 -129461 3.100
...etc

many thanks,

regards,

Jason

Posts: 1

Participants: 1

Read full topic