Puppet Community

in the beaker debug output, do you see how it configures the resolv.conf

and you can inspect the network with the virtualbox gui

<https://github.com/voxpupuli/puppet_metadata/pull/82>

well, it actually works _before_ the resolve.conf changes, but I cannot find what changes it is making that differ

like all are able to yum/apt install puppet-agent

but by the time it gets to the apply that mimics the module, it breaks

resolv.conf hosts, facter, all look correct

dns only on the 2nd and 3rd hosts in vbox, not the first nor on my laptop

<@U114TKH5M>’s haiku reminded of this. :slightly_smiling_face:

I would spin up the VMs and then inspect with vagrant/virtualbox to figure out the differences. then check beaker/beaker-vagrant for the relevant pieces that configure this

not necessarily. you might be screwing routing table to your resolver

there's resolv.conf but also systemd-resolver and i forget what it is but something else tells a system what order to check hosts vs dns

i mean i would find it unlikely to have changed but it's always DNS

• first (working) host: centos-7
• 2nd (broken) host: identical version centos-7 box
• 3rd (broken) ubuntu 18

or some difference that looks completely irrelevant

I normally do
```    vb.customize ["modifyvm", :id, "--natdnsproxy1", "off"]
    vb.customize ["modifyvm", :id, "--natdnshostresolver1", "off"]```

I'll look at current values first. Thanks

the rub is that they work prior during all the boilerplate, only start failing in the module apply.

well, bisecting has indeed zeroed in on the commit, but it is a big conglomerate commit that has to be all-or-nothing to not break, so I don't know how I'm gonna chunk it into smaller parts... :thinking_face:

check if all VMs are on the same virtualbox network, have the same resolver, check if they have any firewall rules, check if the host has any rules

when i want to do a first forge release for puppet-k8s. do we start with v0.0.1 or v1.0.0 for voxpupuli modules?

`rake release:prepare`  is the new way to go? it suggests v0.0.1. the releases docu seems outdated. how do i change it to do a 1.0.0?

ok, this wasn't it :thonk:
```rake aborted!
NoMethodError: undefined method `future_release=' for GCGConfig:Class
Did you mean?  future_release```

stupid me.... metadata.json. istn only metadata but has so manny functions :smile: