![]() MasterEvent PULL socket URI: /var/run/salt/master/master_event_pull.ipc MasterEvent PUB socket URI: /var/run/salt/master/master_event_pub.ipc Insecure logging configuration detected! Sensitive data may be logged. Configuration file path: /etc/salt/master Missing configuration file: /root/.saltrc Using cached minion ID from /etc/salt/minion_id: saltstack Reading configuration from /etc/salt/master Version: Ubuntu 16.04 salt -l debug '*03' test.ping It looks like the minion can access the master fine and do transaction (the master sending information too), but the master cannot see the minion by itself. The master can successfully ping the machine with a normal ping ip.address However, calling any command from the master, even a salt 'machine' test.ping, will fail. If running a salt-call test.ping from the machine, then the machine is accepted on the master and can successfully apply a state. MINION MASTERS CODES 2018 INSTALLNow with the latest version, we install the new package (from a clean machine), run the same salt-config, but the machine is not added to the master key list nor visible. We have the auto-accept option on master so after that, the machine is normally added automatically to the key list and works. run `salt-config -i "machine-name" -m "".MacOS El capitan Steps to Reproduce Issue Now we are setting up new MacOS machines and found that using the latest minion 2018.3.0 doesn't connect to the master anymore, but previous version 2017.7.2 does work. We upgraded the Windows machines to 2018.3.0, all good. ![]() All the currently set-up machines are still working fine. We are were using salt with 2017.7.2 on both master and minions on both MacOS and Windows, then upgraded the master to 2018.3.0. ![]() On MacOS the latest minion 2018.3.0 is not recognised by the master. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |