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

Specifying version issues #92

Open
unsupo opened this issue Jun 13, 2018 · 4 comments
Open

Specifying version issues #92

unsupo opened this issue Jun 13, 2018 · 4 comments

Comments

@unsupo
Copy link
Contributor

unsupo commented Jun 13, 2018

When setting pillar data to a particular version it fails:
zabbix:
lookup:
agent:
version: 3.0.18

I had to change the version by specifying the package as shown below

zabbix:
lookup:
agent:
pkgs:
- 'zabbix-agent: 3.0.*'
version_repo: 3.0

Also, a pkg.installed.refresh=true should be used that way when an update takes place and a different version_repo is needed, it will update the rpms in the repo.

@unsupo
Copy link
Contributor Author

unsupo commented Jun 18, 2018

In repo.sls i had to do this:

refresh_repo:
cmd.run:
- name: yum clean dbcache #metadata, all
- onchanges_in:
- pkgrepo: {{ id_prefix }}_repo

@unsupo
Copy link
Contributor Author

unsupo commented Jun 18, 2018

#93 fixes one of the issues mentioned here.

@unsupo
Copy link
Contributor Author

unsupo commented Jun 18, 2018

The remaining issue is when upgrading version with a different repo, yum doesn't recognize the new repo installed and a yum clean all must be used

@Atem18
Copy link

Atem18 commented Aug 22, 2018

I confirm this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants