Appreciate the response.
No, I hadn't figured out why the upgrade failed from 27 to 28 which was why I
went ahead and tried this. I am assuming that they are somehow caused by the
same underlying issue even though they don't respond exactly the same.
I am really at a loss at how to resolve it.
Doug
From: Dusty Mabe <du...@dustymabe.com>
To: atomic-devel@projectatomic.io
Sent: Friday, March 22, 2019 1:19 AM
Subject: Re: [atomic-devel] Rebase Fedora Atomic 27 > 29 fails to boot
On 3/21/19 1:17 PM, Dusty Mabe wrote:
>
>
> On 3/20/19 11:41 AM, Doug Campbell wrote:
>> Currently running Fedora Atomic 27.153
>>
>> Following instructions at:
>> http://www.projectatomic.io/blog/2018/10/fedora-atomic-28-to-29-upgrade/ to
>> upgrade to version 29.
>>
>> Upon reboot everything is fine until I see:
>>
>> (1 of 2) A start job is running for Network Manager (3min 6s / 1min 36s)
>> [timestmp] systemd-journal[990]: Failed to send WATCHDOG=1 notification
>> message: Connection refused
>> [timestmp] systemd-journal[990]: Failed to send WATCHDOG=1 notification
>> message: Transport endpoint is not connected
>>
>> The last line continues to repeat periodically for as long as I would wait.
>>
>> I had to reboot and switch back to version 27.
>>
>> Please advise how to fix this and upgrade to version 29.
>>
>
> I have not seen that. You may try to go to f28 first and then to f29 and see
> if that helps.
>
Actually just saw your previous email about upgrading from 27 to 28. Did you
ever figure out the
issue there?
Dusty
