Bug 1171473 - Error message in fedup : fedup:message() Downloading failed: invalid data in .treeinfo: File contains no section headers.
Summary: Error message in fedup : fedup:message() Downloading failed: invalid data in ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: distribution
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1171499 1171787 1172343 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-07 13:54 UTC by dominique
Modified: 2015-04-18 21:48 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-09 20:11:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description dominique 2014-12-07 13:54:54 UTC
Today I want update my Fedora 20 to Fedora 21 with fedup, with command: 
fedup --network 21  --product=workstation

But fedup stop quickly after the research of repos.the /var/log/fedup.log

[     0.143] (II) fedup:<module>() /bin/fedup 0.9.0 starting at Sun Dec  7 08:16:12 2014
[     0.143] (DD) fedup:setup_downloader() setup_downloader(version=21, repos=[])
[     0.144] (II) fedup.yum:__init__() UpgradeDownloader(version=21,cachedir=/var/cache/system-upgrade)
[     0.144] (DD) fedup.yum:__init__() prerepoconf.cache=0
[     0.144] (II) fedup.yum:setup_repos() checking repos
[     0.158] (II) fedup.yum:doPluginSetup() enabled plugins: ['blacklist', 'whiteout', 'fastestmirror', 'langpacks']
[     0.161] (DD) fedup.yum:_getConfig() Config time: 0.017
[     0.162] (DD) fedup.yum:_getConfig() conf.cache=0
[     0.411] (II) fedup.cli:start() download adobe-linux-x86_64
[     0.502] (II) fedup.cli:start() download adobe-linux-x86_64/primary
[     0.503] (II) fedup.yum:setup_repos() repo adobe-linux-x86_64 seems OK
[     1.655] (II) fedup.cli:start() download default-installrepo/metalink
[     2.251] (II) fedup.cli:start() download default-installrepo
[     2.506] (II) fedup.cli:start() download default-installrepo/group_gz
[     3.571] (II) fedup.cli:start() download default-installrepo/primary_db
[     7.489] (II) fedup.yum:setup_repos() repo default-installrepo seems OK
[     8.346] (II) fedup.cli:start() download fedora/21/x86_64/metalink
[     8.717] (II) fedup.cli:start() download fedora/21/x86_64
[     8.795] (II) fedup.cli:start() download fedora/21/x86_64/group_gz
[     9.602] (II) fedup.cli:start() download fedora/21/x86_64/primary_db
[    58.634] (II) fedup.yum:setup_repos() repo fedora seems OK
[    59.597] (II) fedup.cli:start() download kde
[    59.972] (II) fedup.cli:start() download kde/primary_db
[    59.976] (II) fedup.yum:setup_repos() repo kde seems OK
[    60.445] (II) fedup.cli:start() download rpmfusion-free/21/x86_64
[    60.587] (II) fedup.cli:start() download rpmfusion-free/21/x86_64/group_gz
[    60.739] (II) fedup.cli:start() download rpmfusion-free/21/x86_64/primary_db
[    61.949] (II) fedup.yum:setup_repos() repo rpmfusion-free seems OK
[    62.486] (II) fedup.cli:start() download rpmfusion-free-updates/21/x86_64
[    62.574] (II) fedup.cli:start() download rpmfusion-free-updates/21/x86_64/group_gz
[    62.672] (II) fedup.cli:start() download rpmfusion-free-updates/21/x86_64/primary_db
[    63.888] (II) fedup.yum:setup_repos() repo rpmfusion-free-updates seems OK
[    64.233] (II) fedup.cli:start() download rpmfusion-nonfree/21/x86_64
[    64.383] (II) fedup.cli:start() download rpmfusion-nonfree/21/x86_64/group_gz
[    64.533] (II) fedup.cli:start() download rpmfusion-nonfree/21/x86_64/primary_db
[    64.889] (II) fedup.yum:setup_repos() repo rpmfusion-nonfree seems OK
[    65.342] (II) fedup.cli:start() download rpmfusion-nonfree-updates/21/x86_64
[    65.420] (II) fedup.cli:start() download rpmfusion-nonfree-updates/21/x86_64/group_gz
[    65.489] (II) fedup.cli:start() download rpmfusion-nonfree-updates/21/x86_64/primary_db
[    65.860] (II) fedup.yum:setup_repos() repo rpmfusion-nonfree-updates seems OK
[    66.947] (II) fedup.cli:start() download updates/21/x86_64/metalink
[    67.164] (II) fedup.cli:start() download updates/21/x86_64
[    67.312] (II) fedup.cli:start() download updates/21/x86_64/group_gz
[    68.576] (II) fedup.cli:start() download updates/21/x86_64/updateinfo
[    69.043] (II) fedup.cli:start() download updates/21/x86_64/primary_db
[    72.142] (II) fedup.cli:start() download updates/21/x86_64/pkgtags
[    75.773] (II) fedup.yum:setup_repos() repo updates seems OK
[    76.138] (II) fedup.yum:log_grab_failure() http://download.virtualbox.org/virtualbox/rpm/fedora/21/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
[    76.139] (II) fedup.yum:setup_repos() can't find valid repo metadata for virtualbox
[    76.140] (DD) fedup.yum:setup_repos() repos.cache=0
[    76.140] (II) fedup:setup_downloader() disabled repos: virtualbox
[    76.140] (DD) fedup.yum:_get_treeinfo() fetching .treeinfo.signed from 'default-installrepo'
[    76.604] (II) fedup.cli:start() download None
[    76.606] (II) fedup.yum:_get_treeinfo() verifying .treeinfo.signed
[    76.607] (DD) fedup.yum:init_keyring() creating gpgdir /var/cache/system-upgrade/gpgdir
[    76.607] (DD) fedup.yum:_setup_keyring() checking rpmdb trusted keys
[    76.655] (DD) fedup.yum:_getRpmDB() rpmdb time: 0.000
[    76.659] (DD) fedup.yum:import_key() importing key 246110c1
[    76.689] (DD) fedup.yum:import_key() importing key ae688223
[    76.716] (DD) fedup.yum:import_key() importing key b5f29883
[    76.739] (DD) fedup.yum:import_key() importing key f6777c67
[    76.763] (DD) fedup.yum:import_key() importing key 98ab5139
[    76.784] (DD) fedup.yum:import_key() importing key ff6382fa
[    76.805] (DD) fedup.yum:import_key() importing key 00f97f56
[    76.827] (DD) fedup.yum:import_key() importing key 7fac5991
[    76.849] (II) fedup.yum:_setup_keyring() checking GPG keys for instrepo
[    76.849] (II) fedup.yum:check_keyfile() checking keyfile /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-21-x86_64
[    76.850] (DD) fedup.yum:check_keyfile() keyfile owned by package fedora-release-0:20-3
[    76.851] (DD) fedup.yum:check_keyfile() package was signed with key 246110c1
[    76.852] (DD) fedup.yum:check_keyfile() key 246110c1 is trusted by rpm
[    76.852] (--) fedup.yum:_retrievePublicKey() Récupération de la clé à partir de file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-21-x86_64
[    76.859] (DD) fedup.yum:import_key() importing key 95a43f54
[    76.887] (II) fedup.yum:_get_treeinfo() .treeinfo.signed was signed with a trusted key
[    76.887] (II) fedup:message() Downloading failed: invalid data in .treeinfo: File contains no section headers.
file: /var/cache/system-upgrade/.treeinfo, line: 1
'-----BEGIN PGP SIGNED MESSAGE-----\n'
[    76.887] (DD) fedup:<module>() Traceback (for debugging purposes):
Traceback (most recent call last):
  File "/bin/fedup", line 286, in <module>
    main(args)
  File "/bin/fedup", line 190, in main
    kernel, initrd = f.download_boot_images() # TODO: force arch?
  File "/usr/lib/python2.7/site-packages/fedup/download.py", line 458, in download_boot_images
    raise YumBaseError(_("invalid data in .treeinfo: %s") % str(e))
