Hi Benjamin, Qian,
I am just trying to stress that this is not default behaviour and thus not expected. Major implementations like apache httpd and sysctl are ignoring other extensions. To me it is irrelevant if this currently documented or not, or easy to adapt to. One should follow 'standards' as much as possible. -----Original Message----- Subject: Re: Is it not time the cni configuration dir loads only specific extensions? Hi Marc, I guess Qian was confused by your email body containing no question. To answer the question from the email’s subject: > Is it not time the cni configuration dir loads only specific extensions? I would say, no, it is not. The current behavior is documented, pretty simple for both users and implementors (e.g., no need to handle multiple possible extensions), and not unusual since a non-vanishing number of tools would also try to load all files from a specific directory. Additionally, changing what files would be considered would be a breaking change for little benefit. Cheers, Benjamin > On Jul 29, 2019, at 9:43 AM, Marc Roos <[email protected]> wrote: > > > I know there is something wrong with > 91-podman-bridge-not.conflist.bak, > that is why I put the .bak extension. > > > > > > > -----Original Message----- > From: Qian Zhang [mailto:[email protected]] > Sent: maandag 29 juli 2019 4:15 > To: user > Subject: Re: Is it not time the cni configuration dir loads only > specific extensions? > > Can you please check the file > `/etc/mesos-cni/91-podman-bridge-not.conflist.bak`? It seems that file > does not have the required field `type`. > > > Regards, > Qian Zhang > > > On Sun, Jul 28, 2019 at 1:04 AM Marc Roos <[email protected]> > wrote: > > > > > mesos-slave.m03.invalid-user.log.WARNING.20190726-124341.9083:E0726 > > 12:43:41.716598 9083 cni.cpp:330] Failed to parse CNI network > configuration file > '/etc/mesos-cni/91-podman-bridge-not.conflist.bak': > Protobuf parse failed: Missing required fields: type > > > > > >
