You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The role fails to install on Debian/Ubuntu when using ansible-core >=2.16 on the (Debian) Unhold GitLab Runner version task.
It will not fail if gitlab-runner is already installed previously.
It worked previously when I was at work, but not anymore when I'm at home. I traced it to this change in behavior of dpkg_selections ansible/ansible#81404 . dpkg_selections will from now on fail if the package isn't installed already.
The simple solution seems to be to place the Unhold task after the Install task.
But I'm not sure if that would create some unintended consequences. If it was previously set to hold, and then you install again, would it install the newly specified version or the one that was hold?
Otherwise I guess using ansible_facts or something to check if the package was installed before using dpkg_selections.
The text was updated successfully, but these errors were encountered:
The role fails to install on Debian/Ubuntu when using ansible-core >=2.16 on the
(Debian) Unhold GitLab Runner version
task.It will not fail if gitlab-runner is already installed previously.
It worked previously when I was at work, but not anymore when I'm at home. I traced it to this change in behavior of dpkg_selections ansible/ansible#81404 .
dpkg_selections
will from now on fail if the package isn't installed already.The simple solution seems to be to place the
Unhold
task after theInstall
task.But I'm not sure if that would create some unintended consequences. If it was previously set to hold, and then you install again, would it install the newly specified version or the one that was hold?
Otherwise I guess using ansible_facts or something to check if the package was installed before using
dpkg_selections
.The text was updated successfully, but these errors were encountered: