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
Using salt.pkgrepo on Ubuntu 16.10 (and other *.10 versions, I would guess, by looking at the available Ubuntu repositories), the saltstack-pkgrepo state fails because the package repository URL that is created does not exist. This is because the repository URL is created using grains['os'] and grains['osrelease'], for which a repository does not actually exist.
I was able to work around this by specifying the repository for Ubuntu 16.04 in the pillars. I don't know if there is a good way to work around this in general, because it might be preferable to fail than to use an unexpectedly older version, but a note in the documentation would be nice.
Here is my workaround snippet.
# pillars/salt.slssalt:
# ...{% if grains['os'] == 'Ubuntu' and grains['osrelease'] == '16.10' %}key_url: 'http://repo.saltstack.com/apt/ubuntu/16.04/amd64/latest/SALTSTACK-GPG-KEY.pub'pkgrepo: 'deb http://repo.saltstack.com/apt/ubuntu/16.04/amd64/latest xenial main'{% endif %}
The text was updated successfully, but these errors were encountered:
Using
salt.pkgrepo
on Ubuntu 16.10 (and other*.10
versions, I would guess, by looking at the available Ubuntu repositories), thesaltstack-pkgrepo
state fails because the package repository URL that is created does not exist. This is because the repository URL is created usinggrains['os']
andgrains['osrelease']
, for which a repository does not actually exist.I was able to work around this by specifying the repository for Ubuntu 16.04 in the pillars. I don't know if there is a good way to work around this in general, because it might be preferable to fail than to use an unexpectedly older version, but a note in the documentation would be nice.
Here is my workaround snippet.
The text was updated successfully, but these errors were encountered: