-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Failed to install snap package: snap \"shellcheck\" has no updates available #6821
Comments
Files identified in the description: If these files are incorrect, please update the |
+1 I also ran into this. Pinning to 7.0.1 fixes it.
|
@ltshb I jsut managed to reproduce your error, should be working in a fix in the next couple of days or so. |
@bgrande12 thanks for reporting. Could you please repeat the error using |
Hi @ltshb @bgrande12 Would you please confirm whether the PR above fixes your issues? I managed to reproduce @ltshb 's case and added that as a testcase in unit tests. @bgrande12 if it still does not work for you, please send that extra-verbose output and I can make a testcase out of it. ;-) |
@russoz I tried to use your PR to test but I couldn't, I'm not a profi with Ansible and might need guidance in order to test your PR. collections:
- name: git@github.com:ansible-collections/community.general.git
type: git
version: russoz-ansible:6821-snap-failure and re-run
|
hi @ltshb Almost that. Try: collections:
- name: https://github.com/russoz-ansible/community.general.git
type: git
version: 6821-snap-failure The working branches are on people's github accounts or projects (as in my case). |
Summary
After the upgrade of the community.general to version 7.1.0, the installation of a snap package that is already present failed. Reverting community.general to version 7.0.1 solved the issue.
Issue Type
Bug Report
Component Name
snap
Ansible Version
Community.general Version
Configuration
OS / Environment
Ubuntu 22.04
Steps to Reproduce
Expected Results
No error, the package is already installed and ansible task should be green
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: