10:19 p.m.
Hi All,
My Fedora Test Virtual Machine (qemu-kvm) won't upgrade
to 33 from, 32. I say it is upgrading then boot almost
immediately back into FC32.
# rpm --rebuilddb
# rpm -Va --nofiles --nodigest
# dnf --enablerepo=* update --refresh --disablerepo=brave*
# dnf install python3-dnf-plugin-system-upgrade
# dnf system-upgrade download --refresh --releasever=33 --allowerasing
--best --disablerepo=brave*
# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-33-primary
# dnf system-upgrade -v reboot --debugsolver
And I forgot how to use --debugsolver to see what is
going wrong.
-T
5:37 a.m.
On 2020-10-31 00:07, Samuel Sieb wrote:
On 10/30/20 8:19 PM, ToddAndMargo via users wrote:
> Hi All,
>
> My Fedora Test Virtual Machine (qemu-kvm) won't upgrade
> to 33 from, 32. I say it is upgrading then boot almost
> immediately back into FC32.
Did you check the journal to see what went wrong?
Forgot how :'(
5:40 a.m.
On Sat, Oct 31, 2020 at 5:38 AM ToddAndMargo via users <
users(a)lists.fedoraproject.org> wrote:
On 2020-10-31 00:07, Samuel Sieb wrote:
> On 10/30/20 8:19 PM, ToddAndMargo via users wrote:
>> Hi All,
>>
>> My Fedora Test Virtual Machine (qemu-kvm) won't upgrade
>> to 33 from, 32. I say it is upgrading then boot almost
>> immediately back into FC32.
>
> Did you check the journal to see what went wrong?
Forgot how :'(
Assuming the previous boot is the one you want to examine (as root or via
sudo)
# journalctl -b -1
Thanks,
Richard
6:24 a.m.
On 31/10/2020 18:37, ToddAndMargo via users wrote:
On 2020-10-31 00:07, Samuel Sieb wrote:
> On 10/30/20 8:19 PM, ToddAndMargo via users wrote:
>> Hi All,
>>
>> My Fedora Test Virtual Machine (qemu-kvm) won't upgrade
>> to 33 from, 32. I say it is upgrading then boot almost
>> immediately back into FC32.
>
> Did you check the journal to see what went wrong?
Forgot how :'(
Also have a look through the upgrade log
dnf system-upgrade log
---
The key to getting good answers is to ask good questions.
2:19 p.m.
On 2020-10-31 04:24, Ed Greshko wrote:
dnf system-upgrade log
# df -kPT
Filesystem Type 1024-blocks Used Available Capacity Mounted on
devtmpfs devtmpfs 995088 0 995088 0% /dev
tmpfs tmpfs 1013564 0 1013564 0% /dev/shm
tmpfs tmpfs 1013564 1112 1012452 1% /run
/dev/vda3 ext4 17413904 8716672 7789612 53% /
tmpfs tmpfs 1013564 28 1013536 1% /tmp
/dev/vda1 ext4 999320 249792 680716 27% /boot
tmpfs tmpfs 202712 24 202688 1%
/run/user/1000
# dnf system-upgrade log
The following boots appear to contain upgrade logs:
1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28
2 / a7b5ab0d772d49f5bc4bece971e3e34f: 2018-09-28 11:26:59 28→29
3 / af5f137e166b43f29a0b569932d59c5b: 2019-04-30 19:33:19 29→30
4 / b906a0cf864c4d2ab51fac91b984a43b: 2019-11-01 21:52:50 30→31
5 / 996e59b22f50425d99b7392c3a1ba11c: 2020-04-18 11:05:18 31→32
6 / 0e48343cf87540db8aa7d984b9c804fd: 2020-10-30 20:08:59 31→32
7 / a8a091e4bb0345108199e0db1619f306: 2020-10-30 20:13:51 31→32
8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
# cat /etc/redhat-release
Fedora release 32 (Thirty Two)
Well, lets try -1 anyway
Nov 01 12:07:52 localhost.localdomain python3[537]: Starting system
upgrade. This will take a while.
Nov 01 12:07:52 localhost.localdomain dnf[537]: Unable to match package:
NetworkManager-fortisslvpn-1.3.90-7.fc31.x86_64
Nov 01 12:07:52 localhost.localdomain dnf[537]: Unable to match package:
NetworkManager-fortisslvpn-gnome-1.3.90-7.fc31.x86_64
<100's of them>
...
Nov 01 12:08:05 localhost.localdomain dnf[537]: Error: Unable to match
some of packages
Nov 01 12:08:05 localhost.localdomain systemd[1]:
dnf-system-upgrade.service: Main process exited, code=exited,
status=1/FAILURE
Nov 01 12:08:05 localhost.localdomain systemd[1]:
dnf-system-upgrade.service: Failed with result 'exit-code'.
Nov 01 12:08:05 localhost.localdomain systemd[1]: Failed to start System
Upgrade using DNF.
Nov 01 12:08:05 localhost.localdomain systemd[1]:
dnf-system-upgrade.service: Triggering OnFailure= dependencies.
Nov 01 12:08:05 localhost.localdomain systemd[1]:
dnf-system-upgrade.service: Consumed 14.522s CPU time.
Nov 01 12:08:05 localhost.localdomain systemd[1]: Reached target Offline
System Update.
3:34 p.m.
New subject: [Solved] FC33 won't upgrade
On 2020-11-01 12:19, ToddAndMargo via users wrote:
On 2020-10-31 04:24, Ed Greshko wrote:
> dnf system-upgrade log
# df -kPT
Filesystem Type 1024-blocks Used Available Capacity Mounted on
devtmpfs devtmpfs 995088 0 995088 0% /dev
tmpfs tmpfs 1013564 0 1013564 0% /dev/shm
tmpfs tmpfs 1013564 1112 1012452 1% /run
/dev/vda3 ext4 17413904 8716672 7789612 53% /
tmpfs tmpfs 1013564 28 1013536 1% /tmp
/dev/vda1 ext4 999320 249792 680716 27% /boot
tmpfs tmpfs 202712 24 202688 1%
/run/user/1000
# dnf system-upgrade log
The following boots appear to contain upgrade logs:
1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28
2 / a7b5ab0d772d49f5bc4bece971e3e34f: 2018-09-28 11:26:59 28→29
3 / af5f137e166b43f29a0b569932d59c5b: 2019-04-30 19:33:19 29→30
4 / b906a0cf864c4d2ab51fac91b984a43b: 2019-11-01 21:52:50 30→31
5 / 996e59b22f50425d99b7392c3a1ba11c: 2020-04-18 11:05:18 31→32
6 / 0e48343cf87540db8aa7d984b9c804fd: 2020-10-30 20:08:59 31→32
7 / a8a091e4bb0345108199e0db1619f306: 2020-10-30 20:13:51 31→32
8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
# cat /etc/redhat-release
Fedora release 32 (Thirty Two)
Well, lets try -1 anyway
Nov 01 12:07:52 localhost.localdomain python3[537]: Starting system
upgrade. This will take a while.
Nov 01 12:07:52 localhost.localdomain dnf[537]: Unable to match package:
NetworkManager-fortisslvpn-1.3.90-7.fc31.x86_64
Nov 01 12:07:52 localhost.localdomain dnf[537]: Unable to match package:
NetworkManager-fortisslvpn-gnome-1.3.90-7.fc31.x86_64
<100's of them>
...
Nov 01 12:08:05 localhost.localdomain dnf[537]: Error: Unable to match
some of packages
Nov 01 12:08:05 localhost.localdomain systemd[1]:
dnf-system-upgrade.service: Main process exited, code=exited,
status=1/FAILURE
Nov 01 12:08:05 localhost.localdomain systemd[1]:
dnf-system-upgrade.service: Failed with result 'exit-code'.
Nov 01 12:08:05 localhost.localdomain systemd[1]: Failed to start System
Upgrade using DNF.
Nov 01 12:08:05 localhost.localdomain systemd[1]:
dnf-system-upgrade.service: Triggering OnFailure= dependencies.
Nov 01 12:08:05 localhost.localdomain systemd[1]:
dnf-system-upgrade.service: Consumed 14.522s CPU time.
Nov 01 12:08:05 localhost.localdomain systemd[1]: Reached target Offline
System Update.
Solved:
I did a
# dnf system-upgrade clean
# dnf --refresh upgrade
and started over.
Thank you all for the help!
-T
3:39 p.m.
New subject: [Solved] FC33 won't upgrade
On 11/1/20 1:34 PM, ToddAndMargo via users wrote:
Solved:
I did a
# dnf system-upgrade clean
# dnf --refresh upgrade
and started over.
It does ask if you fully updated before starting. :-)
I generally update at least all of dnf and systemd before doing a
system-upgrade and I haven't had any problems yet.
3:41 p.m.
New subject: [Solved] FC33 won't upgrade
On 2020-11-01 13:39, Samuel Sieb wrote:
On 11/1/20 1:34 PM, ToddAndMargo via users wrote:
> Solved:
>
> I did a
>
> # dnf system-upgrade clean
> # dnf --refresh upgrade
>
> and started over.
It does ask if you fully updated before starting. :-)
I generally update at least all of dnf and systemd before doing a
system-upgrade and I haven't had any problems yet.
I DID !!! :'(
One down. Three to go.
I will run the VM for a while to make sure I am happy
3:41 p.m.
On 02/11/2020 04:19, ToddAndMargo via users wrote:
# dnf system-upgrade log
The following boots appear to contain upgrade logs:
1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28
2 / a7b5ab0d772d49f5bc4bece971e3e34f: 2018-09-28 11:26:59 28→29
3 / af5f137e166b43f29a0b569932d59c5b: 2019-04-30 19:33:19 29→30
4 / b906a0cf864c4d2ab51fac91b984a43b: 2019-11-01 21:52:50 30→31
5 / 996e59b22f50425d99b7392c3a1ba11c: 2020-04-18 11:05:18 31→32
6 / 0e48343cf87540db8aa7d984b9c804fd: 2020-10-30 20:08:59 31→32
7 / a8a091e4bb0345108199e0db1619f306: 2020-10-30 20:13:51 31→32
8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
Well #8 is what you want to look at. "man dnf" will help you choose it.
But, something odd. You say you want to go to F33. But your entry shows
8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32 <------------
While one would expect
2 / b1f88aab19d4444c9deb9aef2c8a2045: 2020-10-31 14:33:47 32→33 <-----------
---
The key to getting good answers is to ask good questions.
3:44 p.m.
On 2020-11-01 13:41, Ed Greshko wrote:
On 02/11/2020 04:19, ToddAndMargo via users wrote:
> # dnf system-upgrade log
> The following boots appear to contain upgrade logs:
> 1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28
> 2 / a7b5ab0d772d49f5bc4bece971e3e34f: 2018-09-28 11:26:59 28→29
> 3 / af5f137e166b43f29a0b569932d59c5b: 2019-04-30 19:33:19 29→30
> 4 / b906a0cf864c4d2ab51fac91b984a43b: 2019-11-01 21:52:50 30→31
> 5 / 996e59b22f50425d99b7392c3a1ba11c: 2020-04-18 11:05:18 31→32
> 6 / 0e48343cf87540db8aa7d984b9c804fd: 2020-10-30 20:08:59 31→32
> 7 / a8a091e4bb0345108199e0db1619f306: 2020-10-30 20:13:51 31→32
> 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
Well #8 is what you want to look at. "man dnf" will help you choose it.
But, something odd. You say you want to go to F33. But your entry shows
8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
<------------
While one would expect
2 / b1f88aab19d4444c9deb9aef2c8a2045: 2020-10-31 14:33:47 32→33
<-----------
I thought that was weird too. -1 did work and
showed the error.
3:49 p.m.
On 02/11/2020 05:44, ToddAndMargo via users wrote:
On 2020-11-01 13:41, Ed Greshko wrote:
> On 02/11/2020 04:19, ToddAndMargo via users wrote:
>> # dnf system-upgrade log
>> The following boots appear to contain upgrade logs:
>> 1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28
>> 2 / a7b5ab0d772d49f5bc4bece971e3e34f: 2018-09-28 11:26:59 28→29
>> 3 / af5f137e166b43f29a0b569932d59c5b: 2019-04-30 19:33:19 29→30
>> 4 / b906a0cf864c4d2ab51fac91b984a43b: 2019-11-01 21:52:50 30→31
>> 5 / 996e59b22f50425d99b7392c3a1ba11c: 2020-04-18 11:05:18 31→32
>> 6 / 0e48343cf87540db8aa7d984b9c804fd: 2020-10-30 20:08:59 31→32
>> 7 / a8a091e4bb0345108199e0db1619f306: 2020-10-30 20:13:51 31→32
>> 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
>
> Well #8 is what you want to look at. "man dnf" will help you choose it.
>
> But, something odd. You say you want to go to F33. But your entry shows
>
> 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32 <------------
>
> While one would expect
>
> 2 / b1f88aab19d4444c9deb9aef2c8a2045: 2020-10-31 14:33:47 32→33 <-----------
I thought that was weird too. -1 did work and
showed the error.
You are mixing 2 things?
journalctl isn't upgrade-log
---
The key to getting good answers is to ask good questions.
4:09 p.m.
On 2020-11-01 13:49, Ed Greshko wrote:
On 02/11/2020 05:44, ToddAndMargo via users wrote:
> On 2020-11-01 13:41, Ed Greshko wrote:
>> On 02/11/2020 04:19, ToddAndMargo via users wrote:
>>> # dnf system-upgrade log
>>> The following boots appear to contain upgrade logs:
>>> 1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28
>>> 2 / a7b5ab0d772d49f5bc4bece971e3e34f: 2018-09-28 11:26:59 28→29
>>> 3 / af5f137e166b43f29a0b569932d59c5b: 2019-04-30 19:33:19 29→30
>>> 4 / b906a0cf864c4d2ab51fac91b984a43b: 2019-11-01 21:52:50 30→31
>>> 5 / 996e59b22f50425d99b7392c3a1ba11c: 2020-04-18 11:05:18 31→32
>>> 6 / 0e48343cf87540db8aa7d984b9c804fd: 2020-10-30 20:08:59 31→32
>>> 7 / a8a091e4bb0345108199e0db1619f306: 2020-10-30 20:13:51 31→32
>>> 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
>>
>> Well #8 is what you want to look at. "man dnf" will help you choose
it.
>>
>> But, something odd. You say you want to go to F33. But your entry
>> shows
>>
>> 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
>> <------------
>>
>> While one would expect
>>
>> 2 / b1f88aab19d4444c9deb9aef2c8a2045: 2020-10-31 14:33:47 32→33
>> <-----------
>
>
> I thought that was weird too. -1 did work and
> showed the error.
You are mixing 2 things?
journalctl isn't upgrade-log
Explain how
4:18 p.m.
On 11/1/20 1:49 PM, Ed Greshko wrote:
On 02/11/2020 05:44, ToddAndMargo via users wrote:
> On 2020-11-01 13:41, Ed Greshko wrote:
>> On 02/11/2020 04:19, ToddAndMargo via users wrote:
>>> # dnf system-upgrade log
>>> The following boots appear to contain upgrade logs:
>>> 1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28
>>> 2 / a7b5ab0d772d49f5bc4bece971e3e34f: 2018-09-28 11:26:59 28→29
>>> 3 / af5f137e166b43f29a0b569932d59c5b: 2019-04-30 19:33:19 29→30
>>> 4 / b906a0cf864c4d2ab51fac91b984a43b: 2019-11-01 21:52:50 30→31
>>> 5 / 996e59b22f50425d99b7392c3a1ba11c: 2020-04-18 11:05:18 31→32
>>> 6 / 0e48343cf87540db8aa7d984b9c804fd: 2020-10-30 20:08:59 31→32
>>> 7 / a8a091e4bb0345108199e0db1619f306: 2020-10-30 20:13:51 31→32
>>> 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
>>
>> Well #8 is what you want to look at. "man dnf" will help you choose
it.
>>
>> But, something odd. You say you want to go to F33. But your entry
>> shows
>>
>> 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
>> <------------
>>
>> While one would expect
>>
>> 2 / b1f88aab19d4444c9deb9aef2c8a2045: 2020-10-31 14:33:47 32→33
>> <-----------
>
>
> I thought that was weird too. -1 did work and
> showed the error.
You are mixing 2 things?
journalctl isn't upgrade-log
He used the "system-upgrade log" command to get the list, so I assume he
used the same one to see the log. "-1" is the correct option to see the
most recent upgrade log. That doesn't explain why there's no 32->33 in
the list, but it worked anyway.
4:36 p.m.
On 02/11/2020 06:18, Samuel Sieb wrote:
On 11/1/20 1:49 PM, Ed Greshko wrote:
> On 02/11/2020 05:44, ToddAndMargo via users wrote:
>> On 2020-11-01 13:41, Ed Greshko wrote:
>>> On 02/11/2020 04:19, ToddAndMargo via users wrote:
>>>> # dnf system-upgrade log
>>>> The following boots appear to contain upgrade logs:
>>>> 1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28
>>>> 2 / a7b5ab0d772d49f5bc4bece971e3e34f: 2018-09-28 11:26:59 28→29
>>>> 3 / af5f137e166b43f29a0b569932d59c5b: 2019-04-30 19:33:19 29→30
>>>> 4 / b906a0cf864c4d2ab51fac91b984a43b: 2019-11-01 21:52:50 30→31
>>>> 5 / 996e59b22f50425d99b7392c3a1ba11c: 2020-04-18 11:05:18 31→32
>>>> 6 / 0e48343cf87540db8aa7d984b9c804fd: 2020-10-30 20:08:59 31→32
>>>> 7 / a8a091e4bb0345108199e0db1619f306: 2020-10-30 20:13:51 31→32
>>>> 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
>>>
>>> Well #8 is what you want to look at. "man dnf" will help you
choose it.
>>>
>>> But, something odd. You say you want to go to F33. But your entry shows
>>>
>>> 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
<------------
>>>
>>> While one would expect
>>>
>>> 2 / b1f88aab19d4444c9deb9aef2c8a2045: 2020-10-31 14:33:47 32→33
<-----------
>>
>>
>> I thought that was weird too. -1 did work and
>> showed the error.
>
> You are mixing 2 things?
>
> journalctl isn't upgrade-log
He used the "system-upgrade log" command to get the list, so I assume he used
the same one to see the log. "-1" is the correct option to see the most recent
upgrade log. That doesn't explain why there's no 32->33 in the list, but it
worked anyway.
Well, I don't like to "assume" anything. Well, except that you mentioned he
should look at the
"journal" it wasn't clear to me that he wasn't mixing things. Thus the
"?".
As always, I find it helpful if folks include the actual command they use to prevent
misunderstandings.
dnf system-upgrade log --number=-1
Would have been nice to see.
---
The key to getting good answers is to ask good questions.
5:51 p.m.
On 2020-11-01 15:41, ToddAndMargo via users wrote:
On 2020-11-01 14:18, Samuel Sieb wrote:
> That doesn't explain why there's no 32->33 in
> the list, but it worked anyway.
> 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
Or why the date and time were for the failed upgrade
And after the successful upgrade (9):
# dnf system-upgrade log
The following boots appear to contain upgrade logs:
1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28
2 / a7b5ab0d772d49f5bc4bece971e3e34f: 2018-09-28 11:26:59 28→29
3 / af5f137e166b43f29a0b569932d59c5b: 2019-04-30 19:33:19 29→30
4 / b906a0cf864c4d2ab51fac91b984a43b: 2019-11-01 21:52:50 30→31
5 / 996e59b22f50425d99b7392c3a1ba11c: 2020-04-18 11:05:18 31→32
6 / 0e48343cf87540db8aa7d984b9c804fd: 2020-10-30 20:08:59 31→32
7 / a8a091e4bb0345108199e0db1619f306: 2020-10-30 20:13:51 31→32
8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
9 / 8c514886afa4457e89243105ed19909e: 2020-11-01 13:18:46 32→33
1270
days inactive
1271
days old
16 comments
4 participants
participants (4)
-
Ed Greshko -
Richard Shaw -
Samuel Sieb -
ToddAndMargo