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]: Unable to use the collection to automatically pull the recent release, 0.27.4 #16

Closed
trfore opened this issue Oct 4, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@trfore
Copy link
Owner

trfore commented Oct 4, 2024

What happened?

The upstream pkg repo URLs no longer work as expected, due to inconsistencies between the github tag and the package version, for example the current release tag is v0.27.4 and the linux package names are 0.27.4-1.

step-cli_0.27.4-1_amd64.{deb,rpm}

The prior stable release, v0.27.2, works as expected.

Relevant code or playbook

tox -e py-ansible2.16-default

Relevant log output

TASK [trfore.smallstep.step_cli : Download step-cli Package] *******************
fatal: [py-ansible2.16-default]: FAILED! => {"changed": false, "msg": "Unable to find a checksum for file 'step-cli_0.27.4_amd64.deb' in '/~https://github.com/smallstep/cli/releases/download/v0.27.4/checksums.txt'"}

TASK [trfore.smallstep.step_cli : Remove step-cli Package] *********************
fatal: [py-ansible2.16-default]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'dest'. 'dict object' has no attribute 'dest'\n\nThe error appears to be in '/home/trf/.ansible/collections/ansible_collections/trfore/smallstep/roles/step_cli/tasks/main.yml': line 60, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n  always:\n    - name: Remove step-cli Package\n      ^ here\n"}

PLAY RECAP *********************************************************************
py-ansible2.16-default     : ok=8    changed=0    unreachable=0    failed=2    skipped=1    rescued=0    ignored=0

Ansible version

No response

Control node OS

Ubuntu 22.04

Target node OS

All

@trfore
Copy link
Owner Author

trfore commented Nov 4, 2024

Two upstream changes caused this:

  1. The CLI package version included a -1 in all builds past 0.27.2
  2. RPM package arch switched to using .86-64, while Deb packages keep the _amd64.

@trfore trfore closed this as completed Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant