nmcli, nmtui, nm-connection-editor, nmstatectl ...

nmcli, nmtui, nm-connection-editor, nmstatectl ...

nmstatectl uses yaml

but it is back to an all in one config in a file... and I don't know if it can handle setting up multiple routing tables, ip match rules, etc.

and... it is rather detailed

[root@pillan09 system-connections]# nmstatectl show  | wc -l
[2022-11-22T15:58:42Z INFO  nmstate::nispor::show] Got unsupported interface lo type Loopback
[2022-11-22T15:58:42Z INFO  nmstate::nm::show] Got unsupported interface type generic: lo, ignoring
936

I think there 3-4 possible ways forward. 1) drop files under /etc/NetworkManager/system-connections/ -- this will work for interfaces, I still don't know about setting up routes with drop-in files 2) try to write out a yaml config and invoke

nmstatectl

. This does appear to support setting up multiple routing tables: https://nmstate.io/examples.html#route 3) try wrap

nmcli

with a provider and pass everything as cli flags 4) similar to 3 but try to bypass

nmcli

and talk to NM directly via d-bus using something like https://rubygems.org/gems/ruby-dbus

@ananace which way did you go?

@jhoblitt - Got a bunch of types and providers that build the nmconnection ini-files, which then call nmcli to handle the reloading and bringing up/down when necessary

@Ananance It would be great if you can share what you have. I am about to go on vacation until January but I'm going to have to start work on a "final" solution then.

I'm rather pissed about the updown compat scripts being broken under EL9

I'm rather pissed about the updown compat scripts being broken under EL9

This message was deleted.

Hi, I was searching for this exact error and noticed you ran into the same problem I just did. So in case you are still inconvenienced by this: This is a Puppet Debugger problem, caused by this Bolt PR (released in 3.23.0). That patch rearranged the API for the

Bolt::PuppetDB::Config

class, including removing the

load_config

method. I just submitted a PR to fix it at https://github.com/nwops/puppet-debugger/pull/74

Hi, I was searching for this exact error and noticed you ran into the same problem I just did. So in case you are still inconvenienced by this: This is a Puppet Debugger problem, caused by this Bolt PR (released in 3.23.0). That patch rearranged the API for the

Bolt::PuppetDB::Config

class, including removing the

load_config

method. I just submitted a PR to fix it at https://github.com/nwops/puppet-debugger/pull/74

ewoud: OT: As a RedHatter, do you know why all the more recent ubi image tags have disappeared from here? https://catalog.redhat.com/software/containers/ubi8/ubi-minimal/5c359a62bed8bd75a2c3fba8

This message was deleted.

afisher: no, I do not know

no worries. I think it's just a confusing search interface and the image I was actually looking for was renamed and is https://catalog.redhat.com/software/containers/ubi8-minimal/5c64772edd19c77a158ea216

afisher: https://quay.io/repository/app-sre/ubi8-ubi-minimal has more recent tags

oh yes, that interface is horrible and finding what you're after is hard

can I get a review for https://github.com/voxpupuli/beaker/pull/1759

@Alex Fisher I think they announced somewhere docker hub is deprecated (for ubi)

@Mila has left the channel

can I get a review for https://github.com/voxpupuli/puppet-augeasproviders_postgresql/pull/13

Morning all

@bastelfreak this are only references to already merged things, and these things are only "meta"-changes for tested plattforms?

this are only references to already merged things, and these things are only "meta"-changes for tested plattforms?

@bastelfreak this are only references to already merged things, and these things are only "meta"-changes for tested plattforms?

we didnt do any real code changes, yes. the module got migrated to us and this is the first release in our namespace