trunk does not manage cloned_interfaces parameter

the following configuration:
 bsd::network::interface::trunk { 'lagg10':
    interface => [ 'vtnet1', 'vtnet2' ],
    address   => [ '<IP_ADDRESS>/24' ],
  }

creates /etc/rc.conf entry:
ifconfig_lagg10="inet <IP_ADDRESS>/24 laggproto lacp laggport vtnet1 laggport vtnet2"
but doesn't set
cloned_interface=".. lagg10 .."
However, if I try to manage cloned_interface via puppet-bsd module:
 bsd::network::interface::cloned { 'lagg10':
    ensure => present,
  }

I get the following result:
Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Bsd::Network::Interface::Cloned[lagg10] is already declared at (file: /etc/puppetlabs/code/environments/production/modules/mymodule/manifests/init.pp, line: 8); cannot redeclare (file: /etc/puppetlabs/code/environments/production/modules/bsd/manifests/network/interface.pp, line: 123) (file: /etc/puppetlabs/code/environments/production/modules/bsd/manifests/network/interface.pp, line: 123, column: 7) (file: /etc/puppetlabs/code/environments/production/modules/bsd/manifests/network/interface/trunk.pp, line: 41) on node XXX
I suppose that * bsd::network::interface::trunk* should manage cloned_interfase as well

Quick and dirty solution via exec/grep and FreeBSD sysrc ;-)
diff -ruN network/interface/cloned.pp-o network/interface/cloned.pp
`
--- network/interface/cloned.pp-o       2019-07-17 19:11:23.439128961 +0300
+++ network/interface/cloned.pp 2019-07-17 20:39:37.431050872 +0300
@@ -2,6 +2,16 @@
$ensure,
) {

exec {"trunk_cloned_present":

 command     => "/usr/sbin/sysrc cloned_interfaces+=${name}",

 unless      => "/usr/sbin/sysrc -qn cloned_interface | /usr/bin/egrep -E \"${name}(\$|[ ])\"",

}

exec {"trunk_cloned_absent":

 command     => "/usr/sbin/sysrc cloned_interfaces-=${name}",

 onlyif      => "/usr/sbin/sysrc -qn cloned_interface | /usr/bin/egrep -E \"${name}(\$|[ ])\"",

}
case $facts['kernel'] {
'FreeBSD': {
case $ensure {
@@ -25,6 +35,7 @@
value        => $name,
array_append => true,
notify       => Bsd_interface[$name],

     notify       => Exec["trunk_cloned_${cloned_ensure}"],
   }
 }

`
but I can't look at it without tears ;)

Hmm, thanks for the report.  I can double check this, since I think I still have some trunk interfaces on FreeBSD machines to test with.  My laptop is in the shop, but maybe by this weekend or next I can take a look closer.

@olevole Are you in a position to try the branch trunktest of this module?  I've just changed some syntax a bit and things work over here on the one 12-RELEASE box that I tested it on.  Note that my default gateway did not come back after applying this change, so you might want to take that into consideration in your testing before doing so.  I also added a test that was broken, and now is passing, so maybe it works for you too.
Let me know how it goes.  I suspect that perhaps the vlan interface suffers from the same issue.

@xaque208 Zach, Thanks for the quick response.
I tested the following configuration with trunktest branch ( last commit 0e82ac4101a912e13c85b635aeda6a850abfc845 )
Still no cloned_interface settings:

root@og1:/usr/home/freebsd # diff -ruN /etc/rc.conf.orig /etc/rc.conf
--- /etc/rc.conf.orig   2019-07-31 03:18:50.008899000 +0300
+++ /etc/rc.conf        2019-07-31 03:35:21.764626000 +0300
@@ -7,3 +7,4 @@
 sshd_flags="-oUseDNS=no"
 cloudinitlocal_enable="YES"
 dumpdev="AUTO"
+ifconfig_lagg10="inet <IP_ADDRESS>/24 laggproto lacp laggport vtnet1 laggport vtnet2"

and as a result - the lagg10 interface is missing after a reboot

If i try to add bsd::network::interface::cloned:
cat /etc/puppetlabs/code/environments/production/modules/vstack_network/manifests/init.pp
class vstack_network
{
  bsd::network::interface::cloned { 'lagg10':
    ensure => present,
  }
  bsd::network::interface::trunk { 'lagg10':
    interface => [ 'vtnet1', 'vtnet2' ],
    address   => [ '<IP_ADDRESS>/24' ],
  }
}

I still get a conflict:

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Bsd::Network::Interface::Cloned[lagg10] is already declared at (file: /etc/puppetlabs/code/environments/production/modules/vstack_network/manifests/init.pp, line: 3); cannot redeclare (file: /etc/puppetlabs/code/environments/production/modules/bsd/manifests/network/interface.pp, line: 122) (file: /etc/puppetlabs/code/environments/production/modules/bsd/manifests/network/interface.pp, line: 122, column: 7) (file: /etc/puppetlabs/code/environments/production/modules/bsd/manifests/network/interface/trunk.pp, line: 41) on node og1.my.domain

Remove the bsd::network::interface::cloned resource and try again.  That resource should be created for you.

Oh i missed your first comment.  Which puppet version, and FreeBSD version?  What does facter -p cloned_interfaces give you?

client puppet agent: puppet6-6.6.0
client os: FreeBSD 12.0 and 13-CURRENT
puppet server ( if it matters ):  6.5.0 , CentOS
% facter -p cloned_interfaces
[
  "lagg",
  "vlan",
  "ipsec",
  "gif",
  "tun",
  "lo",
  "usbus",
  "wlan"
]

% cat /etc/rc.conf
cloudfinal_enable="YES"
ifconfig_vtnet0="<IP_ADDRESS> netmask <IP_ADDRESS>"
hostname="og1.my.domain"
cloudinit_enable="YES"
defaultrouter="<IP_ADDRESS>"
sshd_enable="YES"
sshd_flags="-oUseDNS=no"
cloudinitlocal_enable="YES"
dumpdev="AUTO"

ifconfig_lagg10="inet <IP_ADDRESS>/24 laggproto lacp laggport vtnet1 laggport vtnet2"

% ifconfig
vtnet0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=80028<VLAN_MTU,JUMBO_MTU,LINKSTATE>
        ether 00:a0:98:59:a6:8e
        inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
        media: Ethernet 10Gbase-T <full-duplex>
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
vtnet1: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=6c07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:a0:98:91:52:31
        media: Ethernet 10Gbase-T <full-duplex>
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
vtnet2: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=6c07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:a0:98:77:67:3f
        media: Ethernet 10Gbase-T <full-duplex>
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
        inet <IP_ADDRESS> netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

Do you by chance have any /etc/rc.conf.d/* files?  I'm confused because it works here, and the tests in the PR say the resource exists too.  Note that you get the resource conflict, so we know the resource is in the catalog.  Maybe are you missing augeas?  Can you confirm that you have all the dependencies listed here: https://github.com/xaque208/puppet-bsd/blob/master/metadata.json#L33

yes, I am sure. I checked on another FreeBSD 13 server without puppetserver: just
puppet module install zleslie-bsd --version 2.3.0
rm -rf /usr/local/etc/puppet/modules/bsd
git clone https://github.com/xaque208/puppet-bsd.git  /usr/local/etc/puppet/modules/bsd
gem install ipaddress

cat > lagg.pp <<EOF
bsd::network::interface::trunk { 'lagg10':
    interface => [ 'vlan10', 'vlan11' ],
    address   => [ '<IP_ADDRESS>/24' ],
}
EOF

puppet apply lagg.pp

and still no luck. /etc/rc.conf.d is empty. on which version of FreeBSD did you check? I will try to check it

I'm on 12-RELEASE.  May I have the debug output from that apply please?

Full step-by-step log on installed FreeBSD 12.0-RELEASE from scratch:
uname -a

FreeBSD freebsd1.my.domain 12.0-RELEASE-p9 FreeBSD 12.0-RELEASE-p9 GENERIC  amd64

pkg install -y puppet6

Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.

Creating group 'puppet' with gid '814'.
===> Creating users
Creating user 'puppet' with uid '814'.
[25/25] Extracting puppet6-6.6.0: 100%
Message from ruby-2.5.5_2,1:
====
Some of the standard commands are provided as separate ports for ease
of upgrading:
    devel/ruby-gems:        gem - RubyGems package manager
    devel/rubygem-rake:     rake - Ruby Make

And some of the standard libraries are provided as separate ports
since they require extra dependencies:
    databases/rubygem-dbm:  DBM module
    databases/rubygem-gdbm: GDBM module

Install them as occasion demands.
Message from boost-libs-1.70.0_2:
You have built the Boost library with thread support.
Don't forget to add -pthread to your linker options when
linking your code.
Message from puppet6-6.6.0:
To enable the puppet agent, add the following to /etc/rc.conf:
    puppet_enable="YES"

The default PID directory is /var/run/puppet

puppet module install zleslie-bsd --version 2.3.0

Notice: Preparing to install into /usr/local/etc/puppet/modules ...
Notice: Downloading from https://forgeapi.puppet.com ...
Notice: Installing -- do not interrupt ...
/usr/local/etc/puppet/modules
└─┬ zleslie-bsd (v2.3.0)
├── herculesteam-augeasproviders_core (v2.5.0)
├── herculesteam-augeasproviders_shellvar (v4.0.0)
├── herculesteam-augeasproviders_sysctl (v2.3.1)
├─┬ puppetlabs-concat (v6.1.0)
│ ├── puppetlabs-stdlib (v6.0.0)
│ └── puppetlabs-translate (v2.0.0)
└── thrnio-ip (v1.0.1)

rm -rf /usr/local/etc/puppet/modules/bsd
/usr/local/bin/git clone https://github.com/xaque208/puppet-bsd.git  /usr/local/etc/puppet/modules/bsd

Cloning into '/usr/local/etc/puppet/modules/bsd'...
remote: Enumerating objects: 137, done.
remote: Counting objects: 100% (137/137), done.
remote: Compressing objects: 100% (111/111), done.
remote: Total 2119 (delta 46), reused 61 (delta 20), pack-reused 1982
Receiving objects: 100% (2119/2119), 353.77 KiB | 700.00 KiB/s, done.
Resolving deltas: 100% (1032/1032), done.

gem install ipaddress

Fetching ipaddress-0.8.3.gem
Successfully installed ipaddress-0.8.3
Parsing documentation for ipaddress-0.8.3
Installing ri documentation for ipaddress-0.8.3
Done installing documentation for ipaddress after 0 seconds
1 gem installed

cat > lagg.pp <<EOF
 bsd::network::interface::trunk { 'lagg10':
     interface => [ 'vlan10', 'vlan11' ],
     address   => [ '<IP_ADDRESS>/24' ],
 }
EOF

puppet apply lagg.pp --log_level=debug

Debug: Caching environment 'production' (ttl = 0 sec)
Debug: Evicting cache entry for environment 'production'
Debug: Deleted text domain :production: false
Debug: Caching environment 'production' (ttl = 0 sec)
Debug: Caching environment 'production' (ttl = 0 sec)
Debug: Applying settings catalog for sections main, agent, ssl
Debug: Could not find library 'selinux' required to enable feature 'selinux'
Debug: Using settings: adding file resource 'confdir': 'File[/usr/local/etc/puppet]{:path=>"/usr/local/etc/puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Facter: searching for custom fact "operatingsystem".
Debug: Facter: searching for operatingsystem.rb in /usr/local/etc/puppet/modules/bsd/lib/facter.
Debug: Facter: searching for operatingsystem.rb in /usr/local/etc/puppet/modules/stdlib/lib/facter.
Debug: Facter: searching for operatingsystem.rb in /var/puppet/lib/facter.
Debug: Facter: searching for operatingsystem.rb in /var/puppet/facts.
Debug: Facter: fact "facterversion" has resolved to "3.14.1".
Debug: Facter: skipping external facts for "/opt/puppetlabs/facter/facts.d": No such file or directory
Debug: Facter: skipping external facts for "/etc/facter/facts.d": No such file or directory
Debug: Facter: skipping external facts for "/etc/puppetlabs/facter/facts.d": No such file or directory
Debug: Facter: skipping external facts for "/usr/local/etc/facter/facts.d": No such file or directory
Debug: Facter: skipping external facts for "/usr/local/etc/puppetlabs/facter/facts.d": No such file or directory
Debug: Facter: no external facts were found.
Debug: Facter: resolving operating system facts.
Debug: Facter: resolving kernel facts.
Debug: Facter: fact "kernel" has resolved to "FreeBSD".
Debug: Facter: fact "kernelrelease" has resolved to "12.0-RELEASE-p9".
Debug: Facter: fact "kernelmajversion" has resolved to "12".
Debug: Facter: fact "kernelversion" has resolved to "12.0".
Debug: Facter: executing command: /bin/freebsd-version
Debug: Facter: 12.0-RELEASE-p9
Debug: Facter: process exited with status code 0.
Debug: Facter: fact "osfamily" has resolved to "FreeBSD".
Debug: Facter: fact "operatingsystemmajrelease" has resolved to "12".
Debug: Facter: fact "operatingsystemrelease" has resolved to "12.0-RELEASE-p9".
Debug: Facter: fact "hardwaremodel" has resolved to "amd64".
Debug: Facter: fact "architecture" has resolved to "amd64".
Debug: Facter: fact "operatingsystem" has resolved to "FreeBSD".
Debug: Facter: fact "os" has resolved to {
architecture => "amd64",
family => "FreeBSD",
hardware => "amd64",
name => "FreeBSD",
release => {
full => "12.0-RELEASE-p9",
major => "12",
minor => "0-RELEASE-p9"
}
}.
Debug: Could not find library 'shadow' required to enable feature 'libshadow'
Debug: Could not find library 'cfpropertylist' required to enable feature 'cfpropertylist'
Debug: Could not find library 'ldap' required to enable feature 'ldap'
Debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
Debug: Puppet::Type::User::ProviderUseradd: file useradd does not exist
Debug: Puppet::Type::User::ProviderOpenbsd: file useradd does not exist
Debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/uuidgen does not exist
Debug: Puppet::Type::User::ProviderUser_role_add: file useradd does not exist
Debug: /User[puppet]: Provider pw does not support features libuser; not managing attribute forcelocal
Debug: Puppet::Type::Group::ProviderGroupadd: file groupadd does not exist
Debug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl does not exist
Debug: Puppet::Type::Group::ProviderLdap: feature ldap is missing
Debug: /Group[puppet]: Provider pw does not support features libuser; not managing attribute forcelocal
Debug: Using settings: adding file resource 'vardir': 'File[/var/puppet]{:path=>"/var/puppet", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'logdir': 'File[/var/log/puppet]{:path=>"/var/log/puppet", :mode=>"750", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'statedir': 'File[/var/puppet/state]{:path=>"/var/puppet/state", :mode=>"1755", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'rundir': 'File[/var/run/puppet]{:path=>"/var/run/puppet", :mode=>"755", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'libdir': 'File[/var/puppet/lib]{:path=>"/var/puppet/lib", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'preview_outputdir': 'File[/var/puppet/preview]{:path=>"/var/puppet/preview", :mode=>"750", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'certdir': 'File[/var/puppet/ssl/certs]{:path=>"/var/puppet/ssl/certs", :mode=>"755", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'ssldir': 'File[/var/puppet/ssl]{:path=>"/var/puppet/ssl", :mode=>"771", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'publickeydir': 'File[/var/puppet/ssl/public_keys]{:path=>"/var/puppet/ssl/public_keys", :mode=>"755", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'requestdir': 'File[/var/puppet/ssl/certificate_requests]{:path=>"/var/puppet/ssl/certificate_requests", :mode=>"755", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'privatekeydir': 'File[/var/puppet/ssl/private_keys]{:path=>"/var/puppet/ssl/private_keys", :mode=>"750", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'privatedir': 'File[/var/puppet/ssl/private]{:path=>"/var/puppet/ssl/private", :mode=>"750", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Facter: searching for custom fact "hostname".
Debug: Facter: searching for hostname.rb in /usr/local/etc/puppet/modules/bsd/lib/facter.
Debug: Facter: searching for hostname.rb in /usr/local/etc/puppet/modules/stdlib/lib/facter.
Debug: Facter: searching for hostname.rb in /var/puppet/lib/facter.
Debug: Facter: searching for hostname.rb in /var/puppet/facts.
Debug: Facter: resolving networking facts.
Debug: Facter: using the FQDN returned by gethostname: freebsd1.my.domain.
Debug: Facter: executing command: /sbin/route -n get default
Debug: Facter: route to: <IP_ADDRESS>
Debug: Facter: destination: <IP_ADDRESS>
Debug: Facter: mask: <IP_ADDRESS>
Debug: Facter: gateway: <IP_ADDRESS>
Debug: Facter: fib: 0
Debug: Facter: interface: vtnet0
Debug: Facter: completed processing output: closing child pipes.
Debug: Facter: process exited with status code 0.
Debug: Facter: got primary interface: "vtnet0"
Debug: Facter: searching "/var/lib/dhclient" for dhclient lease files.
Debug: Facter: searching "/var/lib/dhcp" for dhclient lease files.
Debug: Facter: searching "/var/lib/dhcp3" for dhclient lease files.
Debug: Facter: searching "/var/lib/NetworkManager" for dhclient lease files.
Debug: Facter: searching "/var/db" for dhclient lease files.
Debug: Facter: searching "/var/lib/NetworkManager" for NetworkManager internal lease files
Debug: Facter: executing command: dhcpcd -U lo0
Debug: Facter: dhcpcd was not found on the PATH.
Debug: Facter: executing command: dhcpcd -U vtnet0
Debug: Facter: dhcpcd was not found on the PATH.
Debug: Facter: fact "ipaddress_lo0" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "netmask_lo0" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "network_lo0" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "ipaddress6_lo0" has resolved to "::1".
Debug: Facter: fact "netmask6_lo0" has resolved to "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff".
Debug: Facter: fact "network6_lo0" has resolved to "::1".
Debug: Facter: fact "mtu_lo0" has resolved to 16384.
Debug: Facter: fact "ipaddress_vtnet0" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "ipaddress" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "netmask_vtnet0" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "netmask" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "network_vtnet0" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "network" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "macaddress_vtnet0" has resolved to "00:a0:98:32:4b:a8".
Debug: Facter: fact "macaddress" has resolved to "00:a0:98:32:4b:a8".
Debug: Facter: fact "mtu_vtnet0" has resolved to 1500.
Debug: Facter: fact "hostname" has resolved to "freebsd1".
Debug: Facter: fact "domain" has resolved to "my.domain".
Debug: Facter: fact "fqdn" has resolved to "freebsd1.my.domain".
Debug: Facter: fact "interfaces" has resolved to "lo0,vtnet0".
Debug: Facter: fact "networking" has resolved to {
domain => "my.domain",
fqdn => "freebsd1.my.domain",
hostname => "freebsd1",
interfaces => {
lo0 => {
bindings => [
{
address => "<IP_ADDRESS>",
netmask => "<IP_ADDRESS>",
network => "<IP_ADDRESS>"
}
],
bindings6 => [
{
address => "::1",
netmask => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
network => "::1"
},
{
address => "fe80::1",
netmask => "ffff:ffff:ffff:ffff::",
network => "fe80::"
}
],
ip => "<IP_ADDRESS>",
ip6 => "::1",
mtu => 16384,
netmask => "<IP_ADDRESS>",
netmask6 => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
network => "<IP_ADDRESS>",
network6 => "::1"
},
vtnet0 => {
bindings => [
{
address => "<IP_ADDRESS>",
netmask => "<IP_ADDRESS>",
network => "<IP_ADDRESS>"
}
],
ip => "<IP_ADDRESS>",
mac => "00:a0:98:32:4b:a8",
mtu => 1500,
netmask => "<IP_ADDRESS>",
network => "<IP_ADDRESS>"
}
},
ip => "<IP_ADDRESS>",
mac => "00:a0:98:32:4b:a8",
mtu => 1500,
netmask => "<IP_ADDRESS>",
network => "<IP_ADDRESS>",
primary => "vtnet0"
}.
Debug: Facter: searching for custom fact "domain".
Debug: Facter: searching for domain.rb in /usr/local/etc/puppet/modules/bsd/lib/facter.
Debug: Facter: searching for domain.rb in /usr/local/etc/puppet/modules/stdlib/lib/facter.
Debug: Facter: searching for domain.rb in /var/puppet/lib/facter.
Debug: Facter: searching for domain.rb in /var/puppet/facts.
Debug: Using settings: adding file resource 'clientyamldir': 'File[/var/puppet/client_yaml]{:path=>"/var/puppet/client_yaml", :mode=>"750", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'client_datadir': 'File[/var/puppet/client_data]{:path=>"/var/puppet/client_data", :mode=>"750", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'clientbucketdir': 'File[/var/puppet/clientbucket]{:path=>"/var/puppet/clientbucket", :mode=>"750", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'graphdir': 'File[/var/puppet/state/graphs]{:path=>"/var/puppet/state/graphs", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'pluginfactdest': 'File[/var/puppet/facts.d]{:path=>"/var/puppet/facts.d", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'localedest': 'File[/var/puppet/locales]{:path=>"/var/puppet/locales", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: /File[/var/puppet/state]: Adding autorequire relationship with File[/var/puppet]
Debug: /File[/var/puppet/lib]: Adding autorequire relationship with File[/var/puppet]
Debug: /File[/var/puppet/preview]: Adding autorequire relationship with File[/var/puppet]
Debug: /File[/var/puppet/ssl/certs]: Adding autorequire relationship with File[/var/puppet/ssl]
Debug: /File[/var/puppet/ssl]: Adding autorequire relationship with File[/var/puppet]
Debug: /File[/var/puppet/ssl/public_keys]: Adding autorequire relationship with File[/var/puppet/ssl]
Debug: /File[/var/puppet/ssl/certificate_requests]: Adding autorequire relationship with File[/var/puppet/ssl]
Debug: /File[/var/puppet/ssl/private_keys]: Adding autorequire relationship with File[/var/puppet/ssl]
Debug: /File[/var/puppet/ssl/private]: Adding autorequire relationship with File[/var/puppet/ssl]
Debug: /File[/var/puppet/client_yaml]: Adding autorequire relationship with File[/var/puppet]
Debug: /File[/var/puppet/client_data]: Adding autorequire relationship with File[/var/puppet]
Debug: /File[/var/puppet/clientbucket]: Adding autorequire relationship with File[/var/puppet]
Debug: /File[/var/puppet/state/graphs]: Adding autorequire relationship with File[/var/puppet/state]
Debug: /File[/var/puppet/facts.d]: Adding autorequire relationship with File[/var/puppet]
Debug: /File[/var/puppet/locales]: Adding autorequire relationship with File[/var/puppet]
Debug: /File[/var/log/puppet]/mode: mode changed '0755' to '0750'
Debug: /File[/var/puppet/state]/ensure: created
Debug: /File[/var/run/puppet]/owner: owner changed 'root' to 'puppet'
Debug: /File[/var/run/puppet]/group: group changed 'wheel' to 'puppet'
Debug: /File[/var/puppet/lib]/ensure: created
Debug: /File[/var/puppet/preview]/ensure: created
Debug: /File[/var/puppet/ssl]/ensure: created
Debug: /File[/var/puppet/ssl/certs]/ensure: created
Debug: /File[/var/puppet/ssl/public_keys]/ensure: created
Debug: /File[/var/puppet/ssl/certificate_requests]/ensure: created
Debug: /File[/var/puppet/ssl/private_keys]/ensure: created
Debug: /File[/var/puppet/ssl/private]/ensure: created
Debug: /File[/var/puppet/client_yaml]/ensure: created
Debug: /File[/var/puppet/client_data]/ensure: created
Debug: /File[/var/puppet/clientbucket]/ensure: created
Debug: /File[/var/puppet/state/graphs]/ensure: created
Debug: /File[/var/puppet/facts.d]/ensure: created
Debug: /File[/var/puppet/locales]/ensure: created
Debug: Finishing transaction<PHONE_NUMBER>0
Debug: Runtime environment: puppet_version=6.6.0, ruby_version=2.5.5, run_mode=user, default_encoding=US-ASCII
Debug: Loading external facts from /var/puppet/facts.d
Debug: Facter: loading external fact directories from config file
Info: Loading facts
Debug: Loading facts from /usr/local/etc/puppet/modules/bsd/lib/facter/cloned_interfaces.rb
Info: Loading facts
Debug: Loading facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
Debug: Loading facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/package_provider.rb
Debug: Loading facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/pe_version.rb
Debug: Loading facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/puppet_settings.rb
Debug: Loading facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/root_home.rb
Debug: Loading facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/service_provider.rb
Info: Loading facts
Debug: Loading facts from /usr/local/etc/puppet/modules/bsd/lib/facter/cloned_interfaces.rb
Info: Loading facts
Debug: Loading facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
Debug: Loading facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/package_provider.rb
Debug: Loading facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/pe_version.rb
Debug: Loading facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/puppet_settings.rb
Debug: Loading facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/root_home.rb
Debug: Loading facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/service_provider.rb
Debug: Facter: fact "facterversion" has resolved to "3.14.1".
Debug: Facter: skipping external facts for "/opt/puppetlabs/facter/facts.d": No such file or directory
Debug: Facter: skipping external facts for "/etc/facter/facts.d": No such file or directory
Debug: Facter: skipping external facts for "/etc/puppetlabs/facter/facts.d": No such file or directory
Debug: Facter: skipping external facts for "/usr/local/etc/facter/facts.d": No such file or directory
Debug: Facter: skipping external facts for "/usr/local/etc/puppetlabs/facter/facts.d": No such file or directory
Debug: Facter: searching "/var/puppet/facts.d" for external facts.
Debug: Facter: no external facts were found.
Debug: Facter: loading all custom facts.
Debug: Facter: loading custom fact directories from config file
Debug: Facter: searching for custom facts in /usr/local/etc/puppet/modules/bsd/lib/facter.
Info: Facter: loading custom facts from /usr/local/etc/puppet/modules/bsd/lib/facter/cloned_interfaces.rb.
Debug: Facter: searching for custom facts in /usr/local/etc/puppet/modules/stdlib/lib/facter.
Info: Facter: loading custom facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb.
Info: Facter: loading custom facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/package_provider.rb.
Debug: Reloading pip package provider
Debug: Reloading gem package provider
Info: Facter: loading custom facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/pe_version.rb.
Info: Facter: loading custom facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/puppet_settings.rb.
Info: Facter: loading custom facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/root_home.rb.
Info: Facter: loading custom facts from /usr/local/etc/puppet/modules/stdlib/lib/facter/service_provider.rb.
Debug: Facter: searching for custom fact "operatingsystem".
Debug: Facter: searching for operatingsystem.rb in /usr/local/etc/puppet/modules/bsd/lib/facter.
Debug: Facter: searching for operatingsystem.rb in /usr/local/etc/puppet/modules/stdlib/lib/facter.
Debug: Facter: searching for operatingsystem.rb in /usr/local/etc/puppet/modules/bsd/lib/facter.
Debug: Facter: searching for operatingsystem.rb in /usr/local/etc/puppet/modules/stdlib/lib/facter.
Debug: Facter: searching for operatingsystem.rb in /usr/local/etc/puppet/modules/bsd/lib/facter.
Debug: Facter: searching for operatingsystem.rb in /usr/local/etc/puppet/modules/stdlib/lib/facter.
Debug: Facter: resolving operating system facts.
Debug: Facter: resolving kernel facts.
Debug: Facter: fact "kernel" has resolved to "FreeBSD".
Debug: Facter: fact "kernelrelease" has resolved to "12.0-RELEASE-p9".
Debug: Facter: fact "kernelmajversion" has resolved to "12".
Debug: Facter: fact "kernelversion" has resolved to "12.0".
Debug: Facter: executing command: /bin/freebsd-version
Debug: Facter: 12.0-RELEASE-p9
Debug: Facter: process exited with status code 0.
Debug: Facter: fact "osfamily" has resolved to "FreeBSD".
Debug: Facter: fact "operatingsystemmajrelease" has resolved to "12".
Debug: Facter: fact "operatingsystemrelease" has resolved to "12.0-RELEASE-p9".
Debug: Facter: fact "hardwaremodel" has resolved to "amd64".
Debug: Facter: fact "architecture" has resolved to "amd64".
Debug: Facter: fact "operatingsystem" has resolved to "FreeBSD".
Debug: Facter: fact "os" has resolved to {
architecture => "amd64",
family => "FreeBSD",
hardware => "amd64",
name => "FreeBSD",
release => {
full => "12.0-RELEASE-p9",
major => "12",
minor => "0-RELEASE-p9"
}
}.
Debug: Facter: searching for custom fact "osfamily".
Debug: Facter: searching for osfamily.rb in /usr/local/etc/puppet/modules/bsd/lib/facter.
Debug: Facter: searching for osfamily.rb in /usr/local/etc/puppet/modules/stdlib/lib/facter.
Debug: Facter: searching for osfamily.rb in /usr/local/etc/puppet/modules/bsd/lib/facter.
Debug: Facter: searching for osfamily.rb in /usr/local/etc/puppet/modules/stdlib/lib/facter.
Debug: Facter: searching for osfamily.rb in /usr/local/etc/puppet/modules/bsd/lib/facter.
Debug: Facter: searching for osfamily.rb in /usr/local/etc/puppet/modules/stdlib/lib/facter.
Debug: Facter: searching for custom facts in /usr/local/etc/puppet/modules/bsd/lib/facter.
Debug: Facter: searching for custom facts in /usr/local/etc/puppet/modules/stdlib/lib/facter.
Debug: Facter: searching for custom facts in /usr/local/etc/puppet/modules/bsd/lib/facter.
Debug: Facter: searching for custom facts in /usr/local/etc/puppet/modules/stdlib/lib/facter.
Debug: Facter: fact "agent_specified_environment" resolved to null and will not be added.
Debug: Facter: executing command: /bin/sh -c /sbin/ifconfig -C
Debug: Facter: vlan ipsec gif tun lo usbus wlan
Debug: Facter: process exited with status code 0.
Debug: Facter: fact "cloned_interfaces" has resolved to [
"vlan",
"ipsec",
"gif",
"tun",
"lo",
"usbus",
"wlan"
].
Debug: Facter: fact "puppetversion" has resolved to "6.6.0".
Debug: Facter: fact "pe_version" resolved to null and will not be added.
Debug: Facter: fact "is_pe" has resolved to false.
Debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_info does not exist
Debug: Puppet::Type::Package::ProviderFreebsd: file /usr/sbin/pkg_info does not exist
Debug: Puppet::Type::Package::ProviderPorts: file /usr/local/sbin/portupgrade does not exist
Debug: Puppet::Type::Package::ProviderRpm: file rpm does not exist
Debug: Puppet::Type::Package::ProviderAptrpm: file apt-get does not exist
Debug: Puppet::Type::Package::ProviderDpkg: file /usr/bin/dpkg does not exist
Debug: Puppet::Type::Package::ProviderApt: file /usr/bin/apt-get does not exist
Debug: Puppet::Type::Package::ProviderAptitude: file /usr/bin/aptitude does not exist
Debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge does not exist
Debug: Puppet::Type::Package::ProviderYum: file yum does not exist
Debug: Puppet::Type::Package::ProviderDnf: file dnf does not exist
Debug: Puppet::Type::Package::ProviderTdnf: file tdnf does not exist
Debug: Puppet::Type::Package::ProviderOpkg: file opkg does not exist
Debug: Puppet::Type::Package::ProviderAix: file /usr/bin/lslpp does not exist
Debug: Puppet::Type::Package::ProviderNim: file /usr/sbin/nimclient does not exist
Debug: Puppet::Type::Package::ProviderPkg: file /usr/bin/pkg does not exist
Debug: Puppet::Type::Package::ProviderFink: file /sw/bin/fink does not exist
Debug: Puppet::Type::Package::ProviderSun: file /usr/bin/pkginfo does not exist
Debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper does not exist
Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/local/sbin/portupgrade does not exist
Debug: Puppet::Type::Package::ProviderHpux: file /usr/sbin/swinstall does not exist
Debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist
Debug: Puppet::Type::Package::ProviderUp2date: file /usr/sbin/up2date-nox does not exist
Debug: Puppet::Type::Package::ProviderPkgin: file pkgin does not exist
Debug: Puppet::Type::Package::ProviderUrpmi: file urpmi does not exist
Debug: Puppet::Type::Package::ProviderPacman: file /usr/bin/pacman does not exist
Debug: Puppet::Type::Package::ProviderRug: file /usr/bin/rug does not exist
Debug: /Package[dummy]: Provider pkgng does not support features virtual_packages; not managing attribute allow_virtual
Debug: /Package[dummy]: Provider pkgng does not support features targetable; not managing attribute command
Debug: Facter: fact "package_provider" has resolved to "pkgng".
Debug: Facter: fact "pe_major_version" resolved to null and will not be added.
Debug: Facter: fact "pe_minor_version" resolved to null and will not be added.
Debug: Facter: fact "pe_patch_version" resolved to null and will not be added.
Debug: Facter: fact "puppet_environmentpath" has resolved to "/usr/local/etc/puppet/environments".
Debug: Facter: fact "puppet_server" has resolved to "puppet".
Debug: Facter: fact "puppet_vardir" has resolved to "/var/puppet".
Debug: Facter: executing command: /bin/sh -c /usr/bin/getent passwd root
Debug: Facter: root:*:0:0:Charlie &:/root:/bin/csh
Debug: Facter: process exited with status code 0.
Debug: Facter: fact "root_home" has resolved to "/root".
Debug: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update does not exist
Debug: Puppet::Type::Service::ProviderDaemontools: file %%PREFIX%%/bin/svc does not exist
Debug: Puppet::Type::Service::ProviderOpenbsd: file /usr/sbin/rcctl does not exist
Debug: Puppet::Type::Service::ProviderRedhat: file /sbin/chkconfig does not exist
Debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist
Debug: Puppet::Type::Service::ProviderDebian: file /usr/sbin/update-rc.d does not exist
Debug: Puppet::Type::Service::ProviderUpstart: 0 confines (of 4) were true
Debug: Puppet::Type::Service::ProviderSystemd: file systemctl does not exist
Debug: Puppet::Type::Service::ProviderOpenrc: file /bin/rc-status does not exist
Debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not exist
Debug: /Service[dummy]: Provider freebsd does not support features configurable_timeout; not managing attribute timeout
Debug: Facter: fact "service_provider" has resolved to "freebsd".
Debug: Facter: resolving ruby facts.
Debug: Facter: fact "rubyplatform" has resolved to "amd64-freebsd12".
Debug: Facter: fact "rubysitedir" has resolved to "/usr/local/lib/ruby/site_ruby/2.5".
Debug: Facter: fact "rubyversion" has resolved to "2.5.5".
Debug: Facter: fact "ruby" has resolved to {
platform => "amd64-freebsd12",
sitedir => "/usr/local/lib/ruby/site_ruby/2.5",
version => "2.5.5"
}.
Debug: Facter: resolving path facts.
Debug: Facter: fact "path" has resolved to "/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin".
Debug: Facter: resolving EC2 facts.
Debug: Facter: resolving virtualization facts.
Debug: Facter: resolving desktop management interface facts.
Debug: Facter: kenv lookup for smbios.bios.vendor
Debug: Facter: kenv lookup for smbios.bios.version
Debug: Facter: kenv lookup for smbios.bios.reldate
Debug: Facter: kenv lookup for smbios.system.uuid
Debug: Facter: kenv lookup for smbios.system.serial
Debug: Facter: kenv lookup for smbios.system.product
Debug: Facter: kenv lookup for smbios.system.maker
Debug: Facter: fact "bios_vendor" has resolved to "BHYVE".
Debug: Facter: fact "bios_version" has resolved to "1.00".
Debug: Facter: fact "bios_release_date" has resolved to "03/14/2014".
Debug: Facter: fact "productname" has resolved to "BHYVE".
Debug: Facter: fact "serialnumber" has resolved to "None".
Debug: Facter: fact "uuid" has resolved to "bb31f21d-9988-7438-86fa-050ee1925466".
Debug: Facter: fact "manufacturer" has resolved to " ".
Debug: Facter: fact "dmi" has resolved to {
bios => {
release_date => "03/14/2014",
vendor => "BHYVE",
version => "1.00"
},
manufacturer => " ",
product => {
name => "BHYVE",
serial_number => "None",
uuid => "bb31f21d-9988-7438-86fa-050ee1925466"
}
}.
Debug: Facter: fact "is_virtual" has resolved to true.
Debug: Facter: fact "virtual" has resolved to "bhyve".
Debug: Facter: EC2 facts are unavailable: not running under an EC2 instance.
Debug: Facter: resolving GCE facts.
Debug: Facter: not running under a GCE instance.
Debug: Facter: resolving augeas facts.
Debug: Facter: executing command: /usr/local/bin/augparse --version
Debug: Facter: augparse 1.12.0 http://augeas.net/
Debug: Facter: completed processing output: closing child pipes.
Debug: Facter: process exited with status code 0.
Debug: Facter: fact "augeasversion" has resolved to "1.12.0".
Debug: Facter: fact "augeas" has resolved to {
version => "1.12.0"
}.
Debug: Facter: resolving networking facts.
Debug: Facter: using the FQDN returned by gethostname: freebsd1.my.domain.
Debug: Facter: executing command: /sbin/route -n get default
Debug: Facter: route to: <IP_ADDRESS>
Debug: Facter: destination: <IP_ADDRESS>
Debug: Facter: mask: <IP_ADDRESS>
Debug: Facter: gateway: <IP_ADDRESS>
Debug: Facter: fib: 0
Debug: Facter: interface: vtnet0
Debug: Facter: completed processing output: closing child pipes.
Debug: Facter: process exited with status code 0.
Debug: Facter: got primary interface: "vtnet0"
Debug: Facter: searching "/var/lib/dhclient" for dhclient lease files.
Debug: Facter: searching "/var/lib/dhcp" for dhclient lease files.
Debug: Facter: searching "/var/lib/dhcp3" for dhclient lease files.
Debug: Facter: searching "/var/lib/NetworkManager" for dhclient lease files.
Debug: Facter: searching "/var/db" for dhclient lease files.
Debug: Facter: searching "/var/lib/NetworkManager" for NetworkManager internal lease files
Debug: Facter: executing command: dhcpcd -U lo0
Debug: Facter: dhcpcd was not found on the PATH.
Debug: Facter: executing command: dhcpcd -U vtnet0
Debug: Facter: dhcpcd was not found on the PATH.
Debug: Facter: fact "ipaddress_lo0" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "netmask_lo0" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "network_lo0" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "ipaddress6_lo0" has resolved to "::1".
Debug: Facter: fact "netmask6_lo0" has resolved to "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff".
Debug: Facter: fact "network6_lo0" has resolved to "::1".
Debug: Facter: fact "mtu_lo0" has resolved to 16384.
Debug: Facter: fact "ipaddress_vtnet0" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "ipaddress" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "netmask_vtnet0" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "netmask" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "network_vtnet0" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "network" has resolved to "<IP_ADDRESS>".
Debug: Facter: fact "macaddress_vtnet0" has resolved to "00:a0:98:32:4b:a8".
Debug: Facter: fact "macaddress" has resolved to "00:a0:98:32:4b:a8".
Debug: Facter: fact "mtu_vtnet0" has resolved to 1500.
Debug: Facter: fact "hostname" has resolved to "freebsd1".
Debug: Facter: fact "domain" has resolved to "my.domain".
Debug: Facter: fact "fqdn" has resolved to "freebsd1.my.domain".
Debug: Facter: fact "interfaces" has resolved to "lo0,vtnet0".
Debug: Facter: fact "networking" has resolved to {
domain => "my.domain",
fqdn => "freebsd1.my.domain",
hostname => "freebsd1",
interfaces => {
lo0 => {
bindings => [
{
address => "<IP_ADDRESS>",
netmask => "<IP_ADDRESS>",
network => "<IP_ADDRESS>"
}
],
bindings6 => [
{
address => "::1",
netmask => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
network => "::1"
},
{
address => "fe80::1",
netmask => "ffff:ffff:ffff:ffff::",
network => "fe80::"
}
],
ip => "<IP_ADDRESS>",
ip6 => "::1",
mtu => 16384,
netmask => "<IP_ADDRESS>",
netmask6 => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
network => "<IP_ADDRESS>",
network6 => "::1"
},
vtnet0 => {
bindings => [
{
address => "<IP_ADDRESS>",
netmask => "<IP_ADDRESS>",
network => "<IP_ADDRESS>"
}
],
ip => "<IP_ADDRESS>",
mac => "00:a0:98:32:4b:a8",
mtu => 1500,
netmask => "<IP_ADDRESS>",
network => "<IP_ADDRESS>"
}
},
ip => "<IP_ADDRESS>",
mac => "00:a0:98:32:4b:a8",
mtu => 1500,
netmask => "<IP_ADDRESS>",
network => "<IP_ADDRESS>",
primary => "vtnet0"
}.
Debug: Facter: resolving uptime facts.
Debug: Facter: fact "uptime_seconds" has resolved to 625.
Debug: Facter: fact "uptime_hours" has resolved to 0.
Debug: Facter: fact "uptime_days" has resolved to 0.
Debug: Facter: fact "uptime" has resolved to "0:10 hours".
Debug: Facter: fact "system_uptime" has resolved to {
days => 0,
hours => 0,
seconds => 625,
uptime => "0:10 hours"
}.
Debug: Facter: resolving file system facts.
Debug: Facter: Skipping config label because it has a null value
Debug: Facter: Skipping config label because it has a null value
Debug: Facter: fact "mountpoints" has resolved to {
/ => {
available => "16.98 GiB",
available_bytes =><PHONE_NUMBER>6,
capacity => "11.18%",
device => "/dev/vtbd0p2",
filesystem => "ufs",
options => [
"local",
"root"
],
size => "19.12 GiB",
size_bytes =><PHONE_NUMBER>2,
used => "2.14 GiB",
used_bytes =><PHONE_NUMBER>
},
/dev => {
available => "0 bytes",
available_bytes => 0,
capacity => "100%",
device => "devfs",
filesystem => "devfs",
options => [
"local"
],
size => "1.00 KiB",
size_bytes => 1024,
used => "1.00 KiB",
used_bytes => 1024
}
}.
Debug: Facter: fact "filesystems" has resolved to "devfs,ufs".
Debug: Facter: fact "partitions" has resolved to {
vtbd0p1 => {
partuuid => "76f6a453-be85-11e9-bf62-00a098286ee2",
size => "260.00 MiB",
size_bytes => 272629760
},
vtbd0p2 => {
partuuid => "76ff9988-be85-11e9-bf62-00a098286ee2",
size => "19.75 GiB",
size_bytes =><PHONE_NUMBER>2
}
}.
Debug: Facter: resolving ssh facts.
Debug: Facter: fact "sshdsakey" has resolved to "AAAAB3NzaC1kc3MAAACBAPWNQYbMBNFunF//lLWayoL11okn4L+LghlnQ+PUHTdpWgPZw6jYyzTWedNo+LOSZveTnWDPNXnsbmZ7oW3HtOdZiaPDSxupEllyQLT6S5pKaFil9RlfDHn/65OlehKsRlpGFt86bfaxmMRYgVrnZ1qP/tVUGViThIdt5sY+9UafAAAAFQCsjQh+MmzuVTpOyfXEPRN/5iTjQQAAAIAhCF+q4hwxYH/KLzKiSnh31hspksRbCBaM0Wa8zWh2UaLXzKWpA6c5Tt1r1nq1+lBlo7YKcCHE1iSq0awlXNVUWzFAdRSxz1VDhtm4hX4TLlJQl7rZAnzWvWp11PfO0pQLGo/849vP2//pZ69DQqfBSJPwKR6j/fJW1uqEkE0+FAAAAIEA4mwZ9gKOPgeI0nijovYWz8h0zJ3tgMi6bXh6DxMdtkPilTGiLOjVigFpvJgH2n/n66oOid6qnxgn49XH4gzrPHgUCS3jpxagr4LIUavIG3J+2A5AtQRn41z68xXObDFsuS0MNDIH7p6r/xZ+CtZvKhqsC2jqNSFycwg1IoasEmY=".
Debug: Facter: fact "sshfp_dsa" has resolved to "SSHFP 2 1 2ed833e6a5f887c70a268bf215a8b55b4feb3ea1
SSHFP 2 2 fd7882db34ee3c01f24e6ec949b9486135cd65d409aa4e5ec0d8cdb831925db6".
Debug: Facter: fact "sshrsakey" has resolved to "AAAAB3NzaC1yc2EAAAADAQABAAABAQDA0gTRC6ZrgWNoJfGvEwVlj2mF3GVotr4sTb8y0D2vF4CwBRygNwnRH/UjviaOmfwIm0qnJhHmy2apmTunxA9zq29GxOTAKyl+qCldr9z5uxo0Qca58xwk3Fc1W23WeIAzDBH3nmc/Fg18AKQ6jlDmn0JpccV4JT17tLm9RccnYwdfwpvBxAOtdpkoKD0xvd+4ZJYMOAPOWVmEBSDcyL2qMX7+tBzFcg800msKff7YnaxX3DnSqSu+3B5MyaAUec2jkZ9C9vAxhXYXPenYMxL43McJYlx3/y8XWNPpKXCKt2UbMtEBWIw71K+AoVW87BitIG1lu5yGYVLWRNUy/Yl3".
Debug: Facter: fact "sshfp_rsa" has resolved to "SSHFP 1 1 4b8337576be3f895e8f5bfb7870e38d9e550b073
SSHFP 1 2 d722d47b6a46589613f7f6182bf9d0665969639b1a77f1111ed2382e486bd491".
Debug: Facter: fact "sshecdsakey" has resolved to "AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBGxd/9jbbVVDbWW74OzDwWDPoWzQ4c3Pva2iHx3xRLEjCf9OmOtGTk5EXPfrO6APUjoxHPOoprLW5U2SdLWGkWk=".
Debug: Facter: fact "sshfp_ecdsa" has resolved to "SSHFP 3 1 00c727eac2471390ac5ef475c1e2082c3e1cb5b8
SSHFP 3 2 ed33a75094c34a3ae6bb0eca5d76838a117b3cfdf2a88087ff49ae516aabbb14".
Debug: Facter: fact "sshed25519key" has resolved to "AAAAC3NzaC1lZDI1NTE5AAAAIDX+xBxjKYVZ3cdZs6r3V98OhKPkKYqWvrkGhm9/oKmO".
Debug: Facter: fact "sshfp_ed25519" has resolved to "SSHFP 4 1 1a4e1cbc42e680dcd95bdd5620e025b82d2dd537
SSHFP 4 2 99b871605301083a3196eba410b1886a7623301fa4545b7874b095fe3f9d18fa".
Debug: Facter: fact "ssh" has resolved to {
dsa => {
fingerprints => {
sha1 => "SSHFP 2 1 2ed833e6a5f887c70a268bf215a8b55b4feb3ea1",
sha256 => "SSHFP 2 2 fd7882db34ee3c01f24e6ec949b9486135cd65d409aa4e5ec0d8cdb831925db6"
},
key => "AAAAB3NzaC1kc3MAAACBAPWNQYbMBNFunF//lLWayoL11okn4L+LghlnQ+PUHTdpWgPZw6jYyzTWedNo+LOSZveTnWDPNXnsbmZ7oW3HtOdZiaPDSxupEllyQLT6S5pKaFil9RlfDHn/65OlehKsRlpGFt86bfaxmMRYgVrnZ1qP/tVUGViThIdt5sY+9UafAAAAFQCsjQh+MmzuVTpOyfXEPRN/5iTjQQAAAIAhCF+q4hwxYH/KLzKiSnh31hspksRbCBaM0Wa8zWh2UaLXzKWpA6c5Tt1r1nq1+lBlo7YKcCHE1iSq0awlXNVUWzFAdRSxz1VDhtm4hX4TLlJQl7rZAnzWvWp11PfO0pQLGo/849vP2//pZ69DQqfBSJPwKR6j/fJW1uqEkE0+FAAAAIEA4mwZ9gKOPgeI0nijovYWz8h0zJ3tgMi6bXh6DxMdtkPilTGiLOjVigFpvJgH2n/n66oOid6qnxgn49XH4gzrPHgUCS3jpxagr4LIUavIG3J+2A5AtQRn41z68xXObDFsuS0MNDIH7p6r/xZ+CtZvKhqsC2jqNSFycwg1IoasEmY=",
type => "ssh-dss"
},
ecdsa => {
fingerprints => {
sha1 => "SSHFP 3 1 00c727eac2471390ac5ef475c1e2082c3e1cb5b8",
sha256 => "SSHFP 3 2 ed33a75094c34a3ae6bb0eca5d76838a117b3cfdf2a88087ff49ae516aabbb14"
},
key => "AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBGxd/9jbbVVDbWW74OzDwWDPoWzQ4c3Pva2iHx3xRLEjCf9OmOtGTk5EXPfrO6APUjoxHPOoprLW5U2SdLWGkWk=",
type => "ecdsa-sha2-nistp256"
},
ed25519 => {
fingerprints => {
sha1 => "SSHFP 4 1 1a4e1cbc42e680dcd95bdd5620e025b82d2dd537",
sha256 => "SSHFP 4 2 99b871605301083a3196eba410b1886a7623301fa4545b7874b095fe3f9d18fa"
},
key => "AAAAC3NzaC1lZDI1NTE5AAAAIDX+xBxjKYVZ3cdZs6r3V98OhKPkKYqWvrkGhm9/oKmO",
type => "ssh-ed25519"
},
rsa => {
fingerprints => {
sha1 => "SSHFP 1 1 4b8337576be3f895e8f5bfb7870e38d9e550b073",
sha256 => "SSHFP 1 2 d722d47b6a46589613f7f6182bf9d0665969639b1a77f1111ed2382e486bd491"
},
key => "AAAAB3NzaC1yc2EAAAADAQABAAABAQDA0gTRC6ZrgWNoJfGvEwVlj2mF3GVotr4sTb8y0D2vF4CwBRygNwnRH/UjviaOmfwIm0qnJhHmy2apmTunxA9zq29GxOTAKyl+qCldr9z5uxo0Qca58xwk3Fc1W23WeIAzDBH3nmc/Fg18AKQ6jlDmn0JpccV4JT17tLm9RccnYwdfwpvBxAOtdpkoKD0xvd+4ZJYMOAPOWVmEBSDcyL2qMX7+tBzFcg800msKff7YnaxX3DnSqSu+3B5MyaAUec2jkZ9C9vAxhXYXPenYMxL43McJYlx3/y8XWNPpKXCKt2UbMtEBWIw71K+AoVW87BitIG1lu5yGYVLWRNUy/Yl3",
type => "ssh-rsa"
}
}.
Debug: Facter: resolving id facts.
Debug: Facter: fact "id" has resolved to "root".
Debug: Facter: fact "gid" has resolved to "wheel".
Debug: Facter: fact "identity" has resolved to {
gid => 0,
group => "wheel",
privileged => true,
uid => 0,
user => "root"
}.
Debug: Facter: resolving timezone facts.
Debug: Facter: fact "timezone" has resolved to "UTC".
Debug: Facter: resolving load_average facts.
Debug: Facter: fact "load_averages" has resolved to {
15m => 0.418457,
1m => 0.822266,
5m => 0.696777
}.
Debug: Facter: resolving processor facts.
Debug: Facter: executing command: /usr/bin/uname -p
Debug: Facter: amd64
Debug: Facter: process exited with status code 0.
Debug: Facter: fact "hardwareisa" has resolved to "amd64".
Debug: Facter: fact "processorcount" has resolved to 1.
Debug: Facter: fact "processor0" has resolved to "Intel(R) Core(TM) i5-8600 CPU @ 3.10GHz".
Debug: Facter: fact "processors" has resolved to {
count => 1,
isa => "amd64",
models => [
"Intel(R) Core(TM) i5-8600 CPU @ 3.10GHz"
],
speed => "3.10 GHz"
}.
Debug: Facter: resolving ZFS facts.
Debug: Facter: executing command: /sbin/zfs upgrade
Debug: Facter: This system is currently running ZFS filesystem version 5.
Debug: Facter: completed processing output: closing child pipes.
Debug: Facter: process exited with status code 0.
Debug: Facter: executing command: /sbin/zfs upgrade -v
Debug: Facter: The following filesystem versions are supported:
Debug: Facter: VER  DESCRIPTION
Debug: Facter: ---  --------------------------------------------------------
Debug: Facter: 1   Initial ZFS filesystem version
Debug: Facter: 2   Enhanced directory entries
Debug: Facter: 3   Case insensitive and filesystem user identifier (FUID)
Debug: Facter: 4   userquota, groupquota properties
Debug: Facter: 5   System attributes
Debug: Facter: For more information on a particular version, including supported releases,
Debug: Facter: see the ZFS Administration Guide.
Debug: Facter: process exited with status code 0.
Debug: Facter: fact "zfs_version" has resolved to "5".
Debug: Facter: fact "zfs_featurenumbers" has resolved to "1,2,3,4,5".
Debug: Facter: resolving ZFS storage pool facts.
Debug: Facter: executing command: /sbin/zpool upgrade -v
Debug: Facter: This system supports ZFS pool feature flags.
Debug: Facter: The following features are supported:
Debug: Facter: FEAT DESCRIPTION
Debug: Facter: -------------------------------------------------------------
Debug: Facter: async_destroy                         (read-only compatible)
Debug: Facter: Destroy filesystems asynchronously.
Debug: Facter: empty_bpobj                           (read-only compatible)
Debug: Facter: Snapshots use less space.
Debug: Facter: lz4_compress
Debug: Facter: LZ4 compression algorithm support.
Debug: Facter: multi_vdev_crash_dump
Debug: Facter: Crash dumps to multiple vdev pools.
Debug: Facter: spacemap_histogram                    (read-only compatible)
Debug: Facter: Spacemaps maintain space histograms.
Debug: Facter: enabled_txg                           (read-only compatible)
Debug: Facter: Record txg at which a feature is enabled
Debug: Facter: hole_birth
Debug: Facter: Retain hole birth txg for more precise zfs send
Debug: Facter: extensible_dataset
Debug: Facter: Enhanced dataset functionality, used by other features.
Debug: Facter: embedded_data
Debug: Facter: Blocks which compress very well use even less space.
Debug: Facter: bookmarks                             (read-only compatible)
Debug: Facter: "zfs bookmark" command
Debug: Facter: filesystem_limits                     (read-only compatible)
Debug: Facter: Filesystem and snapshot limits.
Debug: Facter: large_blocks
Debug: Facter: Support for blocks larger than 128KB.
Debug: Facter: large_dnode
Debug: Facter: Variable on-disk size of dnodes.
Debug: Facter: sha512
Debug: Facter: SHA-512/256 hash algorithm.
Debug: Facter: skein
Debug: Facter: Skein hash algorithm.
Debug: Facter: device_removal
Debug: Facter: Top-level vdevs can be removed, reducing logical pool size.
Debug: Facter: obsolete_counts                       (read-only compatible)
Debug: Facter: Reduce memory used by removed devices when their blocks are freed or remapped.
Debug: Facter: zpool_checkpoint                      (read-only compatible)
Debug: Facter: Pool state can be checkpointed, allowing rewind later.
Debug: Facter: spacemap_v2                           (read-only compatible)
Debug: Facter: Space maps representing large segments are more efficient.
Debug: Facter: The following legacy versions are also supported:
Debug: Facter: VER  DESCRIPTION
Debug: Facter: ---  --------------------------------------------------------
Debug: Facter: 1   Initial ZFS version
Debug: Facter: 2   Ditto blocks (replicated metadata)
Debug: Facter: 3   Hot spares and double parity RAID-Z
Debug: Facter: 4   zpool history
Debug: Facter: 5   Compression using the gzip algorithm
Debug: Facter: 6   bootfs pool property
Debug: Facter: 7   Separate intent log devices
Debug: Facter: 8   Delegated administration
Debug: Facter: 9   refquota and refreservation properties
Debug: Facter: 10  Cache devices
Debug: Facter: 11  Improved scrub performance
Debug: Facter: 12  Snapshot properties
Debug: Facter: 13  snapused property
Debug: Facter: 14  passthrough-x aclinherit
Debug: Facter: 15  user/group space accounting
Debug: Facter: 16  stmf property support
Debug: Facter: 17  Triple-parity RAID-Z
Debug: Facter: 18  Snapshot user holds
Debug: Facter: 19  Log device removal
Debug: Facter: 20  Compression using zle (zero-length encoding)
Debug: Facter: 21  Deduplication
Debug: Facter: 22  Received properties
Debug: Facter: 23  Slim ZIL
Debug: Facter: 24  System attributes
Debug: Facter: 25  Improved scrub stats
Debug: Facter: 26  Improved snapshot deletion performance
Debug: Facter: 27  Improved snapshot creation performance
Debug: Facter: 28  Multiple vdev replacements
Debug: Facter: For more information on a particular version, including supported releases,
Debug: Facter: see the ZFS Administration Guide.
Debug: Facter: process exited with status code 0.
Debug: Facter: fact "zpool_version" has resolved to "5000".
Debug: Facter: fact "zpool_featureflags" has resolved to "async_destroy,empty_bpobj,lz4_compress,multi_vdev_crash_dump,spacemap_histogram,enabled_txg,hole_birth,extensible_dataset,embedded_data,bookmarks,filesystem_limits,large_blocks,large_dnode,sha512,skein,device_removal,obsolete_counts,zpool_checkpoint,spacemap_v2".
Debug: Facter: fact "zpool_featurenumbers" has resolved to "1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28".
Debug: Facter: resolving memory facts.
Debug: Facter: fact "memoryfree" has resolved to "1.53 GiB".
Debug: Facter: fact "memoryfree_mb" has resolved to 1567.76.
Debug: Facter: fact "memorysize" has resolved to "1.96 GiB".
Debug: Facter: fact "memorysize_mb" has resolved to 2008.98.
Debug: Facter: fact "memory" has resolved to {
system => {
available => "1.53 GiB",
available_bytes =><PHONE_NUMBER>,
capacity => "21.96%",
total => "1.96 GiB",
total_bytes =><PHONE_NUMBER>,
used => "441.22 MiB",
used_bytes => 462655488
}
}.
Debug: Facter: resolving disk facts.
Debug: Facter: Skipping config descr because it has a null value
Debug: Facter: Skipping config ident because it has a null value
Debug: Facter: Skipping config ident because it has a null value
Debug: Facter: fact "blockdevice_vtbd0_size" has resolved to<PHONE_NUMBER>2.
Debug: Facter: fact "blockdevice_cd0_model" has resolved to "BHYVE BHYVE DVD-ROM".
Debug: Facter: fact "blockdevice_cd0_size" has resolved to 2850816.
Debug: Facter: fact "blockdevice_cd1_model" has resolved to "BHYVE BHYVE DVD-ROM".
Debug: Facter: fact "blockdevice_cd1_size" has resolved to 358400.
Debug: Facter: fact "blockdevices" has resolved to "vtbd0,cd0,cd1".
Debug: Facter: fact "disks" has resolved to {
cd0 => {
model => "BHYVE BHYVE DVD-ROM",
size => "2.72 MiB",
size_bytes => 2850816
},
cd1 => {
model => "BHYVE BHYVE DVD-ROM",
size => "350.00 KiB",
size_bytes => 358400
},
vtbd0 => {
serial_number => "BHYVE-75AC-A9D6-AE16",
size => "20.00 GiB",
size_bytes =><PHONE_NUMBER>2
}
}.
Debug: Reset text domain to :production
Debug: importing '/usr/local/etc/puppet/modules/bsd/manifests/network/interface/trunk.pp' in environment production
Debug: Automatically imported bsd::network::interface::trunk from bsd/network/interface/trunk into production
Warning: This method is deprecated, please use the stdlib validate_legacy function,
with Pattern[]. There is further documentation for validate_legacy function in the README. at ["/usr/local/etc/puppet/modules/bsd/manifests/network/interface/trunk.pp", 17]:
(location: /usr/local/etc/puppet/modules/stdlib/lib/puppet/functions/deprecation.rb:28:in `deprecation')
Debug: importing '/usr/local/etc/puppet/modules/bsd/manifests/network/interface.pp' in environment production
Debug: Automatically imported bsd::network::interface from bsd/network/interface into production
Debug: Config is: {:name=>"lagg10", :addresses=>["<IP_ADDRESS>/24"], :options=>["laggproto lacp", "laggport vlan10", "laggport vlan11"]}
Debug: Data is: {:lagg10=>{:addrs=>["inet <IP_ADDRESS>/24 laggproto lacp laggport vlan10 laggport vlan11"]}}
Debug: Returning resources: {"ifconfig_lagg10"=>{"value"=>"inet <IP_ADDRESS>/24 laggproto lacp laggport vlan10 laggport vlan11"}}
Debug: importing '/usr/local/etc/puppet/modules/bsd/manifests/network/interface/cloned.pp' in environment production
Debug: Automatically imported bsd::network::interface::cloned from bsd/network/interface/cloned into production
Notice: Compiled catalog for freebsd1.my.domain in environment production in 0.08 seconds
Debug: Creating default schedules
Info: Applying configuration version '1565830073'
Debug: /Stage[main]/Main/Bsd::Network::Interface::Trunk[lagg10]/Bsd::Network::Interface[lagg10]/Shellvar[ifconfig_lagg10]/before: before to Bsd_interface[lagg10]
Debug: /Stage[main]/Main/Bsd::Network::Interface::Trunk[lagg10]/Bsd::Network::Interface[lagg10]/Shellvar[ifconfig_lagg10]/notify: notify to Bsd_interface[lagg10]
Notice: /Stage[main]/Main/Bsd::Network::Interface::Trunk[lagg10]/Bsd::Network::Interface[lagg10]/Shellvar[ifconfig_lagg10]/ensure: created
Info: /Stage[main]/Main/Bsd::Network::Interface::Trunk[lagg10]/Bsd::Network::Interface[lagg10]/Shellvar[ifconfig_lagg10]: Scheduling refresh of Bsd_interface[lagg10]
Debug: /Stage[main]/Main/Bsd::Network::Interface::Trunk[lagg10]/Bsd::Network::Interface[lagg10]/Shellvar[ifconfig_lagg10]: The container Bsd::Network::Interface[lagg10] will propagate my refresh event
Debug: Prefetching freebsd resources for bsd_interface
Debug: Executing: '/sbin/ifconfig -C'
Debug: Executing: '/sbin/ifconfig'
Debug: Executing: '/usr/sbin/service netif restart lagg10'
Notice: /Stage[main]/Main/Bsd::Network::Interface::Trunk[lagg10]/Bsd::Network::Interface[lagg10]/Bsd_interface[lagg10]: Triggered 'refresh' from 1 event
Debug: /Stage[main]/Main/Bsd::Network::Interface::Trunk[lagg10]/Bsd::Network::Interface[lagg10]/Bsd_interface[lagg10]: The container Bsd::Network::Interface[lagg10] will propagate my refresh event
Debug: Bsd::Network::Interface[lagg10]: The container Bsd::Network::Interface::Trunk[lagg10] will propagate my refresh event
Debug: Bsd::Network::Interface::Trunk[lagg10]: The container Class[Main] will propagate my refresh event
Debug: Class[Main]: The container Stage[main] will propagate my refresh event
Debug: Finishing transaction<PHONE_NUMBER>0
Debug: Storing state
Info: Creating state file /var/puppet/state/state.yaml
Debug: Pruned old state cache entries in 0.00 seconds
Debug: Stored state in 0.01 seconds
Notice: Applied catalog in 0.28 seconds
Debug: Applying settings catalog for sections reporting, metrics
Debug: Finishing transaction<PHONE_NUMBER>0
Debug: Received report to process from freebsd1.my.domain
Debug: Processing report from freebsd1.my.domain with processor Puppet::Reports::Store

grep -R clone /etc/*

/etc/defaults/rc.conf:cloned_interfaces=""              # List of cloned network interfaces to create.
/etc/defaults/rc.conf:#cloned_interfaces="gif0 gif1 gif2 gif3" # Pre-cloning GENERIC config.
/etc/mtree/BSD.tests.dist:                        zfs_clone
/etc/network.subr:# clone_up
/etc/network.subr:#     Create cloneable interfaces.
/etc/network.subr:clone_up()
/etc/network.subr:      for ifn in ${cloned_interfaces}; do
/etc/network.subr:              warn "$gif_interfaces is obsolete.  Use $cloned_interfaces instead."
/etc/network.subr:              echo "Created clone interfaces: ${_list# }."
/etc/network.subr:# clone_down
/etc/network.subr:#     Destroy cloned interfaces. Destroyed interfaces are echoed to
/etc/network.subr:clone_down()
/etc/network.subr:      : ${cloned_interfaces_sticky:=NO}
/etc/network.subr:      if checkyesno cloned_interfaces_sticky; then
/etc/network.subr:      for ifn in ${cloned_interfaces} ${gif_interfaces}; do
/etc/network.subr:              echo "Destroyed clone interfaces: ${_list# }."
/etc/network.subr:      debug "Destroyed clones: ${_list# }"
/etc/network.subr:#     Note that the list will include cloned interfaces if applicable.
/etc/network.subr:              for _if in ${network_interfaces} ${cloned_interfaces}; do
/etc/rc.d/netif:cloneup_cmd="clone_up"
/etc/rc.d/netif:clonedown_cmd="clone_down"
/etc/rc.d/netif:extra_commands="cloneup clonedown clear vnetup vnetdown"
/etc/rc.d/netif:        # Create cloned interfaces
/etc/rc.d/netif:        clone_up $cmdifn
/etc/rc.d/netif:        _clone_down=1
/etc/rc.d/netif:        _clone_down=
/etc/rc.d/netif:        # Destroy cloned interfaces
/etc/rc.d/netif:        if [ -n "$_clone_down" ]; then
/etc/rc.d/netif:                clone_down $cmdifn

Thank you.  Please also grep lagg /var/puppet/state/resources.txt.

Oh I think maybe I see the issue.

If you try a single digit lagg, like lagg9 for example, does that work?  It looks like a regex issue.

I think maybe https://github.com/xaque208/puppet-bsd/pull/130 will resolve your issue if it the two digit lagg problem that it appears to be.  Would you mind testing and letting me know how it goes please?

@xaque208 Cool, you are right! it was a regex problem.
( yes, I originally had two digit in nic name )
now:
 bsd::network::interface::trunk { 'lagg10':
     interface => [ 'vlan1', 'vlan10' ],
     address   => [ '<IP_ADDRESS>/24' ],
 }

 bsd::network::interface::trunk { 'lagg2':
     interface => [ 'vlan2', 'vlan3' ],
     address   => [ '<IP_ADDRESS>/24' ],
 }

 bsd::network::interface::trunk { 'lagg56':
     interface => [ 'vlan5', 'vlan6' ],
     address   => [ '<IP_ADDRESS>/24' ],
 }

result in /etc/rc.conf:

cloned_interfaces="lagg10 lagg2 lagg56"
ifconfig_lagg10="inet <IP_ADDRESS>/24 laggproto lacp laggport vlan1 laggport vlan10"
ifconfig_lagg2="inet <IP_ADDRESS>/24 laggproto lacp laggport vlan2 laggport vlan3"
ifconfig_lagg56="inet <IP_ADDRESS>/24 laggproto lacp laggport vlan5 laggport vlan6"

Thanks so much for the support!

Great!  Thank you for the patience.  I've merged to master, but been lazy about versions.  I'll cut a version for this.


Ignore. Bug bounty testing... sfusvd

Ignore. Bug bounty testing... sfusvd

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Case sensivity for attribute selectors

There is a difference between CSS and XPath in case sensivity of attributes.
Having these elements on the page:
<form method="post" id="new_user" />
<form method="POST" id="delete_user" />

you can query them in browser:
> document.querySelectorAll('form[method="post"]')
< NodeList [<form id="new_user">, <form id="delete_user">] (2)

> document.querySelectorAll('form[method="POST"]')
< NodeList [<form id="new_user">, <form id="delete_user">] (2)

> $x('.//form[@method="post"]')
< [<form id="new_user">] (1)

> $x('.//form[@method="POST"]')
< [<form id="delete_user">] (1)

This comes from the fact that XPath considers attributes case sensitive while CSS does not.
Since now Watir only uses XPath selectors, using method: 'post' selector would return only one element. But when Watir is used with watir_css or watizzle gems, same selector would return two elements.
Also compare plain Selenium:
driver.find_elements(xpath: './/form[@method="post"]').count # returns 1
driver.find_elements(css: 'form[method="post"]').count       # returns 2

Since two behaviours cannot co-exist, I'm not sure what to do about it.
Related links:

CSS3 Selectors Case Sensiviity

which would you prefer? Do we want to adjust our xpath selector to make this case independent?

I think I'd like to make it case insensitive, but I'm afraid that might break many tests, so maybe we should keep that until Watir 7.

Please note that in CSS only some attribute values are case insensitive.
For example, class / id / href are case sensitive.

@titusfortner I'll do my best but time is pretty limited now :)
@twalpole I don't get what you mean by "enumerated types". Can you elaborate?

@p0deje https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#keywords-and-enumerated-attributes - case insensitivity is for the attributes defined to be allowed a specific set of values (enumerated attributes) on specific elements - If those same attributes were used on elements they are not defined for then they should be case sensitive. Whether that's worth worrying about is  debatable though.

I've prepared #856 to implement the solution, please have a look when you have time.
For now, I've just hardcoded case-insensitive attributes as I don't think it's going to change much. Otherwise, we can still add it to spec generator.


Large corridor clipped on the edge of the globe

Sandcastle
Forum thread

Rotate the globe and you'll see that this is supposed to be a full corridor that gets clipped at the left edge of the globe in the picture above.
If you replace line 25:
geometry: new Cesium.CorridorGeometry( ovalDesc ),

with:
geometry: circleGeom,

You'll see that a large circle gets rendered fine without clipping.

I wonder if this is related to https://github.com/AnalyticalGraphicsInc/cesium/issues/4483

any news on the fix for this issue?

@ninanga no sorry, we haven't had a chance to look into this yet.  If you have time to look into a fix, we would be happy to review a pull request!  Thanks


pure css file input cloaking with pointer-events: none

http://codepen.io/anon/pen/yeVOVr
not sure if desired, but others might find useful.

Thanks for sharing! It's probably worthwhile to submit this as a Building Block. Not totally sure how you do that though.

A better solution would be to set a z-index on the file input. Then it will work in browsers that don't support pointer-events.

@natewiebe13 updated.

@andycochran With this method, would our <label> CSS conflict with the .button CSS?

@andycochran Also, is one approach or the other better for accessibility, do you think?

To be honest, I've yet to use this method with F6.
Just tried a quick experiment and it seems to work fine:
http://codepen.io/anon/pen/MKpLNx
I'm not sure which is better for accessibility. The label method might be more semantic tho. And simpler (zero custom CSS).

i like andy's solution the best, since it doesn't interfere with hover/active/focus states like mine did.

Thinking about accessibility, it should be noted that any solution that hides the input disables browser functionality that displays the chosen filename. So you also need a client-side solution to show the action. Something like:
var fileLoader = $('#file-input')[0];

fileLoader.addEventListener('change', handleFile, false);

function handleFile(){
  // do something with the chosen file
}

@andycochran Does hiding with opacity: 0 count?

I'd say so. You can't see it if it's transparent. :smile:
This is really more UX than accessibility—I think .show-for-sr takes care of a11y.

@andycochran Ah well specifically I was wondering if a file input with opacity: 0 actually becomes non-interactive. But it seems like the clip() method works fine, and a screen reader still reads the element.
I do like this approach because it doesn't even appear to require any extra CSS.


Fsharp preview 20171024 lose File resort and cause errors

Already know that f# modules read by a sorted file order. A+B file,B file can open fileA's module,but fileA can not find fileB module.
Its been solved before use a alt+arrow to sort files manually,but the lastest version remove this function,so errors shows again.
Repro steps
Provide the steps required to reproduce the problem

Create a net standard project,target .net standard1.6

Add a codefile ,name B,some basic module

3.Add another coldfile, name A
These files will be auto sorted by filename ,so B will under A even B is created first.
Expected behavior
A can open a module in B
Actual behavior
according to the file order, A can not open modules in B, but B can read modules in A
Known workarounds
No, since the alt+arrow be removed

@Huqin-China This actually has nothing to do with the visual order in the UI, but rather the project file:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netstandard2.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Compile Include="A.fs" />
    <Compile Include="B.fs" />
    <Compile Include="Library.fs" />
  </ItemGroup>

</Project>

For .NET Core/.NET Standard projects, when you add a new file the <Compile> tag gets added to the top of the list of files.  This is why A.fs cannot use anything defined in B.fs.  You'll need to manually change the ordering in the project file.  This is actually quite easy now:

No need to unload the project in VS.  The two issues you mention:

Compile order not shown in the UI
Lack of right-click gestures to move them around in the UI

Are tracked with these issues in the project system repository:
https://github.com/dotnet/project-system/issues/2793
https://github.com/dotnet/project-system/issues/2887
I'll close this for now, since the experience gaps are going to come from work in the project system repository rather than this one.

@cartermp ,tks.
Hope the projectsystem team  solve the compile problems soon without adjust the project file.
I used to the F# file order feature.This solution, UI order is different from compile order(what u see is not what u get).
thanks again.


AddASPathSegment(asSeg...) is appending only first AS number

Hi,
With current code AddASPathSegment(asSeg...) option in ATE is appending only the first AS number.
For eg., with below code , only first AS in list 65505 is seen in the routes received in the DUT from ATE.
asSeg := []uint32{65505, 65501, 65503}
bgpNeti1.BGP().WithNextHopAddress(ateSrc.IPv4).AddASPathSegment(asSeg...).WithTypeSEQ()
Also gnmi get on ATE fails if "WithTypeSet" is used .
script code:    ASseg := []uint32{65501, 600}, WithTypeSet option
Error:
bgp_remove_private_as_test.go:263: Await(t) on ate(<IP_ADDRESS>) at /network-instances/network-instance[name=atedst]/protocols/protocol[identifier=BGP][name=0]/bgp/rib/afi-safis/afi-safi[afi-safi-name=IPV4_UNICAST]/ipv4-unicast/neighbors/neighbor[neighbor-address=]/adj-rib-in-pre/routes/route[path-id=0][prefix=]/state/prefix: error receiving gNMI response: failed to append details for elem 0: invalid AS path string: "<500 100> {65501}"
Can you please help fix this issue?
Thanks,
Prabha

@cprabha the error in the gnmi response when using WithTypeSet is a bug that I will fix.
The issue of "only first AS in list 65505 is seen in the routes received in the DUT from ATE" is not necessarily a bug in Ondatra. The question there is whether IxNetwork is configured correctly. Can you check whether IxNetwork is configured to have all three "65505, 65501, 65503" in the AS path segment? If it is, then the Ondatra contract (to configure IxNetwork correctly) has been met.

Hi Greg,
I did check routes on ATE , it shows first AS number even though three as segments are set in API.
@.***
Thanks,
Prabha
From: Greg Dennis @.>
Sent: Thursday, May 25, 2023 3:41 PM
To: openconfig/featureprofiles @.>
Cc: Prabha Chethan @.>; Mention @.>
Subject: Re: [openconfig/featureprofiles] AddASPathSegment(asSeg...) is appending only first AS number (Issue #1659)
[External Email. Be cautious of content]
@cprabhahttps://urldefense.com/v3/__https:/github.com/cprabha__;!!NEt6yMaO-gk!EWu6slePIXbQAXxNIY594v82RLeQeaDdGmbMvsVamkHU2r89kCeboGYcab0n3i7WPRhrmCkgHZaWkUdIGN-F-pUi$ the error in the gnmi response when using WithTypeSet is a bug that I will fix.
The issue of "only first AS in list 65505 is seen in the routes received in the DUT from ATE" is not necessarily a bug in Ondatra. The question there is whether IxNetwork is configured correctly. Can you check whether IxNetwork is configured to have all three "65505, 65501, 65503" in the AS path segment? If it is, then the Ondatra contract (to configure IxNetwork correctly) has been met.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/openconfig/featureprofiles/issues/1659*issuecomment-1563596472__;Iw!!NEt6yMaO-gk!EWu6slePIXbQAXxNIY594v82RLeQeaDdGmbMvsVamkHU2r89kCeboGYcab0n3i7WPRhrmCkgHZaWkUdIGJhOCuNB$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AHCEB5V4A25DGE6OMA2TC7LXH7NV7ANCNFSM6AAAAAAYPJBMXQ__;!!NEt6yMaO-gk!EWu6slePIXbQAXxNIY594v82RLeQeaDdGmbMvsVamkHU2r89kCeboGYcab0n3i7WPRhrmCkgHZaWkUdIGLk8-IiR$.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>Juniper Business Use Only

Based on Number of As Segments the Number of AS# In Segment needs to be updated.
Raised PR https://github.com/openconfig/ondatra/pull/76 to fix the issue

The PR from @ANISH-GOTTAPU fixes the first issue.
I am working on the gnmi issue right now.
I'll comment back when both fixed are merged into Ondatra.

This is fixed in the latest Ondatra release https://github.com/openconfig/ondatra/releases/tag/v0.1.16
I'll update featureprofiles to require this release

Thanks Greg.
-Prabha.
From: Greg Dennis @.>
Sent: Tuesday, May 30, 2023 10:28 AM
To: openconfig/featureprofiles @.>
Cc: Prabha Chethan @.>; Mention @.>
Subject: Re: [openconfig/featureprofiles] AddASPathSegment(asSeg...) is appending only first AS number (Issue #1659)
[External Email. Be cautious of content]
This is fixed in the latest Ondatra release https://github.com/openconfig/ondatra/releases/tag/v0.1.16https://urldefense.com/v3/__https:/github.com/openconfig/ondatra/releases/tag/v0.1.16__;!!NEt6yMaO-gk!Fz7Gra5tu_RYng3ElV_jEmd3cgo39xUM4ds-Vo7wIw-J-QrMLenUB_1bFf7gpE49uEvP9p1_6w1zkCF79372cI5I$
I'll update featureprofiles to require this release
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/openconfig/featureprofiles/issues/1659*issuecomment-1568806281__;Iw!!NEt6yMaO-gk!Fz7Gra5tu_RYng3ElV_jEmd3cgo39xUM4ds-Vo7wIw-J-QrMLenUB_1bFf7gpE49uEvP9p1_6w1zkCF79z_FWGfR$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AHCEB5VRSCCE5DPVN3GALCTXIYUZPANCNFSM6AAAAAAYPJBMXQ__;!!NEt6yMaO-gk!Fz7Gra5tu_RYng3ElV_jEmd3cgo39xUM4ds-Vo7wIw-J-QrMLenUB_1bFf7gpE49uEvP9p1_6w1zkCF7907QANkR$.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>Juniper Business Use Only

Hi Greg,
I am still seeing issue with as path on ATE. It shows different AS number then which is configured one on sent routes.
Routes sent to ATE have as paths :<PHONE_NUMBER>1 65507 65554
on ATE it shows :<PHONE_NUMBER>1 65507 23456
I have attached screen shot from ixia . please check.
Thanks,
Prabha

Also this path can contain as path as {65501} when SET mode is used.
so return value need to be changed from uint32 to different value ?

@cprabha, I'm not clear on why uint is a problem here? 65501 is a valid uint. It seems the problem is that Ixia is now comma-separating the segment members as opposed to separating them with whitespace? I have only seen it whitespace separated in IxNetwork -- maybe it's version dependent? @ANISH-GOTTAPU, the segment members can be either space-separated or comma-separated in the learned info?

@cprabha, could you link me to a draft PR that repro's the issue, too?

@ANISH-GOTTAPU, in @cprabha's first comment above the error shows as invalid AS path string: "<500 100> {65501}". That's a space between 500 and 100, and that's what I've see in IxNetwork. Is it sometimes spaces and sometimes commas?

@greg-dennis I have added script for both "SET"  and "SEQ" (currently working fine) . please check.
https://github.com/cprabha/featureprofiles/blob/AsPathSet/feature/bgp/aspath/ate_tests/bgp_remove_private_as_new_test.go
In both Seq and Set mode it is space separated, in Set mode it adds {} to those AS numbers which are added using Set mode.

@cprabha, sorry what's the status of this? Do you still have an issue here? Any knowledge of the what the brackets mean in "[800 65501 600]"?

@greg-dennis ,  There are multiple modes in AS PATH . SET , SEQ  , SET confed, SEQ confed.
We might see different pattern in each of these modes.
I have tested SET and SEQ , SEQ is space separated and SET has pair of {}.

I could not find any document around this pattern  to share.

I found it is comma-separated in SETs and space-separated in SEQs. Example:
<500 100> {65501,65507,65534}
Weird. I'll try to make the parsing logic robust to both.

This is fixed in the latest Ondatra release https://github.com/openconfig/ondatra/releases/tag/v0.1.23

Thanks @greg-dennis .

@greg-dennis , looks like these changes are not merged in otg. I am not getting AS numbers appended at OTG.
Please could you check.

@cprabha, IxNetwork and OTG gnmi are entirely separate. IxNetwork gNMI is provided by a server that Google wrote and is embedded in Ondatra. OTG provides an entirely different yang model. I don't know whether they model the as path segments, but you'd have to take a look at the OTG yang models or ask Keysight.

@cprabha, IxNetwork and OTG gnmi are entirely separate. IxNetwork gNMI is provided by a server that Google wrote and is embedded in Ondatra. I take responsibility for fixing issues there. OTG provides an entirely different yang model. I don't know whether they model the as path segments, but you'd have to take a look at the OTG yang models or ask Keysight. As you may be aware, it's our goal to move entirely to OTG and deprecate IxNetwork.

Thanks @greg-dennis . I have opened issue under otg for ixia to help on this issue in otg.


Add support for NotResources

https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_notresource.html

Method notResources is available since 5847b1d.


⚠ Bofrost.at has degraded performance

In cbd4d99, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1914 ms

Resolved: Bofrost.at performance has improved in ce657d0.


[Maintenance] Rename to SyliusPlugin

Part of #3.
I have to update to newest master to have SyliusPluginTrait so probably we should wait with merge to beta2

👍

Replaced by #21.


create a bot to canary the dart sdk roll

Create a bot to canary the dart sdk roll:

one bot runs the tests (test.sh)
move the doc gen to a separate bot (docs.sh) - this will speed up the regular test bot
create another bot which forces the dart sdk to the latest dev version and runs the tests against that (sdk_canary.sh).

This will give us early warning of issues w/ rolling to the next dev sdk release. It does mean that people's PRs will turn red when there are no issues w/ those specific PRs. Not sure what the best recourse there is; having people TBR the canary bot off? Moving the canary to only run when called from a travis cron job?

(some work to do on this one still)

Shouldn't the SDK test be on the SDK bot?

I don't think this is the right approach.  Instead of using Travis to test integration with futuristic Dart SDKs, we should test this on build.chromium.org, probably in the client.dart project.

we should test this on build.chromium.org, probably in the client.dart project

That would give the sdk repo visibility into compatibility with flutter, but they wouldn't necessarily have a recourse if the bot went red. The bot would stay red until a new sdk release was published, that release rolled into the flutter sdk, and whatever corresponding changes made to the repo.
Mostly what I'm trying to accomplish with this is to get advance warning when there are changes necessary for the next sdk roll (and soe sense for the amount of changes). The time it took to do the last roll caused some issues, esp. when other things got blocked behind it (like the internal roll).
Happy to close this if we want to discuss other solutions -


FMA Instructions Support?

Hello, thank you excellent work!
I have an AMD CPU (FX8300) that supports FMA3 / 4 Instructions, No AVX2.
I noticed that thorium once supported FMA.
https://github.com/Alex313031/thorium/commit/2a16b6ea0ed7c0ccafc814e35a6c9a2ef573fe0d
Why not support it now?
Thank you.

@MedievalSteel I also had an FX CPU.
AMD FX are the ONLY CPUs that have FMA, but not AVX2.
Therefore it doesn't make sense to make AVX builds with FMA, since only people with these specific CPUs would be able to run them.
You can use the AVX release. The performance difference from adding only FMA to the mix is negligible.


Error in retrieving token. Twitter

When I try login via twitter, I get error "Error in retrieving token.".
I think it when authenticate $eauth->authenticate()
What I do wrong?

Error was in
$token = $proxy->requestRequestToken();
of nodge\eauth\oauth1\Service::authenticate() method
then nodge\eauth\oauth1\ServiceProxy::parseRequestTokenResponse()
Error http://joxi.ru/a2X4KLnSy8blZ2
So I unchecked "Enable Callback Locking" in application settings.
Now all working fine.

@romanson-god is this available in new app,cant find it. ""Enable Callback Locking" in application settings."?


Docker - pre-created network removed in create.yml

Issue Type

Bug report

Molecule and Ansible details
See below
Molecule installation method (one of):

pip

Ansible installation method (one of):

pip

Detail any linters or test runners used:
Behavior
EDIT: Further testing has shown that this seems to be a bug introduced with Molecule 3.0.4. I ran the test again after installing Molecule <IP_ADDRESS> from pip3. I can't test if it also happens with Molecule 3.0.4 and Python2, as it is not available.
After converting my Ansible dev environment (where I normally make roles) to python3 only, something broke in the docker networking.
Given the following molecule.yml (a seperate dependency.yml is in place to create the network mentioned):
---
dependency:
  name: 'shell'
  command: ansible-playbook ${MOLECULE_PROJECT_DIRECTORY}/molecule/default/dependency.yml -i localhost,
driver:
  name: 'docker'
lint: |
  set -e
  yamllint -c molecule/default/yamllint.yml .
  ansible-lint molecule/default/converge.yml
platforms:
  - name: "acme-ssl-client"
    image: "geerlingguy/docker-${MOLECULE_DISTRO:-debian10}-ansible:latest"
    command: '/lib/systemd/systemd'
    pre_build_image: true
    volumes:
      - '/sys/fs/cgroup:/sys/fs/cgroup:ro'
    privileged: true
    networks:
      - name: "acmenet"
        ipv4_address: '<IP_ADDRESS>'
  - name: "acme-ssl-helper"
    image: "geerlingguy/docker-debian10-ansible:latest"
    command: '/lib/systemd/systemd'
    pre_build_image: true
    volumes:
      - '/sys/fs/cgroup:/sys/fs/cgroup:ro'
    privileged: true
    networks:
      - name: "acmenet"
        ipv4_address: '<IP_ADDRESS>'
  - name: 'pebble'
    image: 'letsencrypt/pebble'
    command: 'pebble --dnsserver <IP_ADDRESS>:53'
    pre_build_image: true
    networks:
      - name: "acmenet"
        ipv4_address: '<IP_ADDRESS>'
provisioner:
  name: 'ansible'

For this environment to work, I need to be able to assign static IPs to each of the docker containers. This used to work, but after converting to python3 only, I received the following error message from Docker: 400 Client Error: Bad Request ("user specified IP address is supported only when connecting to networks with user configured subnets")
Python 3
When running molecule create with python3, I can observe the following actions on the Docker daemon for networks. I have commented for clarity:
2020-05-08T13:05:03.393276006+02:00 network destroy a5941947a10d00e5d6c31113c4e79ab5a5072e4701639d65d5e065dbdda03082 (name=acmenet, type=bridge) # Precreation destroy
2020-05-08T13:05:18.444261785+02:00 network create eb0f4bc5ff8b0185d874df2712bec7fd72f432ec58c01446e18382e04c677c9e (name=acmenet, type=bridge) # Created by dependency.yml
2020-05-08T13:05:24.939964452+02:00 network destroy eb0f4bc5ff8b0185d874df2712bec7fd72f432ec58c01446e18382e04c677c9e (name=acmenet, type=bridge) # Destroyed for some reason
2020-05-08T13:05:24.986557118+02:00 network create e779303608cf568594d3868eeb4f5de063c2badd29cf3aaf63db89de682a59cf (name=acmenet, type=bridge) # Created by create.yml, broken as it does not accept user-set IP addresses for containers

Molecule task output:
    TASK [Create docker network(s)] ************************************************
    changed: [localhost] => (item=acmenet)
    ok: [localhost] => (item=acmenet)
    ok: [localhost] => (item=acmenet)

Molecule --version
molecule 3.0.4
   ansible==2.9.7 python==3.7

Python 2
Running the same config with python2, gives the following output on the Docker daemon:
2020-05-08T14:26:54.063793066+02:00 network create 3e7457009acb86e1c5f29ebfa3379a9a51f16ed5147077dedd2c616d327fc673 (name=acmenet, type=bridge)

Molecule task output:
TASK [Create docker network(s)] ************************************************
    ok: [localhost] => (item=acmenet)
    ok: [localhost] => (item=acmenet)
    ok: [localhost] => (item=acmenet)

molecule --version
molecule <IP_ADDRESS>
   ansible==2.9.7 python==2.7

I hope it's clear enough, let me know if it isn't! :-)

Hi @Thulium-Drake,
I hit the same issue. This was introduced with molecule 3.0.3 by 4ef8cfb1.
molecule now set an owner label on the network:
https://github.com/ssbarnea/molecule/blob/4ef8cfb173e7128570b16a28726dd73aa1a6eb40/molecule/provisioner/ansible/playbooks/docker/create.yml#L93-L106
When the task runs, docker_network detects a change and recreate the network. (Module doc: When network options are changed, the module disconnects all containers from the network, deletes the network, and re-creates the network.). Because we cannot define the subnet in the molecule configuration, the network is created with a random subnet. Check docker network inspect acmenet.
You can update your dependency.yml to add the label {owner: 'molecule'}:
    - name: "Create docker network(s)"
      docker_network:
        name: "net1"
        ipam_config:
          - subnet: "<IP_ADDRESS>/24"
            gateway: "<IP_ADDRESS>"
        state: present
        labels:
          owner: molecule

By the way, I like the dependency.yml to configure the docker network, I will use it. Thanks!

Hi @actatux,
That's it! Did I miss that in the docs, or isn't it there?
Thanks! It seemed like a very elegant way to set this up :-)

It's not documented. Check PR#2696 which would introduce support of docker_network configuration in the platforms.

That PR looks very promising! Anything I can do to assist with that?

Could you test it in your environment to see if it can match your needs? Report any misunderstanding or caveats? Thanks ;-)

Works like a charm! I have one question regarding to how molecule.yml has to look now.
Would it be possible to move docker_networks to the level of platforms? That seems more logical to me. Like so:
---
driver:
  name: 'docker'
lint: |
  set -e
  yamllint -c molecule/default/yamllint.yml .
  ansible-lint molecule/default/converge.yml
docker_networks:
  - name: 'acmenet'
    ipam_config:
      - subnet: '<IP_ADDRESS>/24'
platforms:
  - name: "acme-ssl-client"
    image: "geerlingguy/docker-${MOLECULE_DISTRO:-debian10}-ansible:latest"
    command: '/lib/systemd/systemd'
    pre_build_image: true
    volumes:
      - '/sys/fs/cgroup:/sys/fs/cgroup:ro'
    privileged: true
    networks:
      - name: "acmenet"
        ipv4_address: '<IP_ADDRESS>'
  - name: "acme-ssl-helper"
    image: "geerlingguy/docker-debian10-ansible:latest"
    command: '/lib/systemd/systemd'
    pre_build_image: true
    volumes:
      - '/sys/fs/cgroup:/sys/fs/cgroup:ro'
    privileged: true
    networks:
      - name: "acmenet"
        ipv4_address: '<IP_ADDRESS>'
  - name: 'pebble'
    image: 'letsencrypt/pebble'
    command: 'pebble --dnsserver <IP_ADDRESS>:53'
    pre_build_image: true
    networks:
      - name: "acmenet"
        ipv4_address: '<IP_ADDRESS>'
provisioner:
  name: 'ansible'

Hi @Thulium-Drake ,
PR #2696 merged.
Your proposal would need a change in the code with a new class Networks, similar to Platforms. This would be a huge rework.

Hi @actatux,
Makes sense, well, the PR fixes this problem, so I'll close the issue :-)
Thanks for the good work!


Feature request: Easily change merchants price

Is your feature request related to a problem? Please describe.
I would like to change an items price instead of changing the items price value.
It's really irritating to have to go into the item and change it every time
Describe the solution you'd like
On the Loot sheet for the merchant I would like to be able to click on the current price and fill in a price I want.

Closest thing to that is using the price modifier but it applies equally to all items.
On Sep 27, 2024 at 10:25 AM -0700, kay1010100 @.***>, wrote:

Is your feature request related to a problem? Please describe.
I would like to change an items price instead of changing the items price value.
It's really irritating to have to go into the item and change it every time
Describe the solution you'd like
On the Loot sheet for the merchant I would like to be able to click on the current price and fill in a price I want.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Yea I know, but I'm talking about separate items


Spyder "Autocompletion / Go to definition" fails on Windows when an import folder is named "array"

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[N/A] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[x] Reset preferences with spyder --reset
[x] Reinstalled the latest version of Anaconda
[N/A] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
What steps reproduce the problem?

Install the current anaconda with spyder on Windows (Anaconda3-2024.02-1-Windows-x86_64)
Create a repository which contains a folder named "array"

Create a folder to be integrated as repository, lets call it "testrepo". Add that folder in the pythonpath manager.
Create some subfolder e.g. "pathdebug" and add an empty init.py.
Create a subfolders in testrepo/pathdebug named "array".
Inside that, add an empty init.py and a simple python file that can be imported from, e.g. test.py with some definition of an empty function.

Open an empty python file in spyder and start to type 'from pathdebug.array.test import...'

What is the expected output? What do you see instead?
This happens and this is expected: After the first dot i.e. 'from pathdebug.' the autcompletion pops up an suggests 'array' as a followup package.
Then this happens and this is not expected: after the second dot 'from pathdebug.array.' no autocompletion pops up and it cannot be forced to pop up even with Ctrl+Space. Also, right click on 'array' and "go to definition" will not open the init of the folder.
You may then continue to import the empty function from inside the array folder, but "Go to definition" will not work.
This seems to be directly related to the name "array". Renaming the folder to something else e.g. "notArray" solves the problem. Then autocompletion works and goto definition works again.
We have seen this issue on two windows machines, but could not see it on a linux setup (possibly a different version of spyder though).
Versions

Spyder version: 5.5.1  (conda)
Python version: 3.11.7 64-bit
Qt version: 5.15.2
PyQt5 version: 5.15.10
Operating System: Windows-10-10.0.19045-SP0

Hey @wlter, thanks for reporting and the detailed description to reproduce the problem. We'll try to take a look at this after we release Spyder 6.0 next month.


Update locale plugin permissions

Description
Would like to be maintainer of the locale-plugin : https://github.com/jenkinsci/locale-plugin
Submitter checklist for adding or changing permissions
Always

[x] Add link to plugin/component Git repository in description above

For a new permissions file only

[x] Make sure the file is created in permissions/ directory
[x] artifactId (pom.xml) is used for name (permissions YAML file).
[x] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[x] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[ ] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
[x] All newly added users have logged in to Artifactory at least once

Reviewer checklist (not for requesters!)

[x] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
[x] Check that the $pluginId Developers team has Admin permissions while granting the access.
[ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
[ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @Wadeck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it
FYI @oleg-nenashev

@oleg-nenashev can you please not merge unless you do the bot commands as well?
@jonesbusy commit permissions added. Make sure you accept the org invite if your not already in it. I believe it should also show up on https://github.com/jenkinsci/

In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.

do you want the jira default assignee to be transferred to you?

Hi @halkeye I can take the default assignee for Jira tickets.


AzureAD - Username or Password wrong give unfriendly message

Rancher Version: master 6/16
Steps to Reproduce:

Setup Azure Auth
Log out
In login screen put garbage in username
In login screen put in good username but bad password

Results: Non-200 Response from Azure

Expected:  Should say "Username or Password incorrect"

@prachidamle If azure says auth fails the response back to the client should be 401/Unauthorized.

@vincent99 yup, ofcourse. My bad

@vincent99 Azure sadly does not provider standard HTTP errors like 401 for unauthorized.
Instead it sends HTTP 400 and a response body like this:
"error=invalid_grant, error_description=AADSTS50034: To sign into this application the account must be added to the ztad.onmicrosoft.com directory.
Trace ID: 04c11d3d-7760-497d-8a97-abc956399dba
Correlation ID: 93167f34-0496-418f-9e37-3bc2d7386384
Timestamp: 2016-06-16 23:44:45Z, error_codes=[50034], timestamp=2016-06-16 23:44:45Z, trace_id=04c11d3d-7760-497d-8a97-abc956399dba, correlation_id=93167f34-0496-418f-9e37-3bc2d7386384}"
And the Azure code AADSTS50034 means User is not registered!
I guess we will have to just log this Azure code and then present 401 to rancher user.

The UI will display "username or password incorrect" if you send back 401, so it doesn't matter what the exact message from MS is.  If you see that error description (or probably the error=invalid_grant is a better thing to check), return 401.  If you see any other kind of error, you can return what they said and it will be displayed to the user.

@vincent99 yeah I am now returning 401, when I see error=invalid_grant.
In other cases I just return the azure error.

Version - master 6/16
I'm always seeing the error response from Azure now.  I would still prefer a "Username or Password incorrect" or something.

Version - v1.1.0-rc3
Verified fixed


Test 3.2.1-A expects wrong Preference-Applied response

Test 3.2.1-A seems to want to see the URI http://fedora.info/definitions/fcrepo#PreferInboundReferences in the Preference-Applied header. I don't think the is right because the Preference-Applied is not expected to include data from omit="..." or include="..." but just the preference name which is return=representation. See, for example, ex20/21 in LDP and https://tools.ietf.org/html/rfc7240#section-3:

The syntax of the Preference-Applied header differs from that of the Prefer header in that parameters are not included.

(I had this wrong in my test for trilpy too ;-) )

Ah, I see the Fedora 4 example includes the parameter in the Preference-Applied response header -- I guess we could specify that but it goes against RFC7240 by my reading.  Will create Fedora API spec issue.


Normative: Display certain "auto"/0 values in "numeric" style when not displaying them would result in ambiguous/awkward output

As discussed in #170, certain combinations of "display" settings in numeric styles can result in output that's both unclear and awkward. Consider the output from this sequence of formatted durations:
// "1:59:58"
new Intl.DurationFormat('en', {hours: "numeric"}).format({hours: 1, minutes: 59, seconds: 59})
// "1:59:59"
new Intl.DurationFormat('en', {hours: "numeric"}).format({hours: 2, minutes: 0, seconds: 0})
// Old: "2"
// New: "2:00:00"
new Intl.DurationFormat('en', {hours: "numeric"}).format({hours: 2, minutes: 0, seconds: 1})
// Old: "2, 01"
// New: "2:00:01"

This problem arises when there is a unit with style "numeric" or "2-digit", display: "auto", and 0 for its value between two nonzero"numeric"/"2-digit"-styled units. Currently this can only happen when the minutes unit is 0 and "auto", though  there would be other contexts where this problem would arise if the "numeric" format were allowed for additional units in a future DFv2.
This PR takes a couple of steps to ensure that "numeric"/"2-digit" formatting produces more regular results:

When units within a duration are "numeric"/"2-digit"-styled without explicitly being set to "numeric"/"2-digit",  the default display settings for minutes and seconds are now "always" instead of "auto"
In the interest of never formatting "numeric"/"2-digit" formatted durations as comma-separated lists of one item each, when a  "numeric"/"2-digit"-styled unit appears between two other actually displayed "numeric"/"2-digit"-styled units, that middle unit is displayed even if it is 0 and even if the display option for that unit is set to "auto".

TG2 approval: https://github.com/tc39/ecma402/blob/master/meetings/notes-2023-11-16.md#hours-numeric-w-0-in-minutes-and-non-0-in-seconds-cause-strange-output-170

2023-11-28: This PR achieved TC39-TG1 consensus.


Issue #40 - fix maven-antrun-plugin build failure

closes #40

Looking.

Started the process to commit first in internal google repo, that will then do the merge.


Fix databricks for 3.1.1

This fixes #2628
I got through about 90% of the python tests before databricks timed out, so I am going to rerun them in parallel with this PR.

build

build

build

The python tests all passed on databricks 8.2 when I ran them just now.