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

[BUG]Failed to check remote refs: fatal: unable to access 'https://<redacted>@dot-portal.... #63489

Open
chayandev108 opened this issue Jan 16, 2023 · 1 comment
Labels
Bug broken, incorrect, or confusing behavior info-needed waiting for more info needs-triage

Comments

@chayandev108
Copy link

Description
We were using gitea(repo) , saltstack (CM) & everything was working fine but now as we are planning to migrate from gitea(repo) to gitlab(repo) our git.latest module is failing with new gitlab repo url . error showing is in comment "Failed to check remote refs: fatal: unable to access 'https://@dot-portal........"

Setup
init.sls file

git_hub_saltstack:
git.latest:
- name: https://
- target: /home/saltstack_gitlab
- branch: {{ salt'pillar.get' }}
- rev: {{ salt'pillar.get' }}
- force_checkout: true
- https_user: {{ salt'pillar.get' }} #specified in pillar files
- https_pass: {{ salt'pillar.get' }} ##specified in pillar files
- force_reset: true
- require:
- pkg: pkg_local

Please be as specific as possible and give set-up details.

  • [ yes ] on-prem machine
  • [ yes ] salt container running on proxmox VE (salt-ssh command is running on this container)

Steps to Reproduce the behavior
details Given in screenshots
module details in init sls state file
salt-ssh command syntax using
git latest module failing

Expected behavior
All modules should work fine and salt should able to pull data from gitlab repo

Versions Report
~ # salt --versions-report
Salt Version:
Salt: 3004

Dependency Versions:
cffi: 1.14.5
cherrypy: Not Installed
dateutil: 2.8.1
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 3.0.1
libgit2: 1.1.0
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 1.0.2
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: 2.20
pycrypto: 3.10.1
pycryptodome: 3.10.1
pygit2: 1.4.0
Python: 3.9.16 (main, Dec 10 2022, 13:47:19)
python-gnupg: 0.4.8
PyYAML: 5.4.1
PyZMQ: 21.0.2
smmap: Not Installed
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.4

System Versions:
dist: alpine 3.14.8
locale: utf-8
machine: x86_64
release: 5.13.19-6-pve
system: Linux
version: Alpine Linux 3.14.8
Additional context
Add any other context about the problem here.

@chayandev108 chayandev108 added Bug broken, incorrect, or confusing behavior needs-triage labels Jan 16, 2023
@OrangeDog
Copy link
Contributor

OrangeDog commented Jan 16, 2023

(use code blocks to avoid formatting issues above)

Does the minion log say anything?
Can you connect to this repo with CLI git from the minion?
Perhaps you need to configure a proxy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior info-needed waiting for more info needs-triage
Projects
None yet
Development

No branches or pull requests

2 participants