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

[dev.icinga.com #12982] Red Hat Satellite / Puppet 3.x compatibility #142

Closed
icinga-migration opened this issue Oct 25, 2016 · 3 comments
Closed

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12982

Created by tontonitch on 2016-10-25 12:05:51 +00:00

Assignee: (none)
Status: Rejected (closed on 2016-11-10 10:01:16 +00:00)
Target Version: (none)
Last Update: 2016-11-10 10:01:16 +00:00 (in Redmine)


Hi,

Neither puppet 4 nor the future parser are supported in Red Hat Satellite.
Consequently, it would be great if the new puppet module for Icinga2 would still be compatible with Puppet 3 (>= 3.8.6 which is the current version used by Satellite).

https://docs.puppet.com/puppet/3.8/reference/experiments\_future.html

Best regards,
Yannick

@icinga-migration
Copy link
Author

Updated by bsheqa on 2016-11-08 09:47:06 +00:00

  • Status changed from New to Feedback

Hi Yannik,

what errors do you exactly have with Puppet 3.8.6?

@icinga-migration
Copy link
Author

Updated by tontonitch on 2016-11-08 11:49:00 +00:00

Hi Sheqa,
Currently I don't have any issue with the module when used with RH Satellite 6.2 (using puppet 3.8.6).
But I had some issues with other modules rewritten using "future parser".
Consequently, I wanted to inform you of that situation in case you planned to use the "future parser".
Best regards,
Yannick

@icinga-migration
Copy link
Author

Updated by bsheqa on 2016-11-10 10:01:16 +00:00

  • Status changed from Feedback to Rejected

Currently I don't have any issue with the module when used with RH Satellite 6.2 (using puppet 3.8.6).
Awesome!

But I had some issues with other modules rewritten using "future parser".
Consequently, I wanted to inform you of that situation in case you planned to use the "future parser".
Our intention is to be comaptible to Puppet => 3.8.6
If you encounter any misbehaviour, please open an issue :-)

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

No branches or pull requests

1 participant