Bug 873605

Created attachment 639230 [details]
anaconda-main.png

Created attachment 639231 [details]
anaconda-source.png

Created attachment 639232 [details]
anaconda.log

Created attachment 639233 [details]
packaging.log

Created attachment 639234 [details]
program.log

Created attachment 639235 [details]
storage.log

Created attachment 639236 [details]
syslog

I can confirm my repository/ files were corrupt (files missing).

This could be F18 NTH (or might be even blocker), proposing.

anaconda-18.27-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.27-1.fc18

Package anaconda-18.27-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.27-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17823/anaconda-18.27-1.fc18
then log in and leave karma (feedback).

With anaconda 18.27 I'm getting the same behavior as in bug 873600 - with invalid repository metadata (missing files), no warning icon is displayed, the item is grayed out, but there is an error line inside the spoke. I'm not really sure this is fixed. Setting dependson:873600 and will verify once that one is fixed.

Package anaconda-18.28-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.28-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17823/anaconda-18.28-1.fc18
then log in and leave karma (feedback).

Kamil, can you re-check this? With the regressions in RC1, perhaps TC9 would be the best indicator of whether it's fixed. If it's good in TC9, close the bug, 18.28 went stable.

I checked with anaconda 28.19 (TC9). The situation is still very sub-optimal. It differs whether you set up NFS interactively or with inst.repo. Attaching screenshots.

Reproducer:
1. Extract DVD.iso
2. go into repodata/ and delete all files with long filenames (checksum in the filename)
3. share it over NFS
4. provide it inside anaconda, either interactively or with nfs.repo

(I found out because file-roller truncates long files names and therefore I ended up with "missing" files in repodata/).

I think bug 873600 needs to be solved first.

Created attachment 650348 [details]
18.29 interactive main.png

Created attachment 650349 [details]
18.29 interactive detail.png

Created attachment 650350 [details]
18.29 inst.repo main.png

Created attachment 650351 [details]
18.29 inst.repo detail.png

that sounds rather like a completely different bug. i mean, a case where the repodata are just wrong is kinda different from where we came in, isn't it?

(In reply to comment #19)
No, see description and comment 8. This is the same problem.

If it's the same bug, I'm going to close it as a dup of the other.  I don't think it is, and the original issue's been fixed, but whatever.

*** This bug has been marked as a duplicate of bug 873600 ***

There has been some misunderstanding here. I'll try to explain again. This bug report documents the fact that if I have an invalid remote repository (corrupted metadata files), I receive very little information from anaconda - in some cases no errors are reported at all.

This bug is worsened by bug 873600, so I believe we should fix bug 873600 first, and only then deal with this one.

I hope I was able to describe it clearly enough this time.

What's the current status of this?

The interactive NFS mode now looks great, problem solved. Installation Source is marked as broken and "bad url" message is displayed in its detail screen.

With inst.repo approach, the Installation Source looks like valid, but you can't enter Software Selection. That still a bit confusing and might be fixed, if anaconda developers deem so.

18.37.6

Created attachment 667245 [details]
18.37.6 inst.repo main

Created attachment 667246 [details]
18.37.6 inst.repo detail

What's RC3 status? Does this still need to be open, or can we close it and open a new bug for any outstanding issues? Thanks!

No change in anaconda 18.37.11, same behavior as in comment 24 - 26.

Then can you answer the second/third questions?

There are no outstanding changes, the problem in question is the same from the beginning - corrupt repository metadata cause weird behavior in anaconda. The symptoms changed slightly in the course of time, but the issue is still the same.

We can close this bug report and file a new one, but the only benefit will be a clearer description (since Buzilla doesn't allow to edit the existing description).

Ah, sorry about that. The report got somewhat confused.

You can edit the description, though. There's a (edit) link right next to it, up at the top of the page. Click that.

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.