Skip to content

Ansible Galaxy Core 2.15.3 changed behavior of identifying installed collections #122

@0xFelix

Description

@0xFelix

With the version bump to 2.15.3 the behavior of ansible-galaxy identifying installed collections changed. [1]

This leads to ansible-galaxy picking up an already installed collection, when trying to install it into a different specified path. [2]

The ansible-galaxy install commands in [3, 4] likely need a --force switch to override that behavior?

[1] https://github.com/ansible/ansible/blob/v2.15.3/changelogs/CHANGELOG-v2.15.rst#id14
[2] https://github.com/kubevirt/kubevirt.core/actions/runs/5887415388/job/15966833282#step:8:283
[3]

- name: Install collection and dependencies (with --pre flag)

[4]
- name: Install collection and dependencies (without --pre flag)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions