On Mon, Dec 13, 2021 at 5:50 PM Michael Catanzaro <mcatanzaro(a)gnome.org> wrote:
> On Mon, Dec 13 2021 at 05:45:45 PM -0500, Chris Murphy
> <lists(a)colorremedies.com> wrote:
> > But I don't know what's
> > responsible for creating the /etc/resolv.conf symlink in the two
> > installation methods.
> Until three days ago, the answer was systemd package scriptlet. There's
> absolutely nothing Server-specific there. Maybe just bad script
> ordering luck?
> There is some good news: the "Enforce authselect configuration
> consistency" change is obsoleting all of the current fragile scriptlets
> and should make everything way more robust. See e.g.:
> So I would not invest too much effort into debugging this except in
> rawhide, because everything is very different in rawhide. It should be
> a lot more robust and I wouldn't be surprised if it fixes this issue.
Filed this against distribution and I'll propose it as a Fedora 36
beta blocker so we don't forget about it.
Again, for everyone's convenience, a brief summary of our IRC meeting right here
For greater details see meetbot
Full log: https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-...
=== Follow up actions ===
action: mowest and pboyHB modify the old SIG page as agreed (2021-12-01,#59) DONE
action: mowest and pboyHB continue to migrate the wiki pages WORK IN PROGRESS
action: eseyman hit hackmd this week and comment on tech spec (2021-12-01,#58) DONE
=== Scheduling for the New Year ===
agreed: Next meeting and first meeting in 2022: Wednesday, January 19 17:00 UTC
action: salimma will prepare am initial list of changes in F36 important for server edition
Discussion about it (and testing activities) on the first meeting in 2022
=== Review updated docs ===
action: pboy will update the reviewer table
We still need a reviewer for item 6: Virtualisation
=== Review current Fedora Server Technical Specification ===
1. action: pboy will modify the section File system according the installation guide. Discussion in February.
2. agreed: Section about roles will be dropped
3. agreed: We start a list of supported capabilities / functions and discuss on mailing list and pagure
=== Meeting planning ===
greed: At the next meeting in January we will discuss the topics in the order listed:
1. Using Ansible to install and configure Wildfly
2. Preparing Fedora 36 release
This is a post where I suggest work without any commitment to helping. I'm
I'm trying to help someone here:
... where they're trying to set up an NFS/Samba share using Cockpit. That
seems like it _should_ be easy. Now, this particular person is new and
there's some basic concepts to work on first, but... also, it turns out
Cockpit doesn't actually have an included tool for doing that. This kind of
surprises me, but is also the kind of thing I just don't know because I'm
not a working sysadmin anymore. (I kind of miss it sometimes....)
I talked to Stephen Gallagher and this is something he was looking at but
doesn't have time for. There is a third-party add-on
https://github.com/45Drives/cockpit-file-sharing which looks pretty great,
but is specifically made for 45Drives, and may be difficult to generalize
and package for Fedora Server.
But that seems _really_ worth doing. Anyone interested in taking that on?
Fedora Project Leader
if I remember correctly, with the switch to systemd-resolved in F33, the file /etc/resolve.conf is no longer managed by NetworkManager. It is replaced by a link to /run/systemd/resolve/stub-resolv.conf. On my F34 production systems this is indeed the way it is.
While updating our documentation to F35 I performed several Fedora Server test installations with everything as default and noticed, that /etc/resolve.conf is again a file and managed by NetworkManager. Systemd-resolved is up and running and responds to DNS queries.
The resolvectl command says "resolv.conf mode: foreign“ (I take it as NetworkManager) instead of „stub“ as my F34 systems.
Did I miss something? And is there a reason?
Any information appreciated.
The meeting is scheduled:
Fedora Server IRC meeting Wednesday, December 15 17:00 ==UTC==
Please, check your local time using date -d '2021-11-17 17:00UTC‘
According to my notes we have to discuss topics we had to skip last meeting. Before those extensive topics, we should deal with 2 topics that require only a short amount of time. Nevertheless, any additional suggestions are welcome!
== Agenda ==
1. = Follow up actions =
2. = Scheduling for the New Year =
(max. 5 mins!, just agree about the schedule)
3. = Review updated docs =
(max. 10 mins if possible, we need reviewer for 3 articles)
4. = Review current Fedora Server Technical Specification =
Commentable version at hackmd.io: https://hackmd.io/qBGmKuZPQ5OloAec3_Nh3w
5. = Using Ansible to install and configure Wildfly =
* This meeting is our last one this year
* We should skip the first Wednesday in January 22 (i.e. skip the January 5)
* Next meeting and first meeting in 2022: Wednesday, January 19 17:00 UTC
* Then we continue in a two-week rhythm until June.
* Then at the end of June there is a 3-week gap again.