-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
globbing in apt.pp fails with gluster release 3.10 and newer #140
Comments
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Oct 25, 2017
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Oct 25, 2017
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Oct 25, 2017
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Oct 25, 2017
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Oct 25, 2017
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Oct 25, 2017
Closed
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Oct 31, 2017
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Oct 31, 2017
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Oct 31, 2017
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Oct 31, 2017
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Mar 25, 2018
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Mar 25, 2018
bastelfreak
added a commit
to bastelfreak/puppet-gluster
that referenced
this issue
Mar 25, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
Core configures the repo for 3.12 but with the signing key for release 3.1
What behaviour did you expect instead
Core configures the repo for 3.12 with the signing key for release 3.12
Output log
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered: