[BUG]Failed to check remote refs: fatal: unable to access 'https://<redacted>@dot-portal....
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
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



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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provided init.sls configuration and the git.latest execution path in Salt 3004, then reproduce the failure using the stated salt-ssh, GitLab, and container setup. Done means identifying the cause of the remote-ref check failure and confirming that the state can pull the requested branch and revision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100