Bug 1375709 - NFS repository setup occasionally fails with 'Installation source not set up'
Summary: NFS repository setup occasionally fails with 'Installation source not set up'
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 26
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-13 19:39 UTC by Adam Williamson
Modified: 2018-05-29 11:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:22:54 UTC
Type: Bug


Attachments (Terms of Use)
anaconda.log (22.98 KB, text/plain)
2016-09-13 19:42 UTC, Adam Williamson
no flags Details
dnf.librepo.log (21.85 KB, text/plain)
2016-09-13 19:43 UTC, Adam Williamson
no flags Details
packaging.log (4.58 KB, text/plain)
2016-09-13 19:43 UTC, Adam Williamson
no flags Details
program.log (14.50 KB, text/plain)
2016-09-13 19:44 UTC, Adam Williamson
no flags Details
storage.log (37.42 KB, text/plain)
2016-09-13 19:44 UTC, Adam Williamson
no flags Details
syslog (64.40 KB, text/plain)
2016-09-13 19:44 UTC, Adam Williamson
no flags Details

Description Adam Williamson 2016-09-13 19:39:29 UTC
We have an openQA test that does a 'graphical NFS' install - that is, it boots the Server DVD image normally, then goes to the INSTALLATION SOURCE spoke and changes the base repo to be an NFS share.

Most of the time this works great. Occasionally, we get an odd failure where, after returning from the INSTALLATION SOURCE spoke, the SOFTWARE SELECTION spoke is in an error state, claiming 'Installation source not set up'

Examples:

https://openqa.fedoraproject.org/tests/34027
https://openqa.stg.fedoraproject.org/tests/41369
https://openqa.fedoraproject.org/tests/31436
https://openqa.fedoraproject.org/tests/31220
https://openqa.fedoraproject.org/tests/25182

we see this on both F25 and Rawhide. Whenever it fails, packaging.log shows some (odd?) 404 errors:

14:44:01,402 INFO packaging: configuring base repo
14:44:01,408 INFO packaging: mounting 10.0.2.110:/repo: on /run/install/source
14:44:01,701 INFO packaging: Disabled 'updates'
14:44:01,702 INFO packaging: Disabled 'updates-testing'
14:44:01,702 INFO packaging: Trying to download '.treeinfo'
14:44:01,706 INFO packaging: Server returned 404 code
14:44:01,706 INFO packaging: Trying to download 'treeinfo'
14:44:01,708 INFO packaging: Server returned 404 code
14:44:01,708 ERR packaging: Got HTTP 404 Error when downloading [.]treeinfo files

not sure if that's related, but where is it getting a 404 from?

I will attach all available logs from a failed attempt.

Comment 1 Adam Williamson 2016-09-13 19:42:44 UTC
Created attachment 1200589 [details]
anaconda.log

Comment 2 Adam Williamson 2016-09-13 19:43:05 UTC
Created attachment 1200590 [details]
dnf.librepo.log

Comment 3 Adam Williamson 2016-09-13 19:43:41 UTC
Created attachment 1200591 [details]
packaging.log

Comment 4 Adam Williamson 2016-09-13 19:44:00 UTC
Created attachment 1200592 [details]
program.log

Comment 5 Adam Williamson 2016-09-13 19:44:24 UTC
Created attachment 1200593 [details]
storage.log

Comment 6 Adam Williamson 2016-09-13 19:44:40 UTC
Created attachment 1200594 [details]
syslog

Comment 7 Fedora End Of Life 2017-02-28 10:15:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 8 Adam Williamson 2017-04-07 18:37:59 UTC
Just saw this again on F26, so it's still happening:

https://openqa.fedoraproject.org/tests/77823

Comment 9 Adam Williamson 2017-04-07 18:39:29 UTC
Actually, that was Rawhide.

Comment 10 Fedora End Of Life 2018-05-03 08:47:35 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora  'version'
of '26'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 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 this bug is closed as described in the policy above.

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.

Comment 11 Fedora End Of Life 2018-05-29 11:22:54 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.


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