saltstack启动报错:importError: No module named certifi

[root@localhost ~]# systemctl start salt-master
Job for salt-master.service failed. See 'systemctl status salt-master.service' and 'journalctl -xn' for details.
[root@localhost ~]# systemctl status salt-master.service
salt-master.service - The Salt Master Server
   Loaded: loaded (/usr/lib/systemd/system/salt-master.service; disabled)
   Active: failed (Result: exit-code) since Sat 2019-08-17 04:05:10 CST; 8s ago
     Docs: man:salt-master(1)
           file:///usr/share/doc/salt/html/contents.html
           https://docs.saltstack.com/en/latest/contents.html
  Process: 1696 ExecStart=/usr/bin/salt-master (code=exited, status=64)
 Main PID: 1696 (code=exited, status=64)

Aug 17 04:05:10 localhost.localdomain salt-master[1696]: File "/usr/lib/python2.7/site-packages/salt/utils/event.py", li...ule>
Aug 17 04:05:10 localhost.localdomain salt-master[1696]: import tornado.iostream
Aug 17 04:05:10 localhost.localdomain salt-master[1696]: File "/usr/lib64/python2.7/site-packages/tornado/iostream.py", ...ule>
Aug 17 04:05:10 localhost.localdomain salt-master[1696]: from tornado.netutil import ssl_wrap_socket, ssl_match_hostname...ults
Aug 17 04:05:10 localhost.localdomain salt-master[1696]: File "/usr/lib64/python2.7/site-packages/tornado/netutil.py", l...ule>
Aug 17 04:05:10 localhost.localdomain salt-master[1696]: import certifi
Aug 17 04:05:10 localhost.localdomain salt-master[1696]: ImportError: No module named certifi
Aug 17 04:05:10 localhost.localdomain systemd[1]: salt-master.service: main process exited, code=exited, status=64/n/a
Aug 17 04:05:10 localhost.localdomain systemd[1]: Failed to start The Salt Master Server.
Aug 17 04:05:10 localhost.localdomain systemd[1]: Unit salt-master.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

根据上述报错"ImportError: No module named certifi，"
没有安装certifi.则执行如下命令：
安装pip

wget https://bootstrap.pypa.io/get-pip.py
python get-pip.py

安装模块
pip install certifi

然后进入python
import certifi

运行通过
重新启动，则解决问题