Bug 861617
Summary: | puppet --parseonly broken (ruby 1.9.x issue) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Matthew Miller <mattdm> |
Component: | puppet | Assignee: | Jeroen van Meeuwen <vanmeeuwen+fedora> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | k.georgiou, tmz, vanmeeuwen+fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-20 13:28:00 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Matthew Miller
2012-09-29 14:21:07 UTC
I'm not sure I see a good way out of this. It's unfortunate that --parseonly was removed upstream and it's unfortunate that 1.9 made it into f17 leaving us with no choice but to update puppet to 2.7 before we wanted to do so. At this point in f17's life, I'm not sure that it's something that is worth the effort to fix. 3.1 is in f18+ and that should resolve the issue. Thoughts? Actually, I didn't look closely enough at this. Using --parseonly is unsupported in 2.7, so that's not something we will support in our packages. You should use puppet parser validate [<manifest>] [<manifest> ...] instead, as the 2.7 release notes suggest¹. The iconv warning is going to be fixed with a few backported patches from the 3.x branch upstream. That is already filed and tracked in bug #809911. I am closing this as a duplicate of that bug, as the only valid bug here is that warning. Sorry for the long delay. ¹ http://docs.puppetlabs.com/puppet/2.7/reference/release_notes.html#deprecations *** This bug has been marked as a duplicate of bug 809911 *** |