Jira (FACT-1676) Acceptance test tests/facts/el.rb fails on Amazon Linux
Title: Message Title John Duarte assigned an issue to Eric Delaney Facter / FACT-1676 Acceptance test tests/facts/el.rb fails on Amazon Linux Change By: John Duarte Assignee: John Duarte Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7744 Puppet CA's CRL is prone to duplicate entries Change By: Josh Cooper Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Josh Cooper commented on PUP-7744 Re: Puppet CA's CRL is prone to duplicate entries Sorry, yeah this is a different issue. The puppet node clean command calls puppet cert clean which will revoke already revoked certs: [root@ma9lddhbmxqglv2 ~]# puppet cert generate foobar Notice: Signed certificate request for ca Notice: foobar has a waiting certificate request Notice: Signed certificate request for foobar Notice: Removing file Puppet::SSL::CertificateRequest foobar at '/etc/puppetlabs/puppet/ssl/ca/requests/foobar.pem' Notice: Removing file Puppet::SSL::CertificateRequest foobar at '/etc/puppetlabs/puppet/ssl/certificate_requests/foobar.pem' [root@ma9lddhbmxqglv2 ~]# puppet cert clean foobar Notice: Revoked certificate with serial 2 Notice: Removing file Puppet::SSL::Certificate foobar at '/etc/puppetlabs/puppet/ssl/ca/signed/foobar.pem'
Jira (PDB-3606) puppetdb upgrade from 4.1.2 to any newer version timeout
Title: Message Title Rob Browning commented on PDB-3606 Re: puppetdb upgrade from 4.1.2 to any newer version timeout Ahh, I see. Did you happen to notice if PuppetDB and/or PostgreSQL were busy during the hour (say via atop, iostat, or similar)? Also, do you happen have any general sense of how much data's involved? Just pondering whether this is more likely just a slow migration, or something more difficult. In particular, if this really is stuck on the fact values migration, do you happen to know whether or not you might be storing a lot of data as fact values? (One gross/overall estimate might be the "du -sm" size of your PostgreSQL data directory). Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7277) Add Init[T] type to type system
Title: Message Title
Eric Delaney commented on PUP-7277
Re: Add Init[T] type to type system
Henrik Lindberg [Thomas Hallgren So I was testing with this, I installed the master bits and played around with notices using different converted values. Converting Strings to Integers and Floats etc. without much of a problem.
class foo {
$i = 100
$io = 050
notice(Init[Integer, 16]($i))
notice(Init[Integer, 8]($io))
notice(Init[Integer, 10]($i))
notice(Init[Integer, 10]($io))
notice(Init[Float]($i))
notice(Init[Float]($io))
notice(Init[String]($i))
Jira (PUP-7277) Add Init[T] type to type system
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-7277 Add Init[T] type to type system Change By: Eric Delaney Assignee: qa Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Erik Hansen commented on PUP-7744 Re: Puppet CA's CRL is prone to duplicate entries Josh Cooper Just a clarification, the duplicate entries can be produced without multiple writers though. It occurs simply by attempting to purge a certificate name that has already been revoked. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1676) Acceptance test tests/facts/el.rb fails on Amazon Linux
Title: Message Title John Duarte updated an issue Facter / FACT-1676 Acceptance test tests/facts/el.rb fails on Amazon Linux Change By: John Duarte QA Risk Assessment: Needs Assessment Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1676) Acceptance test tests/facts/el.rb fails on Amazon Linux
Title: Message Title John Duarte created an issue Facter / FACT-1676 Acceptance test tests/facts/el.rb fails on Amazon Linux Issue Type: Bug Affects Versions: FACT 3.6.5 Assignee: John Duarte Created: 2017/06/30 3:35 PM Environment: Amazon Linux 6 x86_64 Priority: Normal Reporter: John Duarte The tests/facts/el.rb acceptance test fails on Amazon Linux when the os.name fact returns Amazon rather than RedHat. This test needs to be updated to accommodate Amazon Linux. Add Comment
Jira (PUP-7746) Triage acceptance failures on Amazon Linux
Title: Message Title John Duarte created an issue Puppet / PUP-7746 Triage acceptance failures on Amazon Linux Issue Type: Task Affects Versions: PUP 4.10.4 Assignee: John Duarte Attachments: 20170630-puppet-amazon6ma-a-test-summary.log Created: 2017/06/30 3:25 PM Environment: Amazon Linux 6 x86_64 Priority: Normal Reporter: John Duarte Using the 4.10.x branch and puppet-agent build 4.99.0.363.g96b104a, the following acceptance tests fail on Amazon Linux. tests/resource/package/common_package_name_in_different_providers.rb
Jira (PDB-3606) puppetdb upgrade from 4.1.2 to any newer version timeout
Title: Message Title Mark Bentley commented on PDB-3606 Re: puppetdb upgrade from 4.1.2 to any newer version timeout Yeah, when I ran into this problem initially (a couple weeks ago), I tried bumping up the timeout from the default of 300 seconds, and let it run for an hour, but it didn't help. Still didn't finish, nor log anything interesting. I'm setting this setting found in the /etc/sysconfig/puppetdb to increase the timeout: START_TIMEOUT can be set here to alter the default startup timeout in seconds. This is used in System-V style init scripts only, and will have no effect in systemd. START_TIMEOUT=3600 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7741) puppet lookup fails with "--compile" option when using module puppet_agent
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7741
puppet lookup fails with "--compile" option when using module puppet_agent
Change By:
Josh Cooper
When using "puppet lookup" from the puppet master, when "--compile" is used (required with my configuration normally), if the puppet module "puppet_agent" is called, an error is raised and the lookup is stopped.Example : {noformat} puppet lookup --node vmlabdbm02.rsvgnw.local --compile --environment=lab global::ldapauthWarning: Undefined variable '::global::sector::sector'; class ::global::sector has not been evaluated (file & line not available)Warning: /etc/puppetlabs/code/environments/lab/hiera/team/IT.yaml: file does not contain a valid yaml hashWarning: /etc/puppetlabs/code/environments/lab/hiera/application/all.yaml: file does not contain a valid yaml hashWarning: /etc/puppetlabs/code/environments/lab/hiera/datacenter/all.yaml: file does not contain a valid yaml hashWarning: ModuleLoader: module 'puppet_agent' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules (file & line not available)Error: Could not run: Evaluation Error: Error while evaluating a Function Call, The puppet_agent class requires stringify_facts to be disabled at /etc/puppetlabs/code/environments/lab/modules/puppet_agent/manifests/params.pp:9:5 {noformat} If the "--compile" option is not given, the lookup is successful.However, nothing to report on the client side : the run of the agent on a node is successful, only the "puppet lookup --compile" on the server fails.The puppet_agent module has this code : {code:puppet} if $::puppet_stringify_facts {fail('The puppet_agent class requires stringify_facts to be disabled') } {code} {{ $::puppet_stringify_facts }} is false on the client, but not during a "lookup --compile" run on the master.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Josh Cooper commented on PUP-7744 Re: Puppet CA's CRL is prone to duplicate entries Thanks, Erik Hansen, yes this is caused because we do not write to the file atomically. So it is entirely likely for multiple writers to interleave, causing the kind of corruption described here and in PUP-2189. I'm going to close this as a dup of the earlier ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Josh Cooper commented on PUP-7738 Re: "bundle exec puppet module install" fails on Puppet 5.0.0 Hey David Hollinger, I'm reviewing the changes now, hope to get that merged today. But next Monday and Tues are US/company holidays, so it's going to be next week before we can get a fix published. To repro, create a Gemfile containing: source "https://rubygems.org" gem "puppet" gem "semantic_puppet" $ bundle install --path .bundle Fetching gem metadata from https://rubygems.org/.. Fetching version metadata from https://rubygems.org/. Resolving dependencies... Installing CFPropertyList 2.2.8 Installing
Jira (PUP-7745) package latest method does not refresh metadata on Solaris
Title: Message Title Shawn Ferry commented on PUP-7745 Re: package latest method does not refresh metadata on Solaris Pull request #6033 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title David Hollinger commented on PUP-7738 Re: "bundle exec puppet module install" fails on Puppet 5.0.0 Josh Cooper, Any idea when such a fix might be pushed into the external gem and release. Right now this issue is preventing users of the VP metadata-json-lint tool from using Puppet 5 as it breaks puppet module install with the external gem and the metadata-json-lint gem is broken without the external gem. We're looking into workarounds on our end, but it'd be preferential to not have to hack together some crazy logic depending on Puppet version. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5570) puppet module build parses .gitignore files unexpectedly
Title: Message Title Trevor Vaughan commented on PUP-5570 Re: puppet module build parses .gitignore files unexpectedly It turns out that, if you change the leading slash to a trailing slash, both PMT and Git appear to function correctly. So from /vendor to vendor/. That said, PMT really should be using git itself to figure out what is valid. This is the shell version ( git status - short| grep '^?' | cut -d\ -f2 && git ls-files ) | sort -u from https://stackoverflow.com/questions/39064520/list-all-files-that-are-not-ignored-by-gitignore and would be preferable to any internal parsing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3608) Move ntp dependency to spec_helper_acceptance
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3608 Move ntp dependency to spec_helper_acceptance Issue Type: Bug Assignee: Unassigned Created: 2017/06/30 11:38 AM Priority: Normal Reporter: gepetto-bot aac71812f6da18e402c8082d9627a37152943c75 added this dependency but it's only needed in the acceptance tests. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7599) Acceptance: Fix authorized keys acceptance tests
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-7599 Acceptance: Fix authorized keys acceptance tests Change By: Maggie Dreyer Assignee: qa Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7745) package latest method does not refresh metadata on Solaris
Title: Message Title
Shawn Ferry updated an issue
Puppet / PUP-7745
package latest method does not refresh metadata on Solaris
Change By:
Shawn Ferry
The current behavior from `latest` does not refresh package metadata. pkg list -a implies a periodic metadata refresh. {noformat} Note the current code says:# Return the version of the package. Note that the bug# http://defect.opensolaris.org/bz/show_bug.cgi?id=19159%# notes that we can't use -Ha for the same even though the manual page reads that way. {noformat} I can't find that bug to see what it was but -Ha is the way to do it. If -Hav is unacceptable vs -Hvn `pkg refresh` would be required prior to the list action.-a is preferred as it will not refresh every time
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7745) package latest method does not refresh metadata on Solaris
Title: Message Title Shawn Ferry created an issue Puppet / PUP-7745 package latest method does not refresh metadata on Solaris Issue Type: Bug Affects Versions: PUP 4.10.4 Assignee: Shawn Ferry Created: 2017/06/30 11:28 AM Priority: Normal Reporter: Shawn Ferry The current behavior from `latest` does not refresh package metadata. pkg list -a implies a periodic metadata refresh. Note the current code says: Return the version of the package. Note that the bug http://defect.opensolaris.org/bz/show_bug.cgi?id=19159% notes that we can't use -Ha for the same even though the manual page reads that way. I can't find that bug to see what it was but -Ha is the way to do it. If -Hav is unacceptable vs -Hvn `pkg refresh` would be required prior to the list action. -a is preferred as it will not refresh every time
Jira (PUP-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Erik Hansen updated an issue Puppet / PUP-7744 Puppet CA's CRL is prone to duplicate entries Change By: Erik Hansen Method Found: Needs Assessment Customer Feedback Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Erik Hansen created an issue Puppet / PUP-7744 Puppet CA's CRL is prone to duplicate entries Issue Type: Bug Assignee: Unassigned Created: 2017/06/30 9:50 AM Priority: Normal Reporter: Erik Hansen Using the 'puppet node purge' command it is possible to put duplicate revoked certificates in Puppet's CRL. For example: # puppet cert generate testcert Notice: testcert has a waiting certificate request Notice: Signed certificate request for testcert Now purge the node / certificate:
Jira (FACT-1630) Prepare a gem-only Facter 2.5.0 release
Title: Message Title John Duarte updated an issue Facter / FACT-1630 Prepare a gem-only Facter 2.5.0 release Change By: John Duarte QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3606) puppetdb upgrade from 4.1.2 to any newer version timeout
Title: Message Title Rob Browning commented on PDB-3606 Re: puppetdb upgrade from 4.1.2 to any newer version timeout Hmm, so I'm not sure yet, but I'm wondering if the module might just be too impatient. It looks like your server might just be working on a migration, which could take a while. If that's the case, then you should be able to work around the problem by either increasing the timeout in the module, or just starting PuppetDB manually once, and waiting for it to finish the migrations. You can tell that it has finished when it starts responding normally on its https endpoints, or by watching the log. And if it actually is just working on the migrations, I'd expect to see notable CPU and/or IO activity from PuppetDB and/or PostgreSQL during the process. Hope this helps. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7684) Puppet acceptance tests failures on Power 8 Ubuntu 16.04 and Rhel 7
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-7684 Puppet acceptance tests failures on Power 8 Ubuntu 16.04 and Rhel 7 Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3606) puppetdb upgrade from 4.1.2 to any newer version timeout
Title: Message Title Mark Bentley updated an issue PuppetDB / PDB-3606 puppetdb upgrade from 4.1.2 to any newer version timeout Change By: Mark Bentley Attachment: puppetdb-2017-06-29-trimmed.log.txt Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7738 "bundle exec puppet module install" fails on Puppet 5.0.0 Change By: Geoff Nichols Fix Version/s: PUP 5.0.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7738 "bundle exec puppet module install" fails on Puppet 5.0.0 Change By: Geoff Nichols Sprint: Agent 2017-07-12 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7738 "bundle exec puppet module install" fails on Puppet 5.0.0 Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7739) Need to regen man pages for 5.0.x
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7739 Need to regen man pages for 5.0.x Change By: Eric Delaney QA Risk Assessment Reason: We should review the man page changes QA Risk Assessment: Needs Assessment Manual QA Contact: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7662) SPIKE - investigate agent/master/puppetdb HTTP coms optimizations
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7662 SPIKE - investigate agent/master/puppetdb HTTP coms optimizations Change By: Eric Delaney QA Risk Assessment Reason: Its a spike ticket QA Risk Assessment: Needs Assessment No Action QA Contact: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3607) Mismatch in query and response keys: "parameters"
Title: Message Title Ranjit Viswakumar created an issue PuppetDB / PDB-3607 Mismatch in query and response keys: "parameters" Issue Type: Bug Assignee: Unassigned Created: 2017/06/30 7:38 AM Priority: Normal Reporter: Ranjit Viswakumar I'm doing a query like this: [root@puppet2017 ~]# cat /tmp/test1.pp $stuff_query = [ "from", "resources", [ "=", "exported", true ], ]
Jira (PDB-3606) puppetdb upgrade from 4.1.2 to any newer version timeout
Title: Message Title
Mark Bentley created an issue
PuppetDB / PDB-3606
puppetdb upgrade from 4.1.2 to any newer version timeout
Issue Type:
Bug
Affects Versions:
PDB 4.2.4
Assignee:
Unassigned
Components:
PuppetDB
Created:
2017/06/30 7:21 AM
Environment:
Puppet 4.3.2 (open source version) running on Amazon Linux Puppetserver and PuppetDB are running on the same node with 16GB of memory (m4.xlarge) Postgresql 9.4 RDS instance
Priority:
Normal
Reporter:
Mark Bentley
I'm trying to upgrade PuppetDB 4.1.2 to a newer version using the puppetlabs/puppetdb module. After puppet upgrades the packages for puppetdb and puppetdb-termini, puppetdb does not startup fully. It tries to start, and reports in the logs it's "Applying database migration version 47 - 51", but then starts to spin until the process finally times out and is killed.
The log messages I'm seeing look like this:
{{==> puppetdb.log <== 2017-06-29 23:39:49,877 INFO
Jira (PUP-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Markus Frosch commented on PUP-7738 Re: "bundle exec puppet module install" fails on Puppet 5.0.0 Thanks for dealing with that! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7115) Un-vendor semantic_puppet gem for Puppet 6
Title: Message Title Thomas Hallgren commented on PUP-7115 Re: Un-vendor semantic_puppet gem for Puppet 6 Markus Frosch, the problem you describe is being dealt with in PUP-7738. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7741) puppet lookup fails with "--compile" option when using module puppet_agent
Title: Message Title
Henrik Lindberg commented on PUP-7741
Re: puppet lookup fails with "--compile" option when using module puppet_agent
Hm, so then the puppet agent module needs to change since it assumes a version 3 agent - it happens to work for version 4 unless strict variables is turned on. What it really should do is check with
if $facts[stringify_facts] == true {
fail(...)
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-7741) puppet lookup fails with "--compile" option when using module puppet_agent
Title: Message Title Henrik Lindberg commented on PUP-7741 Re: puppet lookup fails with "--compile" option when using module puppet_agent Ping Josh Cooper - where should this ticket go? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7115) Un-vendor semantic_puppet gem for Puppet 6
Title: Message Title Markus Frosch commented on PUP-7115 Re: Un-vendor semantic_puppet gem for Puppet 6 Or at least update semantic_puppet on GitHub and release the Gem... Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7115) Un-vendor semantic_puppet gem for Puppet 6
Title: Message Title
Markus Frosch commented on PUP-7115
Re: Un-vendor semantic_puppet gem for Puppet 6
This causes interesting problems when developing Puppet modules, and using fixtures from the Forge, instead of direct GIT.
In any environment where the semantic_puppet gem is installed, and loaded before Puppet will do so:
{{$ puppet module install --ignore-dependencies --force "puppetlabs-stdlib" --trace --debug Debug: Runtime environment: puppet_version=5.0.0, ruby_version=2.4.1, run_mode=user, default_encoding=UTF-8 Notice: Preparing to install into /home/markus/.puppetlabs/etc/code/modules ... Notice: Downloading from https://forgeapi.puppet.com ... Error: wrong number of arguments (given 2, expected 1) /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/semantic_puppet-1.0.0/lib/semantic_puppet/version_range.rb:64:in `parse' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/lib/puppet/module_tool/applications/installer.rb:209:in `build_single_module_graph' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/lib/puppet/module_tool/applications/installer.rb:86:in `run' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/lib/puppet/module_tool/applications/application.rb:11:in `run' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/lib/puppet/face/module/install.rb:131:in `block (3 levels) in ' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/lib/puppet/interface/action.rb+eval[wrapper]:242:in `install' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/lib/puppet/application/face_base.rb:247:in `main' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/lib/puppet/application.rb:366:in `run_command' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/lib/puppet/application.rb:358:in `block in run' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/lib/puppet/util.rb:666:in `exit_on_fail' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/lib/puppet/application.rb:358:in `run' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/lib/puppet/util/command_line.rb:132:in `run' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/lib/puppet/util/command_line.rb:72:in `execute' /home/markus/.rvm/gems/ruby-2.4.1@puppet/gems/puppet-5.0.0/bin/puppet:5:in `' /home/markus/.rvm/gems/ruby-2.4.1@puppet/bin/puppet:23:in `load' /home/markus/.rvm/gems/ruby-2.4.1@puppet/bin/puppet:23:in `' /home/markus/.rvm/gems/ruby-2.4.1@puppet/bin/ruby_executable_hooks:15:in `eval' /home/markus/.rvm/gems/ruby-2.4.1@puppet/bin/ruby_executable_hooks:15:in `' Error: Try 'puppet help module install' for usage }}
Add Comment
Jira (PUP-7667) puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set
Title: Message Title Florian Klink commented on PUP-7667 Re: puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set I still think it's wrong ignoring a FQDN set in /etc/hostname. By looking at facters code for 'fqdn', it will only muble-jumble with /etc/resolv.conf, it the hostname is not already full-qualified: https://github.com/puppetlabs/facter/blob/d53ef63aab6d73f11e9f647aca59dee36ad479af/lib/src/facts/posix/networking_resolver.cc#L60 So IMHO, default_certname should simply also use facter's fqdn value. For hosts without a fqdn set in /etc/hostname, this shouldn't change things at all (as it will still combine /etc/resolv.conf as before, but this will then be done in facter). Of course, this would still be something for a major release, as it will change behaviour for hosts with a FQDN set in /etc/hostname if different from a domain set in /etc/resolv.conf, but it will still make things much more consistent. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7741) puppet lookup fails with "--compile" option when using module puppet_agent
Title: Message Title Yvan Broccard commented on PUP-7741 Re: puppet lookup fails with "--compile" option when using module puppet_agent Hello Henril, Thank you for your answer, but isn't "stringify facts" gone in Puppet v4 ? As my puppetmaster is running Puppet v4, I cannot configure this, as it doesn't exist anymore. puppet config print --section main | grep -i stringify puppet config print --section master | grep -i stringify puppet config print --section agent | grep -i stringify nothing returned here. Cheers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7741) puppet lookup fails with "--compile" option when using module puppet_agent
Title: Message Title Henrik Lindberg assigned an issue to Yvan Broccard Puppet / PUP-7741 puppet lookup fails with "--compile" option when using module puppet_agent Change By: Henrik Lindberg Assignee: Thomas Hallgren Yvan Broccard Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7741) puppet lookup fails with "--compile" option when using module puppet_agent
Title: Message Title Henrik Lindberg commented on PUP-7741 Re: puppet lookup fails with "--compile" option when using module puppet_agent Not sure I get what the problem is here other than you need to set stringify facts also on the master side. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Thomas Hallgren commented on PUP-7738 Re: "bundle exec puppet module install" fails on Puppet 5.0.0 Robert Heinzmann, I understand your concern and we are going to remove the bundled version. We did however decide to postpone that for Puppet 6 (see PUP-7115). The reason is partly because we want to retain a somewhat broken behavior that was present in 0.1.4 but has been corrected in 1.0.0. Incidentally, this is also what's causing the current problems with the extra argument. We didn't really anticipate that users were using the gem and that doing so actually overrides the vendored gem. Another reason for not removing it right now is that we're concerned that users might depend on the gem being vendored and thus be left with broken configurations if it's no longer present. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Thomas Hallgren assigned an issue to Josh Cooper Puppet / PUP-7738 "bundle exec puppet module install" fails on Puppet 5.0.0 Change By: Thomas Hallgren Assignee: Thomas Hallgren Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Robert Heinzmann commented on PUP-7738 Re: "bundle exec puppet module install" fails on Puppet 5.0.0 Sorry to interfere from the outside (more or less), but I still do not get (as more of a ops then a dev guy) why to bundle semantic_puppet gem within the puppet gem, while semantic_puppet has initially been created to avoid code duplicates. Shouldn't you just depend on if in gemspec and bundle it in Puppet AIO in a tested version ? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7738 "bundle exec puppet module install" fails on Puppet 5.0.0 Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Thomas Hallgren commented on PUP-7738 Re: "bundle exec puppet module install" fails on Puppet 5.0.0 Reopening this since we decided that the puppet module tool needs to check the arity of the VersionRange#parse method, or it will still fail when using other versions of the gem. Although this will fix almost all use-cases, there is still one that will remain. And that is if the semantic_puppet version 1.0.x is used. Its method has an arity of 1 and when called, it will always enforce strict semver semantics. We can only fix this partially by providing a 1.0.1 version of the gem where the patch is applied but the problem will still remain for the 1.0.0. version. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1675) virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm
Title: Message Title Sebastian Reitenbach commented on FACT-1675 Re: virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm I created a pull request to address the issue here: https://github.com/puppetlabs/facter/pull/1591 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1675) virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm
Title: Message Title
Sebastian Reitenbach updated an issue
Facter / FACT-1675
virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm
Change By:
Sebastian Reitenbach
For a OpenBSD vm running within OpenBSD's hypervisor vmm, the facts 'virtual' and 'is_virtual' are wrong.current status:{ { quote} # facter virtualphysical# facter is_virtual# false# facter dmi { bios => { vendor => "OpenBSD"}} {quote } }
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1675) virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm
Title: Message Title
Sebastian Reitenbach updated an issue
Facter / FACT-1675
virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm
Change By:
Sebastian Reitenbach
For a OpenBSD vm running within OpenBSD's hypervisor vmm, the facts 'virtual' and 'is_virtual' are wrong.current status:{ quote} { # facter virtualphysical# facter is_virtual# false# facter dmi { bios => { vendor => "OpenBSD"}} {quote } }
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1675) virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm
Title: Message Title
Sebastian Reitenbach updated an issue
Facter / FACT-1675
virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm
Change By:
Sebastian Reitenbach
For a OpenBSD vm running within OpenBSD's hypervisor vmm, the facts 'virtual' and 'is_virtual' are wrong.current status:{{ # facter virtualphysical# facter is_virtual# false# facter dmi { bios => { vendor => "OpenBSD"}} }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1675) virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm
Title: Message Title
Sebastian Reitenbach created an issue
Facter / FACT-1675
virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm
Issue Type:
Bug
Affects Versions:
FACT 3.7.0
Assignee:
Unassigned
Components:
Community
Created:
2017/06/30 12:07 AM
Environment:
OpenBSD VM running within OpenBSD's hypervisor vmm
Priority:
Normal
Reporter:
Sebastian Reitenbach
For a OpenBSD vm running within OpenBSD's hypervisor vmm, the facts 'virtual' and 'is_virtual' are wrong.
current status: {{# facter virtual physical
facter is_virtual
false
