Duplicate IPV4 address on network -- headless server
by John W. Himpel
All,
I just finished testing the condition where I booted F40 Server having
previously used NetworkManager to force the interface to use the ipv4
address already assigned to another ho
I did not see any indication on the console that an duplicate ipv4
address had been detected. However in the journal there were several
messages in the journal from NetworkManager indicating there was an
issue with a duplicate ipv4 address already active on the network.
Issuing the command nmcli device status, shows the device as
disconnected.
I have not tried this with an active GUI on the host trying to add the
duplicate ipv4 address.
1 month, 1 week
Short info about our April 03 meeting
by Peter Boy
Again, for everyone's convenience, a brief summary of our IRC meeting right here.
== Essentials ==
=== Review Installation Media ===
The discussion revealed obvious inconsistencies between the ways of creating our various installation media that have evolved over time. All of this is difficult to deal with in a matrix discussion.
Therefore:
AGREED: An additional meeting out of turn in the Matrix Sever room exclusively to discuss the Review Installation Media topic.
==== Wednesday, April 10, 17:00 UTC ====
(same time as our regular meetings)
ACTION: pboy will prepare the room and provide a test opportunity so that everyone can try out their equipment beforehand and make sure that the audio and video work.
==== Tuesday, April 9, 17:00 UTC ====
in Matrix Server room.
=== Revisiting Server installation media naming convention ===
The online/offline proposal is welcomed, but the overall solution should be presented more clearly.
A decision will be aimed for by mid-May at the latest so that there is sufficient time for implementation.
== Summary: ==
https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-0...
== Full log: ==
https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-0...
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
1 month, 1 week
Agenda Items on 2024-04-03 17:00 ==UTC== meeting
by Peter Boy
The upcoming meeting will be held on
==========================================================================
Fedora Server MATRIX meeting Wednesday, Apr 03 17:00 ==UTC==
https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=c...
==========================================================================
Please, check your local time using date -d '2024-04-03 17:00UTC'
Unfortunately, I'm "a bit" late again. Sorry for this.
As a reminder
=============
We decided to continue our meetings on MATRIX!
The above link lets you choose which app to use: web browser, elements, and a lot of others, including some CLI tools, and redirects you to the meeting romm.
==== Agenda ====
#link https://pagure.io/fedora-server/report/Meeting
To be able to discuss all topics on the agenda and to prevent us from repeatedly putting off topics that have not been dealt with, we should set time limits for the individual items on the agenda. If we need more time, we should continue on the mailing list.
=== 1. Follow up actions and announcements ===
=== 2. Review installation media ===
!link https://pagure.io/fedora-server/issue/88
!link https://pagure.io/fedora-server/issue/130
!link https://pagure.io/pungi-fedora/blob/main/f/variants-fedora.xml
!link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject....
We have to discuss how to proceed. About 30 mins
=== 3. LVM2 default configuration change
!link https://bugzilla.redhat.com/show_bug.cgi?id=2247872
Mainly informational today. About 5 mins
=== 4. Testing F40 ===
!link https://pagure.io/fedora-server/issue/125
link https://hackmd.io/NtO4O9vRT3a71UMZMkceoA?both
We need to discuss
- the current state of tests
- How to continue moving away from hackmd
=== 5. Revisiting Server installation media naming convention
!https://pagure.io/fedora-server/issue/126
=== 6. Our "story" for F40
!https://pagure.io/fedora-server/issue/101
This includes a Server entry to the Release Notes!
=== 7. Open Floor
For any additions or changes, please reply to this email.
For an overview about current tasks look at:
https://pagure.io/fedora-server/boards/Works%20in%20progress
===== Pending topics for the next meetings =====
=== Revisiting Fedora Server release criteria
!link https://pagure.io/fedora-server/issue/61
=== Using Ansible to install and configure Wildfly
!link https://pagure.io/fedora-server/issue/60
=== Revisiting Server installation media naming convention
!https://pagure.io/fedora-server/issue/126
=== Work program and goals for F40/41 ===
Previous discussion: Fedora Server goal(s) for F39
!link https://pagure.io/fedora-server/issue/102
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
1 month, 2 weeks
Fix variants.xml in compose configs
by Peter Boy
See https://pagure.io/fedora-server/issue/130
I’m wondering about all the <groups> entries. Server is the only variant with those. (And I think we should delete the <arch>armhfp</arch> to make it clear, that Fedora no longer supports armhfp)
My question is, do we still need the groups at all? Isn't everything regulated via Kickstart files?
As far as I could decipher in the generation process, everything begins with a kickstart file
fedora-disk-server.ks
In https://pagure.io/fedora-kickstarts/blob/main/f/fedora-disk-server.ks
Basically it includes fedora-disk-base.ks and that in turn a lot of other kickstart files. And each kickstart file includes/installs a lot of packages or package groups (from comps).
All of these seems to be quite old and could date back to the time before the differentiation into editions.
Wouldn't it be a good first step to systematize the comps files?
One idea is:
fedora-disk-server.ks // base für iso installation media
-- fedora-server-base hw //packages to ensure operability on hardware, kernel, firmware, hw driver, etc
—- fedora-server-base-kvm //packages to ensure operability on KVM virtual machen: kernel—core
—- fedora-server-base-sys //basic universal system: systems, bus, etc. for either hw and vm
—- fedora-server-base-runtime // our minimal generic server packages: ipa, nfs-client, etc.
And and some optional packages/group
We should create these groups as server-specific as possible. Currently, many of the groups used seem to be too general and more suited to Workstation. A lot of stuff is installed that we don't need and don't want.
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
1 month, 2 weeks