Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot Update debian-9 and fedora-29 on Qubes 4.0.1 #4714

Closed
scoobyscrappy opened this issue Jan 14, 2019 · 4 comments
Closed

Cannot Update debian-9 and fedora-29 on Qubes 4.0.1 #4714

scoobyscrappy opened this issue Jan 14, 2019 · 4 comments
Labels
C: Debian/Ubuntu C: Fedora R: cannot reproduce Resolution: Attempts to replicate the problem have not been reliably successful enough to proceed. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@scoobyscrappy
Copy link

scoobyscrappy commented Jan 14, 2019

Qubes OS version:

4.0.1 (clean install)

Affected component(s):

Debian-9 and Fedora-29 Template Updates


Steps to reproduce the behavior:

Start Qube Manager
Right-click debian-9 and select Update Qube
Right-click fedora-29 and select Update Qube

Select debian-9 template terminal: sudo apt-get update
Select fedora-29 template terminal: sudo dnf update

Expected behavior:

Update debian-9 and fedora-29 templates and remove pending updates from Qube Manager.

Actual behavior:

I got the same errors when I terminal into the debian-9 and fedora-29 templates.

Here is the errors I got from the debian-9 update:

Jan 13 09:30:09 localhost systemd[1]: Started Forward connection to updates prox
y over Qubes RPC (127.0.0.1:59084).
Jan 13 09:30:09 localhost systemd[1]: Started Forward connection to updates prox
y over Qubes RPC (127.0.0.1:59086).
Jan 13 09:30:09 localhost systemd[1]: qubes-updates-proxy-forwarder@0-127.0.0.1:
8082-127.0.0.1:59082.service: Main process exited, code=exited, status=1/FAILURE
Jan 13 09:30:09 localhost systemd[1]: qubes-updates-proxy-forwarder@0-127.0.0.1:
8082-127.0.0.1:59082.service: Unit entered failed state.
Jan 13 09:30:09 localhost systemd[1]: qubes-updates-proxy-forwarder@0-127.0.0.1:
8082-127.0.0.1:59082.service: Failed with result 'exit-code'.

Here is the errors I get from fedora-29:

2019-01-13T17:34:39Z DEBUG Unknown configuration value: failovermethod=priority
in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failoverm
ethod" does not exist
2019-01-13T17:34:39Z DEBUG repo: downloading from remote: fedora-modular
2019-01-13T17:34:39Z DEBUG error: Curl error (56): Failure when receiving data f
rom the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-
29&arch=x86_64 [Received HTTP code 500 from proxy after CONNECT] (https://mirror
s.fedoraproject.org/metalink?repo=fedora-modular-29&arch=x86_64).
2019-01-13T17:34:39Z DEBUG Cannot download 'https://mirrors.fedoraproject.org/me
talink?repo=fedora-modular-29&arch=x86_64': Cannot prepare internal mirrorlist:
Curl error (56): Failure when receiving data from the peer for https://mirrors.f
edoraproject.org/metalink?repo=fedora-modular-29&arch=x86_64 [Received HTTP code
 500 from proxy after CONNECT].
2019-01-13T17:34:39Z DDEBUG Cleaning up.
2019-01-13T17:34:39Z SUBDEBUG
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/dnf/repo.py", line 566, in load
    ret = self._repo.load()
  File "/usr/lib64/python3.7/site-packages/libdnf/repo.py", line 503, in load
    return _repo.Repo_load(self)
RuntimeError: Failed to synchronize cache for repo 'fedora-modular'

General notes:


Related issues:

@andrewdavidwong andrewdavidwong added T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. C: Fedora C: Debian/Ubuntu labels Jan 15, 2019
@andrewdavidwong andrewdavidwong added this to the Release 4.0 updates milestone Jan 15, 2019
@ghost
Copy link

ghost commented Jan 26, 2019

How to solve this issue?

@0spinboson
Copy link

it reads like a connectivity issue. Both update fine here.

@marmarek
Copy link
Member

Looks like updates proxy doesn't work. See what VM you have set for those templates in /etc/qubes-rpc/policy/qubes.UpdatesProxy (see documentation) - the line with target=.... Check if that VM exists and can be started.

@scoobyscrappy
Copy link
Author

I decided to do a clean Qubes install a few days ago and I was able to update Debian-9 and Fedora-29. I might have selected to use Whonix for the updates during the setup procedure. I was having problems connecting to Tor so that was probably the reason for the update problem.
Thanks for following up.

@andrewdavidwong andrewdavidwong added the R: cannot reproduce Resolution: Attempts to replicate the problem have not been reliably successful enough to proceed. label Jan 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: Debian/Ubuntu C: Fedora R: cannot reproduce Resolution: Attempts to replicate the problem have not been reliably successful enough to proceed. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

4 participants