qvm-dom0-upgrade fails

[Zrubi]

Hi,

Maybe related to #287

The very first update seems scary - hovewer it is only 'means' there is no updates jet:

[zrubi@dom0 ~]$ sudo qubes-dom0-update --clean
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running command on VM: 'sys-firewall'...
(Note: dnf will complain that the yum command has been deprecated.
This message is safe to ignore.)
Yum command has been deprecated, use dnf instead.
See 'man dnf' and 'man yum2dnf' for more information.

Loaded plugins: yum-qubes-hooks
Cleaning repos: fedora qubes-dom0-current qubes-templates-itl updates
Cleaning up everything
Checking for dom0 updates...
Yum command has been deprecated, use dnf instead.
See 'man dnf' and 'man yum2dnf' for more information.

No new updates available
file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml"
Trying other mirror.

[mig5]

I reproduce this, also does not matter whether sys-firewall is the UpdateVM or any other VM. Issue did not occur for me on 3.0, I think it started when I reinstalled with 3.1.

[mig5]

I reproduce this, also does not matter whether sys-firewall is the UpdateVM or any other VM. Issue did not occur for me on 3.0, I think it started when I reinstalled with 3.1.

[unixninja92]

I'm also having this issue. I'm using a wifi connection. Have not tested with ethernet. This is on 3.1rc2. Internet works fine in personal domain.

[unixninja92]

I'm also having this issue. I'm using a wifi connection. Have not tested with ethernet. This is on 3.1rc2. Internet works fine in personal domain.

[mpalenik-redhat]

Confirmed on fresh install of 3.1rc2 that runs using the grub2 menuentry Qubes, with Xen 4.6.0 and Linux 4.1.13-8.pvops.qubes.x86_64 (without updates).

I would provide more info from my custom.cfg, but there is afaik no way to copy content from dom0 terminal to another VMs (running firefox). The tutorial seems to be outdated (no file matching qubes-clipboard* lies on my /). Shall I file a bug?

I am using a wireless connection as well.

Note that the GUI app Software Updater is also not working. I would pass the screenshot, if it were not so clumsy. The title says [Dom0] No network connection available - Plasma Widgets shell and after clicking on Details < < there is a message cannot refresh cache when offline. Shall I file a separate bug for this?

Also note the command qvm-dom0-upgrade has been renamed to qvm-dom0-update. However, the command in question is qubes-dom0-update, so the title should be renamed accordingly.

[mpalenik-redhat]

Confirmed on fresh install of 3.1rc2 that runs using the grub2 menuentry Qubes, with Xen 4.6.0 and Linux 4.1.13-8.pvops.qubes.x86_64 (without updates).

I would provide more info from my custom.cfg, but there is afaik no way to copy content from dom0 terminal to another VMs (running firefox). The tutorial seems to be outdated (no file matching qubes-clipboard* lies on my /). Shall I file a bug?

I am using a wireless connection as well.

Note that the GUI app Software Updater is also not working. I would pass the screenshot, if it were not so clumsy. The title says [Dom0] No network connection available - Plasma Widgets shell and after clicking on Details < < there is a message cannot refresh cache when offline. Shall I file a separate bug for this?

Also note the command qvm-dom0-upgrade has been renamed to qvm-dom0-update. However, the command in question is qubes-dom0-update, so the title should be renamed accordingly.

[qubesuser2]

I may have had the same problem as Zrubi, and posted it in the mailing list, and had it answered by prance.
See here: https://groups.google.com/forum/?_escaped_fragment_=topic/qubes-users/Feew33DFAAM#!topic/qubes-users/Feew33DFAAM . Note my problem was with sudo qubes-dom0-update, and yours was with upgrade so they may be different problems. Somewhere along the way I have had a successful update without the fix recommended by prance, but that may have been with qubes v3.1 rc1. The update I received after the changes recommended by prance was pretty small, only two items totaling only about 313 k.

[qubesuser2]

I may have had the same problem as Zrubi, and posted it in the mailing list, and had it answered by prance.
See here: https://groups.google.com/forum/?_escaped_fragment_=topic/qubes-users/Feew33DFAAM#!topic/qubes-users/Feew33DFAAM . Note my problem was with sudo qubes-dom0-update, and yours was with upgrade so they may be different problems. Somewhere along the way I have had a successful update without the fix recommended by prance, but that may have been with qubes v3.1 rc1. The update I received after the changes recommended by prance was pretty small, only two items totaling only about 313 k.

[mpalenik-redhat]

It seems we have a solution, then. Confirming it works as intended.