YumBaseError: invalid data in .treeinfo: File contains no section headers.
file: /var/cache/system-upgrade/.treeinfo, line: 1
'-----BEGIN PGP SIGNED MESSAGE-----\n'
[    76.888] (II) fedup:<module>() /bin/fedup exiting cleanly at Sun Dec  7 08:17:29 2014

It seem that there is problem with .treeinfo file

Can you solve that ?

Comment 1 Jeremy Nickurak 2014-12-07 20:39:54 UTC
Sounds similar to https://bugzilla.redhat.com/show_bug.cgi?id=1171499

Comment 2 satellitgo 2014-12-07 20:47:55 UTC
fedup --network 21  --product=workstation  may be incorrect command:

Try
fedup --network 21  --product workstation

options are
    product [workstation|server|cloud|nonproduct]

Comment 3 Adam Williamson 2014-12-08 01:01:51 UTC
No, it's correct. fedup refuses to run if the syntax is incorrect.

Can you remove /var/cache/system-upgrade/.treeinfo and try again? If it still fails, can you attach that file?

Comment 4 Jeremy Nickurak 2014-12-08 01:17:13 UTC
From #1171499:

> kk4ewt on irc pointed out the release notes https://lists.fedoraproject.org/pipermail/devel/2014-December/204924.html
> 
> "fedup tests may require the --nogpgcheck parameter until the signed .treeinfo file is available."
> 
> This worked for me. Thanks!

