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

gpk_viewer in a VM keeps displaying "Failed:failed" error when trying to install updates and aborts the update. #643

Closed
marmarek opened this Issue Mar 8, 2015 · 7 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 22 Jul 2012 09:12 UTC
I can now reproduce it quite often, on two different templates, and on two different machines. Interestingly commandline yum update works just fine. Also, there is notething interesting in the logs...

Migrated-From: https://wiki.qubes-os.org/ticket/643

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 23 Jul 2012 21:48 UTC
Perhaps this is related to #645? But this doesn't explain why cmdline update works at the same time...

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 23 Jul 2012 21:48 UTC
Perhaps this is related to #645? But this doesn't explain why cmdline update works at the same time...

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 5 Aug 2012 09:53 UTC
I can still see this problem, even with the latest core and without kernel in my template:

[user](user@fedora-17-x64)$ rpm -qa | grep kernel
qubes-core-vm-kernel-placeholder-1.0-1.fc17.x86_64
libreport-plugin-kerneloops-2.0.10-3.fc17.x86_64
abrt-addon-kerneloops-2.0.10-4.fc17.x86_64

[user](user@fedora-17-x64)$ rpm -qa | grep ^qubes
qubes-core-vm-kernel-placeholder-1.0-1.fc17.x86_64
qubes-core-vm-libs-1.7.36-1.fc17.x86_64
qubes-gui-vm-1.4.15-1.fc17.x86_64
qubes-core-vm-systemd-1.7.36-1.fc17.x86_64
qubes-gpg-split-1.0-1.fc17.x86_64
qubes-core-vm-1.7.42-1.fc17.x86_64

?

Member

marmarek commented Mar 8, 2015

Comment by joanna on 5 Aug 2012 09:53 UTC
I can still see this problem, even with the latest core and without kernel in my template:

[user](user@fedora-17-x64)$ rpm -qa | grep kernel
qubes-core-vm-kernel-placeholder-1.0-1.fc17.x86_64
libreport-plugin-kerneloops-2.0.10-3.fc17.x86_64
abrt-addon-kerneloops-2.0.10-4.fc17.x86_64

[user](user@fedora-17-x64)$ rpm -qa | grep ^qubes
qubes-core-vm-kernel-placeholder-1.0-1.fc17.x86_64
qubes-core-vm-libs-1.7.36-1.fc17.x86_64
qubes-gui-vm-1.4.15-1.fc17.x86_64
qubes-core-vm-systemd-1.7.36-1.fc17.x86_64
qubes-gpg-split-1.0-1.fc17.x86_64
qubes-core-vm-1.7.42-1.fc17.x86_64

?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 6 Aug 2012 12:34 UTC
I've managed to reproduce it (at least on one machine) and have logs (strace etc). Trying to find what is going on...

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 6 Aug 2012 12:34 UTC
I've managed to reproduce it (at least on one machine) and have logs (strace etc). Trying to find what is going on...

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 6 Aug 2012 12:49 UTC
Ok, found. This is triggered by network problem:

error   internal-error  Error Type: <class 'yum.Errors.NoMoreMirrorsRepoError'>;
Error Value: failure: repodata/7d03bb9a7d0aaae920422bb8dc8a38fdecf297957cb7b1e970126903fba59b1f-filelists.sqlite.bz2 from updates: [256](Errno) No more mirrors to try.;  
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3636, in <module>;    main();  
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3633, in main;    backend.dispatcher(sys.argv[ 
File : /usr/lib/python2.7/site-packages/packagekit/backend.py, line 836, in dispatcher;   self.dispatch_command(args[0](1:]);), args[1:]);  
File : /usr/lib/python2.7/site-packages/packagekit/backend.py, line 678, in dispatcher;
(...)

The error message "failed:failed" doesn't tell much here...

This "network problem" looks like be caused by our updates proxy - it blocks the request:

GET ftp://ftp.cogeco.net/fedora/linux/updates/17/x86_64/repodata/7d03bb9a7d0aaae920422bb8dc8a38fdecf297957cb7b1e970126903fba59b1f-filelists.sqlite.bz2 HTTP/1.1
User-Agent: urlgrabber/3.9.1 yum/3.4.3
Host: ftp.cogeco.net:21
Accept: */*
Proxy-Connection: Keep-Alive

Will fix the regexps.

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 6 Aug 2012 12:49 UTC
Ok, found. This is triggered by network problem:

error   internal-error  Error Type: <class 'yum.Errors.NoMoreMirrorsRepoError'>;
Error Value: failure: repodata/7d03bb9a7d0aaae920422bb8dc8a38fdecf297957cb7b1e970126903fba59b1f-filelists.sqlite.bz2 from updates: [256](Errno) No more mirrors to try.;  
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3636, in <module>;    main();  
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3633, in main;    backend.dispatcher(sys.argv[ 
File : /usr/lib/python2.7/site-packages/packagekit/backend.py, line 836, in dispatcher;   self.dispatch_command(args[0](1:]);), args[1:]);  
File : /usr/lib/python2.7/site-packages/packagekit/backend.py, line 678, in dispatcher;
(...)

The error message "failed:failed" doesn't tell much here...

This "network problem" looks like be caused by our updates proxy - it blocks the request:

GET ftp://ftp.cogeco.net/fedora/linux/updates/17/x86_64/repodata/7d03bb9a7d0aaae920422bb8dc8a38fdecf297957cb7b1e970126903fba59b1f-filelists.sqlite.bz2 HTTP/1.1
User-Agent: urlgrabber/3.9.1 yum/3.4.3
Host: ftp.cogeco.net:21
Accept: */*
Proxy-Connection: Keep-Alive

Will fix the regexps.

@marmarek marmarek assigned marmarek and unassigned rootkovska Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 6 Aug 2012 12:52 UTC
Strange, because I remember testing the update with proxy disabled, i.e. I commented out the proxy setting in the /etc/yum.conf/qubes-proxy.conf, allowed all traffic on the f/w, and tried the update again, and... it still failed in this same way.

Besides, this would not explain why yum updated from command line works fine, would it?

Member

marmarek commented Mar 8, 2015

Comment by joanna on 6 Aug 2012 12:52 UTC
Strange, because I remember testing the update with proxy disabled, i.e. I commented out the proxy setting in the /etc/yum.conf/qubes-proxy.conf, allowed all traffic on the f/w, and tried the update again, and... it still failed in this same way.

Besides, this would not explain why yum updated from command line works fine, would it?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 6 Aug 2012 12:53 UTC
I've also seen "no more mirrors to try" errors during yum update, but this doesn't stop update process. PackageKit stopped on it.

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 6 Aug 2012 12:53 UTC
I've also seen "no more mirrors to try" errors during yum update, but this doesn't stop update process. PackageKit stopped on it.

@marmarek

This comment has been minimized.

Show comment
Hide comment

@marmarek marmarek closed this Mar 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment