Hey All,
I have an issue I need help working around or determining if it is a bug....
the issue is as follows, I have a custom repo(s) that has all my software
for a specific version release in it. A new version gets a new repo.
The problem lies when I move to upgrade software. My idea was to have a a
simple version variable in an external nodes script. When that changed the
repo would change... and all my software would be updated. The problem lies
that for some reason I need to puppet restarts to make this work??
example
class repos {
yumrepo { "custom_app":
descr => "custom_app",
baseurl =>
"http://reporserver/\$releasever/application-${::VERSION}/\$basearch";,
gpgkey => "http://reposerver/RPM-GPG-KEY-Interop";,
enabled => 1,
gpgcheck => 1
}
}
class packages {
include repos
package { "custom_app_rpm1":
ensure => latest,
require => Yumrepo["custom_app"],
}
package { "custom_app_rpm2":
ensure => latest,
require => Yumrepo["custom_app"],
}
}
This is just a snippet...
Issue:
1) I update my VERSION variable
2) the next puppet run and only updates the repo (no rpms are upgraded)
3) next puppet run updates the rpms.
There are no errors. but shouldn't my rpms update on the first run after
the variable change?
Any ideas?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/jS4yhakSc-AJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
