Jira (PUP-3934) Environment used before set in Resource.initialize (regression?)
Title: Message Title Henrik Lindberg commented on PUP-3934 Re: Environment used before set in Resource.initialize (regression?) I am fine with the change, it enables setting environment directly in a resource when it is created. When created via the catalog, it is clear that it should be looking things up in the catalog's environment even if the resource is not added to the catalog. I think it is prudent to also have a review of this by the client team - ping Kylo Ginsberg since Resource logic and environment is also used on the client. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3934) Environment used before set in Resource.initialize (regression?)
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-3934
Environment used before set in Resource.initialize (regression?)
Change By:
Thomas Hallgren
I'mnotabletodoacleanrunofthepuppetspecswhenusingstableorthetagged3.7.4commit.IfIrevertbacktothecommitjustbeforethisone:[0be9c1a|https://github.com/puppetlabs/puppet/commit/0be9c1adaec3b0d3450f202b89f205cfb8d10090](fixforPUP-3755),theneverythingworksOK.There'snothingwrongwiththecommitbutitprovokestherealproblemwhichisthattheResourceinitializermethodcallson{{resource_type}}whichinturnneedsthe{{ environment current_environment }}atapointwheretheenvironmenthasnotbeenset.Thus,itfallsbacktothe_**root**_environmentratherthanusingtheenvironmentfromthecatalogthatcreateditandtheresourcetypeisnotfound.Ihavenogoodexplanationtowhythistestpassedeverywherebefore3.7.4wasreleased.I'mnotabletogetagreen3.7.4orstablebuildonanyofmymachines.Thespecthatfailsisthisone:{noformat}1)PurerubymanifestsshouldallowdefinesFailure/Error:catalog.resource(Bar[instance]).should_notbe_nilPuppet::Error:Couldnotparseforenvironment*root*:Nofile(s)foundforimportof'foo'atline2#./lib/puppet/parser/parser_support.rb:175:in`rescueinparse'#./lib/puppet/parser/parser_support.rb:166:in`parse'#./lib/puppet/node/environment.rb:545:in`perform_initial_import'#./lib/puppet/node/environment.rb:276:in`known_resource_types'#./lib/puppet/resource.rb:276:in`resource_type'#./lib/puppet/resource.rb:242:in`initialize'#./lib/puppet/resource/catalog.rb:305:in`new'#./lib/puppet/resource/catalog.rb:305:in`resource'#./spec/integration/parser/ruby_manifest_spec.rb:39:in`block(2levels)intop(required)'{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3936) Injected parameter results in omission of block parameter
Title: Message Title
Thomas Hallgren created an issue
Puppet / PUP-3936
Injected parameter results in omission of block parameter
Issue Type:
Bug
Assignee:
Unassigned
Components:
Language
Created:
2015/02/01 9:16 AM
Priority:
Normal
Reporter:
Thomas Hallgren
An InternalFunction declared with the following dispatch:
Puppet::Functions.create_function('test', Puppet::Functions::InternalFunction) do
dispatch :test do
scope_param
Jira (PUP-3936) Injected parameter results in omission of block parameter
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-3936 Injected parameter results in omission of block parameter Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3655) Error: /File[/var/lib/puppet/facts.d]: Could not evaluate when no facts.d folder on any module
Title: Message Title otheus commented on PUP-3655 Re: Error: /File[/var/lib/puppet/facts.d]: Could not evaluate when no facts.d folder on any module BTW: the API docs do not mention that :mount may be pluginfacts Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3936) Injected parameter results in omission of block parameter
Title: Message Title Henrik Lindberg commented on PUP-3936 Re: Injected parameter results in omission of block parameter merged at: d26b925 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3655) Error: /File[/var/lib/puppet/facts.d]: Could not evaluate when no facts.d folder on any module
Title: Message Title otheus updated an issue Puppet / PUP-3655 Error: /File[/var/lib/puppet/facts.d]: Could not evaluate when no facts.d folder on any module Change By: otheus Comment: Looksverysimilarto... Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-777) Remove 'versionRequirement' per code comment
Title: Message Title Kylo Ginsberg commented on PUP-777 Re: Remove 'versionRequirement' per code comment Anderson Mills +1. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3936) Injected parameter results in omission of block parameter
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3936 Injected parameter results in omission of block parameter Change By: Henrik Lindberg Fix Version/s: PUP3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-777) Remove 'versionRequirement' per code comment
Title: Message Title
Anderson Mills updated an issue
Puppet / PUP-777
Remove 'versionRequirement' per code comment
Change By:
Anderson Mills
in3.x,module.rbsaysthefollowing:{code}#NOTICE:Thefallbackto`versionRequirement`issomethingwe'dliketo#nothavetosupport,butwehaveareasonablenumberofreleasesthat#don'tuse`version_requirement`.Whenwecandeprecatethis,weshould.{code}Thisshouldbeslatedforwarningsin3.5andremovalin4.0. EDIT-Perdiscussionbelow,itwasdecidedtosimplyremovethisnever-officially-supported-functionalityandjustdocumentthechange.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-777) Remove 'versionRequirement' per code comment
Title: Message Title Anderson Mills updated an issue Puppet / PUP-777 Remove 'versionRequirement' per code comment Change By: Anderson Mills Summary: Startdeprecating Remove 'versionRequirement'percodecomment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3655) Error: /File[/var/lib/puppet/facts.d]: Could not evaluate when no facts.d folder on any module
Title: Message Title otheus updated an issue Puppet / PUP-3655 Error: /File[/var/lib/puppet/facts.d]: Could not evaluate when no facts.d folder on any module Change By: otheus Comment:
Jira (FACT-802) cannot use text-based external facts to represent empty fact-values.
Title: Message Title otheus created an issue Facter / FACT-802 cannot use text-based external facts to represent empty fact-values. Issue Type: Bug Affects Versions: FACT 2.3.0 Assignee: Eric Sorenson Components: QA Created: 2015/02/01 3:06 PM Priority: Normal Reporter: otheus Original Estimate: 2 hours Remaining Estimate: 2 hours Text-based external facts can be created by adding a file to a module's facts.d/ directory. Indeed, thanks to another bug, at least one fact must exist (or an error is generated). It becomes sensible to create a null fact. However, the text-based parser does not allow this.
Jira (PUP-3655) Error: /File[/var/lib/puppet/facts.d]: Could not evaluate when no facts.d folder on any module
Title: Message Title otheus commented on PUP-3655 Re: Error: /File[/var/lib/puppet/facts.d]: Could not evaluate when no facts.d folder on any module After further analysis: It's clear this is a meta- (protocol) issue, between client and server. I enabled Trace in the code to confirm that at least in our case, what happens is this: Some value is defined and the client-side attempts to determine the metadata (source, environment, etc) of that value. The metadata method acts as an accessor to the @metadata variable. If that variable is nil, it attempts to populate it through Puppet::FileServing::Metadata, which has the task of determining the possible sources of the given value. In the case in which we see the error, the indirector uses the indirectory/rest.rb module, rest being a buzzword for an HTTP-based API. The find() method for rest forms an HTTP request which will look like this: https://puppet.domain:8140/development_environment/file_metadata/pluginfacts?links=managesource_permissions=us The server will (under certain circumstances) return 404. In our case, the 404 error will not trigger an exception, but instead return nil. The HTTP also returns the error message: Not Found: Could not find file_metadata plugin We have here one of three possibilities: The server should not respond with a 404 in this case. The client should pass up the 404 as an exception and let the higher-level caller deal sensibly with the unavailability of metadata. The client should suppress the 404 except, but instead of passing up nil, return metadata that indicates that there is non
Jira (PUP-777) Remove 'versionRequirement' per code comment
Title: Message Title Anderson Mills commented on PUP-777 Re: Remove 'versionRequirement' per code comment Lauren Rother - So, this looks like it needs to be an update to the Puppet 3.7 documentation for PMT as we will be removing this never officially supported dependency versionRequirement, and then as part of the release notes for Puppet 4.0 should be noted as removed. Kylo Ginsberg Eric Sorenson – I just want to get your buy in on this because it didn't happen prior to Puppet 3.7. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3254) Remove all Modulefile functionality in PMT except warnings about ignoring
Title: Message Title Anderson Mills commented on PUP-3254 Re: Remove all Modulefile functionality in PMT except warnings about ignoring Lauren Rother, I realized that the Modulefile isn't ignored. It's ignored as a container of metadata about the module, and is treated like any other text file in the root directory of the module. Do we still stick with the same wording? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-798) Error on Windows: cannot load such file -- util/sssd
Title: Message Title GeneBean commented on FACT-798 Re: Error on Windows: cannot load such file -- util/sssd Sorry for the delay responding... any tips on finding where this fact is coming from? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
