Hey all,
This one is a bit of a long shot so I'm not too optimistic about
finding any resolution, but figured I'd try.
In Fedora CoreOS we've seen a mount unit get stuck and the system will
just stay there forever (in the initramfs). Does this sound crazy?
Anyone seen something similar before?
On 5/22/22 08:35, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, May 20, 2022 at 03:51:58PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
>> On Thu, May 19, 2022 at 01:42:43PM +0200, Daan De Meyer wrote:
>>>> Am 19.05.22 um 05:32 schrieb Dusty Mabe:
>>>>>
I'm requesting help to try to find a problematic commit between
v251-rc2..v251-rc3.
We have a test in Fedora CoreOS [1] that tests luks and this test started
failing in our
rawhide stream with the introduction of 251-rc3. Reverting back to 251-rc2
makes the
failing test go away. I briefly
On 5/12/22 13:36, Dan Streetman wrote:
> On Thu, May 12, 2022 at 11:11 AM Thomas Haller wrote:
>>
>> Hi Zbyszek,
>>
>>
>>
>> I must say, I personally don't care too much. NetworkManager is fine
>> either way.
>>
>> There is however the problem about RHEL8/9, which patches this
>> downstream. I
On 5/12/22 12:43, Lennart Poettering wrote:
> On Mo, 09.05.22 22:37, Dusty Mabe (du...@dustymabe.com) wrote:
>
>>> This is true. But one can just as well argument that with
>>> MACAddressPolicy=persistent the address is even more predictable. If
>>> you know th
On 5/9/22 13:27, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, May 09, 2022 at 03:57:21PM +0200, Lennart Poettering wrote:
>> On Mo, 09.05.22 11:23, Thomas Haller (thal...@redhat.com) wrote:
>>
>>> Hi everybody,
>>>
>>> this email is for discussing MACAddressPolicy=persistent in
>>>
