Skip to content
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

Invalid master key #46883

Closed
karpiozoo opened this issue Apr 5, 2018 · 1 comment
Closed

Invalid master key #46883

karpiozoo opened this issue Apr 5, 2018 · 1 comment
Labels
Duplicate Duplicate of another issue or PR - will be closed
Milestone

Comments

@karpiozoo
Copy link

Description of Issue

After upgrade to 2018.3.0 on some minions I get message "Invalid master key"
When I compared to hosts where minions works I saw difference with m2crypto packet installed on Centos 7.4
After yum remove m2crypto-0.21.1-17.el7.x86_64 minion seems to accept public key from master again.

salt-call pillar.items

[CRITICAL] The Salt Master server's public key did not authenticate!
The master may need to be updated if it is a version of Salt lower than 2018.3.0, or
If you are confident that you are connecting to a valid Salt Master, then remove the master public key and restart the Salt Minion.
The master public key can be found at:
/etc/salt/pki/minion/minion_master.pub

Setup

(Please provide relevant configs and/or SLS files (Be sure to remove sensitive info).)

Steps to Reproduce Issue

yum install m2crypto-0.21.1-17.el7.x86_64

Versions Report

salt-minion --versions-report
Salt Version:
           Salt: 2018.3.0
 
Dependency Versions:
           cffi: 1.6.0
       cherrypy: 5.6.0
       dateutil: 2.4.2
      docker-py: Not Installed
          gitdb: 0.6.4
      gitpython: 1.0.1
          ioflo: 1.3.8
         Jinja2: 2.7.2
        libgit2: 0.24.6
        libnacl: 1.4.3
       M2Crypto: 0.21.1
           Mako: 0.8.1
   msgpack-pure: Not Installed
 msgpack-python: 0.5.1
   mysql-python: Not Installed
      pycparser: 2.14
       pycrypto: 2.6.1
   pycryptodome: Not Installed
         pygit2: 0.24.2
         Python: 2.7.5 (default, Aug  4 2017, 00:39:18)
   python-gnupg: Not Installed
         PyYAML: 3.11
          PyZMQ: 15.3.0
           RAET: 0.6.5
          smmap: 0.9.0
        timelib: Not Installed
        Tornado: 4.2.1
            ZMQ: 4.1.4
 
System Versions:
           dist: centos 7.4.1708 Core
         locale: UTF-8
        machine: x86_64
        release: 3.10.0-693.21.1.el7.x86_64
         system: Linux
        version: CentOS Linux 7.4.1708 Core

@gtmanfred
Copy link
Contributor

This is the same issue as here.

#46868

It appears that there is an incompatiblity between m2crypto and pycrypto, so that the keys from one do not work with the other.

I am closing this as a duplicate.

@gtmanfred gtmanfred added the Duplicate Duplicate of another issue or PR - will be closed label Apr 5, 2018
@gtmanfred gtmanfred added this to the Blocked milestone Apr 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate Duplicate of another issue or PR - will be closed
Projects
None yet
Development

No branches or pull requests

2 participants