Same thing here, so I don't have the file any more. That said:

Deleting the .treeinfo file didn't help, it was just re-created the same way.

What was included in the file was a PGP-signed message, similar to what's attached to this defect as "treeinfo created by fedup"

GNUPGP did authenticate the signature on that file, if I pointed it at it manually.

Comment 5 dominique 2014-12-08 05:19:19 UTC
(In reply to Adam Williamson (Red Hat) from comment #3)
> No, it's correct. fedup refuses to run if the syntax is incorrect.
> 
> Can you remove /var/cache/system-upgrade/.treeinfo and try again? If it
> still fails, can you attach that file?

I remove /var/cache/system-upgrade/.treeinfo and I have same error.

Content of file /var/cache/system-upgrade/.treeinfo:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

e0f189a0539a149ceb34cb2b28260db7780f348443b756904e6a250474953f69 *Fedora-Live-Workstation-i686-21-5.iso
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJUgif8AAoJEImtToeVpD9U8qYQAM2TzItcJNflA5oYrTpYwZET
RvewnWoCb3NcwqHOx7Um6ZJ8VQ31AOfYXW8+Y0W8CSmDxBWNbUGwshhR8wQUOj/5
Gzu8JxbwEFtzZ1192BW+EzoHT4TMOlG7nZWAv17+H3s0gF4HqqwgZ5DFtg/mDikU
zPtH0MT8/B+2KnnXPiOad8ri5+jHZWFP+tFnuBhtVmtcZZHBry6qJoh86BP4o6N7
PFT33KnDvgTMM6cHgRGi3ZXuZR2Q2iuGk62LvzxjRgzw3ZO5TdH7mBVYDmrm6mLW
ojWzfGMMcEybDr6sYzwI1Ory9UYTeUF09xooBdzJZX/nk3eNBY1WpjTOm+oUyEyU
qBtKSa0LwLOLMddy6wtiC0Y1YaDQbUWM5T6JJTiTNh7lIB6o2Ytj48sFynkrdlaY
FIwqNcxztHK2jiEqBMNATBhhrjN0heP8oubHphdpSn2IPvUBDarQzAQQpaFHnImH
7Sb1yqBBCOWlPmHcpWQtiOVc0adGs7vP1g67oylpMsMbz+ZzCEn7E60w3ppVHeEy
ZnI6b1LZyKk+Rs3Fw/ucmHAhX/AZ5/gx/OQfZuT6F3MBsxGJw6Jk7vWbYIopArQ4
1smWrzhBXWwZNLd1K1YyWnnUYRwTAVbuc05y6sNOrXUPWj7mZxgp0NYxNPTBmX0j
cQQwFoh8stH4ZQ84QpI1
=v9Nu
-----END PGP SIGNATURE-----

@Jeremy Nickurak:
--nogpgcheck parameter may be help, but I think it's not a good idea, for me fedup upgrade about 2200 packages, and with no control...

Comment 6 Adam Williamson 2014-12-08 06:56:53 UTC
Ah. Well that one's not hard to diagnose: the .treeinfo.signed filed in the RC5 tree is completely wrong.

https://dl.fedoraproject.org/pub/alt/stage/21_RC5/Server/armhfp/os/.treeinfo.signed , https://dl.fedoraproject.org/pub/alt/stage/21_RC5/Server/i386/os/.treeinfo.signed and https://dl.fedoraproject.org/pub/alt/stage/21_RC5/Server/x86_64/os/.treeinfo.signed are all the i686 Workstation live directory's checksum file, for some reason, and not the correct .treeinfo files.

It works with --nogpgcheck because when you pass that it gets the unsigned copy of the .treeinfo file - which is just called .treeinfo - and that one is correct.

Comment 7 Adam Williamson 2014-12-08 07:00:47 UTC
dominique: for now it's fairly safe because the fedora-install-21 redirect that fedup uses:

Comment 8 dominique 2014-12-08 07:06:12 UTC
(In reply to Adam Williamson (Red Hat) from comment #7)
> dominique: for now it's fairly safe because the fedora-install-21 redirect
> that fedup uses:

Ok Adam,
I see in /var/cache/system-upgrade a file named .treeinfo.signed with this content:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

e0f189a0539a149ceb34cb2b28260db7780f348443b756904e6a250474953f69 *Fedora-Live-Workstation-i686-21-5.iso
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJUgif8AAoJEImtToeVpD9U8qYQAM2TzItcJNflA5oYrTpYwZET
RvewnWoCb3NcwqHOx7Um6ZJ8VQ31AOfYXW8+Y0W8CSmDxBWNbUGwshhR8wQUOj/5
Gzu8JxbwEFtzZ1192BW+EzoHT4TMOlG7nZWAv17+H3s0gF4HqqwgZ5DFtg/mDikU
zPtH0MT8/B+2KnnXPiOad8ri5+jHZWFP+tFnuBhtVmtcZZHBry6qJoh86BP4o6N7
PFT33KnDvgTMM6cHgRGi3ZXuZR2Q2iuGk62LvzxjRgzw3ZO5TdH7mBVYDmrm6mLW
ojWzfGMMcEybDr6sYzwI1Ory9UYTeUF09xooBdzJZX/nk3eNBY1WpjTOm+oUyEyU
qBtKSa0LwLOLMddy6wtiC0Y1YaDQbUWM5T6JJTiTNh7lIB6o2Ytj48sFynkrdlaY
FIwqNcxztHK2jiEqBMNATBhhrjN0heP8oubHphdpSn2IPvUBDarQzAQQpaFHnImH
7Sb1yqBBCOWlPmHcpWQtiOVc0adGs7vP1g67oylpMsMbz+ZzCEn7E60w3ppVHeEy
ZnI6b1LZyKk+Rs3Fw/ucmHAhX/AZ5/gx/OQfZuT6F3MBsxGJw6Jk7vWbYIopArQ4
1smWrzhBXWwZNLd1K1YyWnnUYRwTAVbuc05y6sNOrXUPWj7mZxgp0NYxNPTBmX0j
cQQwFoh8stH4ZQ84QpI1
=v9Nu
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJUgihSAAoJEImtToeVpD9U1lUP/1H3zSgG994x7QOcpqsrj7RF
ouHdjAeyhkSJQ2q860I+H38pPg+idEel28lftAOnrOhnNs1ELq4SESN/sIrHcRT0
AjKceqaaQEcOnXwmuDBiJPVdtvr7XX8tYv5GlXyXeMa3IbdegTGjl4fRO8rhue/u
mhlTrRluc0KqmWbSaITggndQW98cvvPPAGIBVbr2EvsY750Sqkhciv/1hejOPY/o
QhIrNbDeca6ptNUEv4cVO0V66sc+eNdQV2NKAKlLlK3NAQ3nMzIOcdmBUh8EoJy9
pqSBZSOOX0oCCG33c72Go65dy+TX80DYJyjElkChXNlmCGAtunyYyXTTMUOLXphO
H83B16mJCoc08sQOeJeyXzVHPBiBXZRyUBW5PZe9sl3OSDWs+P1QjU7/0a/X+BZ8
K1pCQo/RxjryIZYFZGLiSGRg3UyU9YxZ6sA4s8Mw/cHj3xgS0vsCSkBV1hYlXmTv
OWUKzsEW45nrgf7mmOtGunTWPWnd797jcnjeNMB1/GYkxSGPE6tZA52KVa083zbb
k3Elb9X1ZG7b0abgb9L3xEzOvohzmssglZuKo5AXZ4bvfCjRFLqier6et+T5ymQ3
V7ld7JPCjg4uNM4rrUqYN4DZBnUOHPfIfV3HQZ9X4UsZwVF7ouJaDoCulWdHOJZu
QMxvAfUpNh9K9SfAO+k7
=+nSd
-----END PGP SIGNATURE-----

May-be the error is here.

Comment 9 Adam Williamson 2014-12-08 07:21:19 UTC
I already explained what the error is, in #c6. We don't need any more information, thanks.

Comment 10 dominique 2014-12-08 07:32:09 UTC
Ok Adam
I use --nogpgcheck option and fedup start.
I have 2696 package to upgrade, I think that will be finished in 3 hours.

I send you feedback after fedup is completed.t

Comment 11 dominique 2014-12-08 10:15:41 UTC
I am now with Fedora 21, all work fine, except nvidia drivers which give me a 800x600 resolution.

But It's not in this bugzilla that I would find the solution, only in the rpmfusion bugzilla.

Thank for your help.

Comment 13 Adam Williamson 2014-12-08 15:59:01 UTC
*** Bug 1171787 has been marked as a duplicate of this bug. ***

Comment 14 Will Woods 2014-12-09 20:08:15 UTC
*** Bug 1171499 has been marked as a duplicate of this bug. ***

Comment 15 Adam Williamson 2014-12-09 20:11:18 UTC
This was fixed on Saturday to point to RC5 in stage, then fixed last night to point to the final 21 mirrors. closing.

Comment 16 Will Woods 2014-12-10 00:09:52 UTC
*** Bug 1172343 has been marked as a duplicate of this bug. ***

Comment 17 juicejar 2014-12-10 00:14:42 UTC
This is still erroring at 6:14pm CST 12/9 and I have double checked I have the newest fedup installed.

Comment 18 Adam Williamson 2014-12-10 00:17:08 UTC
We seem to have some mirror in the system stuck with a bad copy of the file, but can't figure out which it is. Try adding this parameter:

--instrepo http://mirrors.tummy.com/pub/fedora.redhat.com/fedora/linux/releases/21/Server/x86_64/os/

or really any of the mirrors at:

https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-install-21&arch=x86_64

which has the correct .treeinfo.signed file. All the ones I've checked do, I can't figure out what the bad mirror is. But mirrormanager is fairly 'intelligent', so it can be a bit tricky to pinpoint.

Comment 19 Justin W. Flory (Fedora) 2014-12-10 00:17:46 UTC
I can also confirm this is happening to me as well, using a fresh install of fedup. I've been talking in #fedora-qa about this issue and we're all a bit confused.

The solution was solved by adding the --instarepo flag and specifying a working repo, although that isn't really a "fix".

Comment 20 Adam Williamson 2014-12-10 00:28:00 UTC
I did find one mirror on the list which still had the bad files: mirror.web-ster.com . I've contacted that mirror's admin and asked if they can fix it up. I also checked with releng if we can take them out of the list until they're good.

Still, there might be more to the story. mirrormanager can, for instance, return different lists to specific IP ranges - so that unis or companies with internal mirrors can ask us to add them to the mirrormanager directory, and then folks in those sites will get the private mirror as their default. if one of those is bad, there's no way I can figure that from outside.

wwoods points out that proxies in the chain could also be messing things up, of course.

Comment 21 sattellite 2014-12-11 09:37:10 UTC
I have the same problem with fedup.noarch 0:0.9.0-2.fc20 (currently installed last version of fedup).

1. sudo rm -fr /var/chache/system-upgrade
2. sudo fedup --network 21 --product=workstation
3. Error

Error message:
Downloading failed: invalid data in .treeinfo: File contains no section headers.
file: /var/cache/system-upgrade/.treeinfo, line: 1
'-----BEGIN PGP SIGNED MESSAGE-----\n'


Last lines from /var/log/fedup.log:

[     6.467] (DD) fedup.yum:_get_treeinfo() fetching .treeinfo.signed from 'default-installrepo'
[     6.480] (II) fedup.cli:start() download None
[     6.481] (II) fedup.yum:_get_treeinfo() verifying .treeinfo.signed
[     6.481] (DD) fedup.yum:init_keyring() creating gpgdir /var/cache/system-upgrade/gpgdir
[     6.482] (DD) fedup.yum:_setup_keyring() checking rpmdb trusted keys
[     6.523] (DD) fedup.yum:_getRpmDB() rpmdb time: 0.000
[     6.526] (DD) fedup.yum:import_key() importing key 7fac5991
[     6.562] (DD) fedup.yum:import_key() importing key 246110c1
[     6.600] (DD) fedup.yum:import_key() importing key 1453936d
[     6.640] (DD) fedup.yum:import_key() importing key ae688223
[     6.675] (DD) fedup.yum:import_key() importing key dbb6c70d
[     6.716] (DD) fedup.yum:import_key() importing key 5044912e
[     6.755] (DD) fedup.yum:import_key() importing key b5f29883
[     6.797] (DD) fedup.yum:import_key() importing key f6777c67
[     6.834] (DD) fedup.yum:import_key() importing key 7c90e5af
[     6.871] (DD) fedup.yum:import_key() importing key 210d7891
[     6.915] (DD) fedup.yum:import_key() importing key 23acd201
[     6.959] (II) fedup.yum:_setup_keyring() checking GPG keys for instrepo
[     6.959] (II) fedup.yum:check_keyfile() checking keyfile /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-21-x86_64
[     6.960] (DD) fedup.yum:check_keyfile() keyfile owned by package fedora-release-0:20-3
[     6.962] (DD) fedup.yum:check_keyfile() package was signed with key 246110c1
[     6.962] (DD) fedup.yum:check_keyfile() key 246110c1 is trusted by rpm
[     6.963] (--) fedup.yum:_retrievePublicKey() Получение ключа из file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-21-x86_64
[     6.969] (DD) fedup.yum:import_key() importing key 95a43f54
[     7.039] (II) fedup.yum:_get_treeinfo() .treeinfo.signed was signed with a trusted key
[     7.040] (II) fedup:message() Downloading failed: invalid data in .treeinfo: File contains no section headers.
file: /var/cache/system-upgrade/.treeinfo, line: 1
'-----BEGIN PGP SIGNED MESSAGE-----\n'
[     7.040] (DD) fedup:<module>() Traceback (for debugging purposes):
Traceback (most recent call last):
  File "/bin/fedup", line 286, in <module>
    main(args)
  File "/bin/fedup", line 190, in main
    kernel, initrd = f.download_boot_images() # TODO: force arch?
  File "/usr/lib/python2.7/site-packages/fedup/download.py", line 458, in download_boot_images
    raise YumBaseError(_("invalid data in .treeinfo: %s") % str(e))
YumBaseError: invalid data in .treeinfo: File contains no section headers.
file: /var/cache/system-upgrade/.treeinfo, line: 1
'-----BEGIN PGP SIGNED MESSAGE-----\n'
[     7.041] (II) fedup:<module>() /bin/fedup exiting cleanly at Thu Dec 11 12:32:52 2014

Comment 22 Roman Kagan 2014-12-15 13:29:26 UTC
Another broken mirror is mirror.yandex.ru:

# curl http://mirror.yandex.ru/fedora/linux/releases/21/Server/x86_64/os/.treeinfo.signed                                                                                        -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

e0f189a0539a149ceb34cb2b28260db7780f348443b756904e6a250474953f69 *Fedora-Live-Workstation-i686-21-5.iso
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJUgif8AAoJEImtToeVpD9U8qYQAM2TzItcJNflA5oYrTpYwZET
RvewnWoCb3NcwqHOx7Um6ZJ8VQ31AOfYXW8+Y0W8CSmDxBWNbUGwshhR8wQUOj/5
Gzu8JxbwEFtzZ1192BW+EzoHT4TMOlG7nZWAv17+H3s0gF4HqqwgZ5DFtg/mDikU
zPtH0MT8/B+2KnnXPiOad8ri5+jHZWFP+tFnuBhtVmtcZZHBry6qJoh86BP4o6N7
PFT33KnDvgTMM6cHgRGi3ZXuZR2Q2iuGk62LvzxjRgzw3ZO5TdH7mBVYDmrm6mLW
ojWzfGMMcEybDr6sYzwI1Ory9UYTeUF09xooBdzJZX/nk3eNBY1WpjTOm+oUyEyU
qBtKSa0LwLOLMddy6wtiC0Y1YaDQbUWM5T6JJTiTNh7lIB6o2Ytj48sFynkrdlaY
FIwqNcxztHK2jiEqBMNATBhhrjN0heP8oubHphdpSn2IPvUBDarQzAQQpaFHnImH
7Sb1yqBBCOWlPmHcpWQtiOVc0adGs7vP1g67oylpMsMbz+ZzCEn7E60w3ppVHeEy
ZnI6b1LZyKk+Rs3Fw/ucmHAhX/AZ5/gx/OQfZuT6F3MBsxGJw6Jk7vWbYIopArQ4
1smWrzhBXWwZNLd1K1YyWnnUYRwTAVbuc05y6sNOrXUPWj7mZxgp0NYxNPTBmX0j
cQQwFoh8stH4ZQ84QpI1
=v9Nu
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJUgihSAAoJEImtToeVpD9U1lUP/1H3zSgG994x7QOcpqsrj7RF
ouHdjAeyhkSJQ2q860I+H38pPg+idEel28lftAOnrOhnNs1ELq4SESN/sIrHcRT0
AjKceqaaQEcOnXwmuDBiJPVdtvr7XX8tYv5GlXyXeMa3IbdegTGjl4fRO8rhue/u
mhlTrRluc0KqmWbSaITggndQW98cvvPPAGIBVbr2EvsY750Sqkhciv/1hejOPY/o
QhIrNbDeca6ptNUEv4cVO0V66sc+eNdQV2NKAKlLlK3NAQ3nMzIOcdmBUh8EoJy9
pqSBZSOOX0oCCG33c72Go65dy+TX80DYJyjElkChXNlmCGAtunyYyXTTMUOLXphO
H83B16mJCoc08sQOeJeyXzVHPBiBXZRyUBW5PZe9sl3OSDWs+P1QjU7/0a/X+BZ8
K1pCQo/RxjryIZYFZGLiSGRg3UyU9YxZ6sA4s8Mw/cHj3xgS0vsCSkBV1hYlXmTv
OWUKzsEW45nrgf7mmOtGunTWPWnd797jcnjeNMB1/GYkxSGPE6tZA52KVa083zbb
k3Elb9X1ZG7b0abgb9L3xEzOvohzmssglZuKo5AXZ4bvfCjRFLqier6et+T5ymQ3
V7ld7JPCjg4uNM4rrUqYN4DZBnUOHPfIfV3HQZ9X4UsZwVF7ouJaDoCulWdHOJZu
QMxvAfUpNh9K9SfAO+k7
=+nSd
-----END PGP SIGNATURE-----


I've sent a message to their contact address; however it'd be good to know why the correct version hasn't percolated there yet.

Comment 23 sattellite 2014-12-15 13:31:32 UTC
(In reply to Roman Kagan from comment #22)
> Another broken mirror is mirror.yandex.ru:
> 
> # curl
> http://mirror.yandex.ru/fedora/linux/releases/21/Server/x86_64/os/.treeinfo.
> signed                                                                      

Yesterday I updated without errors using this mirror .

Comment 24 Roman Kagan 2014-12-15 14:18:14 UTC
Unless you used --nogpgcheck that would mean that this mirror *received* the broken file *after* you upgraded.  Which, in turn, would indicate that the bug was still there.

Comment 25 sattellite 2014-12-15 14:23:23 UTC
(In reply to Roman Kagan from comment #24)
> Unless you used --nogpgcheck that would mean that this mirror *received* the
> broken file *after* you upgraded.  Which, in turn, would indicate that the
> bug was still there.

I updated without --nogpgcheck:
$ sudo fedup --network 21 --product=workstation --instrepo http://mirror.yandex.ru/fedora/linux/releases/21/Server/x86_64/os/

It was at ~ 11:00 am GMT+4. Everything was fine.

Comment 26 Adam Williamson 2014-12-16 01:42:57 UTC
I confirm yandex appears to be bad ATM. Roman, it doesn't necessarily indicate the 'bug is still there' though, exactly - because we don't know what mirror yandex is downstream from.

You can confirm for yourself that dl.fedoraproject.org has the correct file:

https://dl.fedoraproject.org/pub/fedora/linux/releases/21/Server/x86_64/os/.treeinfo.signed

Comment 27 Richard Z. 2015-01-03 12:06:02 UTC
just hit this same problem again, --instrepo workaround seems to work.

Maybe fedup could be more robust against this kind of mirror breakage?

I am a bit worried that some authority in some evil country could do this deliberately to trick users to use --nogpgcheck.

Comment 28 Sam Tuke 2015-04-18 21:48:03 UTC
Same problem here, experienced today, while upgrading F20 to F21.


Note You need to log in before you can comment on or make changes to this bug.