Doug Lasa

Hi @parth-gr ! Has there been any solution found for this issue? We recently upgraded a few staging clusters from rook 1.14.10/ceph 18.2.4 to rook 1.15.8/ceph 18.2.4. After the upgrade,...

## We were asked for the following: - `underlying hardware (network devices / virt environments etc.)` - Bare metal - Problematic Flatcar OS 3975.2.1 & 3975.2.2 - Working Flatcar OS...

@jepio # Please see below upgrade process and results: * 3975.2.1 - Reboot X 3 - Have `churn` on all 3 reboots - No `system mac address` on 2nd Bond0...

@jepio Please see the information you requested below: ## 3975.2.1 - `networkctl list` ``` IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp65s0f0np0 ether enslaved configured 3...

@ader1990 ## First Question ``` Hello, this looks to be a concurrency issue between the unit that enforces/creates the bond and the unit that enforces the /etc/systemd/network/98-bond-mac.link. Can you give...

@ader1990 @sayanchowdhury We upgraded out test box from 3975.2.1 to 4230.0.0. Unfortunately, the `churn` problem still exists: ``` 1st boot into 4230.0.0, after the upgrade: churn 2nd reboot: churn 3rd...

Hi @t-lo This particular configuration has worked for other Flatcar versions and node spin ups.

Hi there @t-lo ! I apologize for the long response time but i did not actually hit `comment` on my response. This is a good thing though because I did...