The solution is to run sudo qubes-dom0-update --enablerepo=qubes-*-testing to only update or sudo qubes-dom0-update --enablerepo=qubes-*-testing --clean to update and also clean the yum cache to avoid possible problems.

I suggest adding this to the Known issues for 3.1rc2, or creating an alias in ~/.bash_aliases or ~/.bashrc. The syntax is alias qubes-dom0-update='qubes-dom0-update --enablerepo=qubes-*-testing --clean' and alias sudo='sudo ' to also make the sudo work.

The fix:
echo "alias sudo='sudo '" >> ~/.bash_aliases &&
echo "alias qubes-dom0-update='qubes-dom0-update --enablerepo=qubes-*-testing --clean'" >> ~/.bash_aliases &&
cp ~/.bashrc ~/.bashrc.bak &&
echo ". ~/.bash_aliases" >> ~/.bashrc &&
. ~/.bashrc

To remove the fix:
rm ~/.bash_aliases && rm ~/.bashrc.bak; unalias sudo; unalias qubes-dom0-update;

After the fix:
sudo qubes-dom0-update
will work!

Needless to say, the updated file was small but seemed important, so I recommend to update. The Software Updater (GUI application) still does not work. The fedora-23: Package Updater works, but there are no updates. Probably none have been released yet, so it might be correct.

Note: I have corrected my post multiple times to improve the solution. Can anyone (besides me) confirm that the fix works?

[mpalenik-redhat]

It seems we have a solution, then. Confirming it works as intended.

The solution is to run sudo qubes-dom0-update --enablerepo=qubes-*-testing to only update or sudo qubes-dom0-update --enablerepo=qubes-*-testing --clean to update and also clean the yum cache to avoid possible problems.

I suggest adding this to the Known issues for 3.1rc2, or creating an alias in ~/.bash_aliases or ~/.bashrc. The syntax is alias qubes-dom0-update='qubes-dom0-update --enablerepo=qubes-*-testing --clean' and alias sudo='sudo ' to also make the sudo work.

The fix:
echo "alias sudo='sudo '" >> ~/.bash_aliases &&
echo "alias qubes-dom0-update='qubes-dom0-update --enablerepo=qubes-*-testing --clean'" >> ~/.bash_aliases &&
cp ~/.bashrc ~/.bashrc.bak &&
echo ". ~/.bash_aliases" >> ~/.bashrc &&
. ~/.bashrc

To remove the fix:
rm ~/.bash_aliases && rm ~/.bashrc.bak; unalias sudo; unalias qubes-dom0-update;

After the fix:
sudo qubes-dom0-update
will work!

Needless to say, the updated file was small but seemed important, so I recommend to update. The Software Updater (GUI application) still does not work. The fedora-23: Package Updater works, but there are no updates. Probably none have been released yet, so it might be correct.

Note: I have corrected my post multiple times to improve the solution. Can anyone (besides me) confirm that the fix works?

[marmarek]

The problem with missing /var/lib/qubes/updates/repodata/repomd.xml is just about about handling "no updates" situation. It doesn't affect installation of updates when they are available.

So, enabling testing repository, makes some (testing) updates available, so indeed it looks like the issue is gone.

[marmarek]

The problem with missing /var/lib/qubes/updates/repodata/repomd.xml is just about about handling "no updates" situation. It doesn't affect installation of updates when they are available.

So, enabling testing repository, makes some (testing) updates available, so indeed it looks like the issue is gone.

[mpalenik-redhat]

Interestingly, the problem won't reoccur after sudo qubes-dom0-update --disablerepo=qubes-*-testing --clean. I could not repoduce the error with sudo qubes-dom0-update nor sudo qubes-dom0-update --clean in cases when there are no updates. There have been no updates in any of the cases.

Note I unaliased the stuff from my fix for the test.

[mpalenik-redhat]

Interestingly, the problem won't reoccur after sudo qubes-dom0-update --disablerepo=qubes-*-testing --clean. I could not repoduce the error with sudo qubes-dom0-update nor sudo qubes-dom0-update --clean in cases when there are no updates. There have been no updates in any of the cases.

Note I unaliased the stuff from my fix for the test.

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.1.7-1.fc20 has been pushed to the r3.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.1.7-1.fc20 has been pushed to the r3.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.1.7-1.fc20 has been pushed to the r3.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.1.7-1.fc20 has been pushed to the r3.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.0.19-1.fc20 has been pushed to the r3.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.0.19-1.fc20 has been pushed to the r3.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.0.19-1.fc20 has been pushed to the r3.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.0.19-1.fc20 has been pushed to the r3.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update