-
Couldn't load subscription status.
- Fork 5.6k
Open
Open
Copy link
Labels
RegressionThe issue is a bug that breaks functionality known to work in previous releases.The issue is a bug that breaks functionality known to work in previous releases.Sulfur v3006.0release code name and versionrelease code name and versionbugbroken, incorrect, or confusing behaviorbroken, incorrect, or confusing behaviordependencyunderlying Salt dependency issueunderlying Salt dependency issue
Description
Description
I did not change any configuration between 3005.1 and 3006.0 but suddently salt-master cannot find my public keys.
Setup
fileserver_backend:
- gitfs
gitfs_provider: pygit2
gitfs_remotes:
- ssh://[email protected]/myorg/mysalt.git:
- base: main
- root: salt
- pubkey: /root/.ssh/id_salt.pub
- privkey: /root/.ssh/id_salt
- https://github.com/saltstack/salt-winrepo-ng.git:
- all_saltenvs: master
- mountpoint: salt://win/repo-ng/salt-winrepo-ng
ext_pillar:
- git:
- main ssh://[email protected]/myorg/mypillar.git:
- env: base
- root: pillar
- pubkey: /root/.ssh/id_pillar.pub
- privkey: /root/.ssh/id_pillar- on-prem machine
- VM (Virtualbox, KVM, etc. please specify)
- VM running on a cloud service, please be explicit and add details
- container (Kubernetes, Docker, containerd, etc. please specify)
- or a combination, please be explicit
- jails if it is FreeBSD
- classic packaging
- onedir packaging
- used bootstrap to install
Steps to Reproduce the behavior
Upgrade from 3005.1 to 3006.0. Run salt-pip install pygit2.
Expected behavior
Should fetch gitfs normally.
Screenshots
[CRITICAL] SSH pubkey (/root/.ssh/id_salt.pub) for gitfs remote 'ssh://[email protected]/myorg/mysalt.git' could not be found, path may be incorrect. Note that it may be necessary to clear git_pillar locks to proceed once this is resolved and the master has been started back up. A warning will be logged if this is the case, with instructions.
[CRITICAL] SSH pubkey (/root/.ssh/id_pillar.pub) for git_pillar remote 'main ssh://[email protected]/myorg/mypillar.git' could not be found, path may be incorrect. Note that it may be necessary to clear git_pillar locks to proceed once this is resolved and the master has been started back up. A warning will be logged if this is the case, with instructions.
[CRITICAL] Failed to load gitfs
[CRITICAL] Failed to load git_pillar
[CRITICAL] Master failed pre flight checks, exiting
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)Salt Version:
Salt: 3006.0
Python Version:
Python: 3.10.11 (main, Apr 14 2023, 05:57:16) [GCC 11.2.0]
Dependency Versions:
cffi: 1.15.1
cherrypy: unknown
dateutil: 2.8.1
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 3.1.2
libgit2: 1.6.3
looseversion: 1.0.2
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 1.0.2
msgpack-pure: Not Installed
mysql-python: Not Installed
packaging: 22.0
pycparser: 2.21
pycrypto: Not Installed
pycryptodome: 3.9.8
pygit2: 1.12.0
python-gnupg: 0.4.8
PyYAML: 5.4.1
PyZMQ: 23.2.0
relenv: 0.11.2
smmap: Not Installed
timelib: 0.2.4
Tornado: 4.5.3
ZMQ: 4.3.4
System Versions:
dist: debian 11 bullseye
locale: utf-8
machine: x86_64
release: 5.10.0-21-cloud-amd64
system: Linux
version: Debian GNU/Linux 11 bullseyeAdditional context
Running cat and ls on those files show they exist fine. The files have permission 0400/-r-------- and are owned by root:root.
defanator, chais0n and gregseb
Metadata
Metadata
Assignees
Labels
RegressionThe issue is a bug that breaks functionality known to work in previous releases.The issue is a bug that breaks functionality known to work in previous releases.Sulfur v3006.0release code name and versionrelease code name and versionbugbroken, incorrect, or confusing behaviorbroken, incorrect, or confusing behaviordependencyunderlying Salt dependency issueunderlying Salt dependency issue