Re: [Puppet Users] Facter incorrectly detecting Virtual status on Windows VM
Noticed that a matching issue was opened a few days ago, so I marked the one I opened as duplicate and just added a comment on the open issue instead. On Tuesday, October 15, 2013 9:11:42 AM UTC-6, Jason Harmon wrote: > > I created an issue. Never done one before so I may have balls it up a > bit. I added you as a watcher > > Wasn't sure how to even properly begin with a pull request. I've barely > used Git so the proper process of pulling and merging is out of my skill > set right now. > > > On Wednesday, October 9, 2013 2:51:09 PM UTC-6, Rob Reynolds wrote: >> >> Would you mind filing a pull request on this? If you already have please >> ignore. >> >> If you don't feel comfortable with that, please file an issue with the >> code you used to fix it and we will take a look at it. Thanks! >> >> >> On Tue, Oct 8, 2013 at 3:49 PM, Jason Harmon wrote: >> >>> Ran into a problem with Facter on a Windows 2008 R2 system running on a >>> proxmox server. >>> Facter reports the machine as being physical. >>> This is due to the WMI query used in the virtual.rb file is being return >>> "Bochs" as the Manufacturer and Model. >>> >>> Adding an additional "When" statement to the Ruby file (virtual.rb) >>> corrected the check coming back as physical. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to puppet-users...@googlegroups.com. >>> To post to this group, send email to puppet...@googlegroups.com. >>> Visit this group at http://groups.google.com/group/puppet-users. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> >> >> -- >> Rob Reynolds >> Developer, Puppet Labs >> >> Join us at PuppetConf 2014, September 23-24 in San Francisco >> > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Facter incorrectly detecting Virtual status on Windows VM
I created an issue. Never done one before so I may have balls it up a bit. I added you as a watcher Wasn't sure how to even properly begin with a pull request. I've barely used Git so the proper process of pulling and merging is out of my skill set right now. On Wednesday, October 9, 2013 2:51:09 PM UTC-6, Rob Reynolds wrote: > > Would you mind filing a pull request on this? If you already have please > ignore. > > If you don't feel comfortable with that, please file an issue with the > code you used to fix it and we will take a look at it. Thanks! > > > On Tue, Oct 8, 2013 at 3:49 PM, Jason Harmon > > wrote: > >> Ran into a problem with Facter on a Windows 2008 R2 system running on a >> proxmox server. >> Facter reports the machine as being physical. >> This is due to the WMI query used in the virtual.rb file is being return >> "Bochs" as the Manufacturer and Model. >> >> Adding an additional "When" statement to the Ruby file (virtual.rb) >> corrected the check coming back as physical. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users...@googlegroups.com . >> To post to this group, send email to puppet...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/puppet-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Rob Reynolds > Developer, Puppet Labs > > Join us at PuppetConf 2014, September 23-24 in San Francisco > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'
I had this come up a couple of weeks ago.
Basic of the problem was that the source file it was looking for didn't
exist.
In depth, the file it should have been grabbing did exist, but it wasn't
being evaluated correctly due to a missing rb file in facter. I was
evaluating the source as
puppet:///module/exmaple/file${operatingsystemmajversion}.ext and since
facter on the client did not have the method for getting the major version
it was returning nothing. It would try and get file.ext instead of
file7.ext
When it couldn't find the file it gave me an error about not being able to
create the temp file.
On Wednesday, October 9, 2013 9:16:20 AM UTC-6, alessandro mazzoli wrote:
>
> Hi,
> i'm a newbie about Puppet( 1 month ~)
> i got error on generate temp file, i'll explain my situation:
> -i have a puppetmaster(version: 3.3.0),executed on root
> and a puppet agent(version 2.7) provisioning by vagrant,executed on root
> -my site.pp, where webserv is a parametrized class, and typews is a
> parameter to choice nginx or lamp module,
> -i have my Enc node with path /var/lib/puppet/yaml/facts/ on my
> puppetmaster
> -Selinux disabled
>
> node 'vagrant1.localdomain'{
> include webserv
> class{ 'webserv':
> typews=>["nginx"],
> }
>
> }
>
>
> puppet agent -t --debug
> debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
> exist
> debug: Puppet::Type::User::ProviderPw: file pw does not exist
> debug: Puppet::Type::User::ProviderLdap: true value when expecting false
> debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl
> does not exist
> debug: Failed to load library 'selinux' for feature 'selinux'
> debug: Failed to load library 'ldap' for feature 'ldap'
> debug: /File[/var/lib/puppet/clientbucket]: Autorequiring
> File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
> File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
> Autorequiring File[/etc/puppet/ssl/private_keys]
> debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
> File[/var/lib/puppet/state]
> debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring
> File[/var/lib/puppet/state]
> debug: /File[/var/lib/puppet/client_yaml]: Autorequiring
> File[/var/lib/puppet]
> debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
> debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring
> File[/var/lib/puppet/state]
> debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
> File[/var/lib/puppet/state]
> debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
> Autorequiring File[/etc/puppet/ssl/public_keys]
> debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
> debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring
> File[/var/lib/puppet/state]
> debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
> File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppet/client_data]: Autorequiring
> File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]:
> Autorequiring File[/etc/puppet/ssl/certs]
> debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
> File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
> File[/etc/puppet/ssl/certs]
> debug: /File[/var/lib/puppet/classes.txt]: Autorequiring
> File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/run/puppet/agent.pid]: Autorequiring
> File[/var/run/puppet]
> debug: Finishing transaction -614883798
> debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
> Autorequiring File[/etc/puppet/ssl/private_keys]
> debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
> File[/etc/puppet/ssl/certs]
> debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]:
> Autorequiring File[/etc/puppet/ssl/certs]
> debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
> File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
> File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
> Autorequiring File[/etc/puppet/ssl/public_keys]
> debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/pup
[Puppet Users] Facter incorrectly detecting Virtual status on Windows VM
Ran into a problem with Facter on a Windows 2008 R2 system running on a proxmox server. Facter reports the machine as being physical. This is due to the WMI query used in the virtual.rb file is being return "Bochs" as the Manufacturer and Model. Adding an additional "When" statement to the Ruby file (virtual.rb) corrected the check coming back as physical. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers
I have the same type of setup with MSCS running in a virtual environment. The change to the windows.rb file fixed my facter problem as well. puppet agent --test now completes on the machines now. On Friday, 4 October 2013 06:13:23 UTC-6, Ethan Brown wrote: > > Christian - > > Thanks a bunch for taking the time out to verify this. While we believed > our fix was correct, I was trying to replicate your network configuration > internally to be absolutely certain. I was having difficulty getting the > virtual machines configured properly with respect to the 'Microsoft > Failover Cluster Virtual Adapter', so it's fantastic to hear that you were > able to verify this directly in your environment. > > > > On Fri, Oct 4, 2013 at 6:00 AM, Christian Koep > > wrote: > >> Hi Rob, >> i just applied the changes to the windows.rb file. >> >> The catalog run finished as usual. Thank you ;-) >> >> >> >> On Thu, Oct 3, 2013 at 8:47 PM, Rob Reynolds >> >> > wrote: >> >>> This verifies for us that this is a gating issue. >>> >>> Would you feel comfortable helping us verify that we've fixed this issue >>> for you? >>> >>> >>> https://github.com/ferventcoder/facter/blob/874a5a96ac5fa778c50f1e93424850022b1756cf/lib/facter/util/ip/windows.rb#L46-L47 >>> >>> >>> >>> >>> On Thu, Oct 3, 2013 at 1:42 PM, Christian Koep >>> >>> > wrote: >>> Yes, thats all i got from *facter --trace --debug* On Thu, Oct 3, 2013 at 8:41 PM, Rob Reynolds > wrote: > Was this the entire log (minus anything you feel sensitive)? > > > On Thu, Oct 3, 2013 at 1:15 PM, cko >wrote: > >> https://gist.github.com/anonymous/6814400 >> >> >> On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote: >> >>> You should be able to run >>> >>> facter --trace --debug >>> >>> >>> On Wed, Oct 2, 2013 at 5:18 PM, cko wrote: >>> Hi Ethan, what's the exact command that i would have to use? On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote: > Christian - > > I'm doing the final verification of our fix, and was hoping that I > could get the output from Facter run by itself? > > > > On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds > wrote: > >> I would say with all of this in mind we move forward with a fix >> where we look to see that the network adapter itself is also >> enabled. This >> is laid out in the ticket that I noted earlier. >> >> >> On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel >> wrote: >> >>> Exchange DAG is essentially a cluster and the adapter in >>> question the dag ip. >>> >>> My guess is the logic for adapters should be modded for when >>> netconnectionid is not null. >>> >>> In general don't try to mess with hidden adapters on dags unless >>> you understand ramifications. >>> >>> -- >>> You received this message because you are subscribed to the >>> Google Groups "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from >>> it, send an email to puppet-users...@googlegroups.com. >>> To post to this group, send email to puppet...@googlegroups.com. >>> >>> Visit this group at http://groups.google.com/group/puppet-users. >>> For more options, visit https://groups.google.com/groups/opt_out >>> . >>> >> >> >> >> -- >> Rob Reynolds >> Developer, Puppet Labs >> >> Join us at PuppetConf 2014, September 23-24 in San Francisco >> -- >> You received this message because you are subscribed to the >> Google Groups "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, >> send an email to puppet-users...@googlegroups.com. >> To post to this group, send email to puppet...@googlegroups.com. >> >> Visit this group at http://groups.google.com/group/puppet-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > -- > Ethan Brown > et...@puppetlabs.com > Software Engineer > > *Join us at PuppetConf 2014, September 23-24 in San Francisco* > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com. To post to this group, send email to puppet...@googlegroups.com. Visit this group at http://groups.google
