Created attachment 1192785 [details]
File: anaconda-tb

Created attachment 1192786 [details]
File: anaconda.log

Created attachment 1192787 [details]
File: dnf.librepo.log

Created attachment 1192788 [details]
File: environ

Created attachment 1192789 [details]
File: hawkey.log

Created attachment 1192790 [details]
File: lsblk_output

Created attachment 1192791 [details]
File: nmcli_dev_list

Created attachment 1192792 [details]
File: os_info

Created attachment 1192793 [details]
File: program.log

Created attachment 1192794 [details]
File: storage.log

Created attachment 1192795 [details]
File: syslog

Created attachment 1192796 [details]
File: ifcfg.log

Created attachment 1192797 [details]
File: packaging.log

Similar problem has been detected:

This problem is raised by running the QA:Testcase_install_repository_NFS_graphical
on f25 ppc64le Beta 1.2  
http://ppc.koji.fedoraproject.org/compose/25/Fedora-25-20161010.0/compose/Server/ppc64le/iso/Fedora-Server-dvd-ppc64le-25_Beta-1.2.iso
nfs choosen and 9.101.19.56:/share/xxx  as repo.

I am not able to use NFS in graphical mode for my repo.
Note that is working fine if I use the equivalent anaconda boot option. 
linux /ppc/ppc64/vmlinuz inst.repo=nfs:9.101.19.56:/share/xxx

Alaso, when the problem occurs, I can switch in the anaconda console and I am able to
mount the same nfs repo with a standard mount command.
mount 9.101.19.56:/share/xxx test

addons:         com_redhat_kdump, com_redhat_docker
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=/ppc/ppc64/vmlinuz ro
hashmarkername: anaconda
kernel:         4.8.0-0.rc7.git0.1.fc25.ppc64le
package:        anaconda-25.20.4-1
product:        Fedora
reason:         dnf.exceptions.ConfigError: Repository anaconda has no mirror or baseurl set.
release:        Cannot get release name.
version:        25

Created attachment 1265288 [details]
dnf_reports_missing_repo.png

The problem is still alive with f26, 
the reported error is still
"dnf.exceptions.ConfigError: Repository anaconda has no mirror or baseurl set."
despite the nfs server address specified via UI (as per dnf_reports_missing_repo.png attachment)

If required I could add similar logs as already attached, but what is missing to help investigation of this bug ?

This problem exists on anaconda 26.21.1-1 when installing Fedora-26 as well.

===============================================================================
An unknown error has occurred
===============================================================================
anaconda 26.21.1-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python3.6/site-packages/dnf/repodict.py", line 41, in add
    raise ConfigError(msg)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/payload/dnfpayload.py", line 339, in _add_repo
    self._base.repos.add(repo)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/payload/dnfpayload.py", line 952, in updateBaseRepo
    self._add_repo(base_ksrepo)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/payload/__init__.py", line 1359, in _runThread
    payload.updateBaseRepo(fallback=fallback, checkmount=checkmount)
  File "/usr/lib64/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/threads.py", line 251, in run
    threading.Thread.run(self, *args, **kwargs)
dnf.exceptions.ConfigError: Repository anaconda has no mirror or baseurl set.

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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.

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.

still valid problem for f28 ppc64/ppc64le as per openQA test:

https://openqa.stg.fedoraproject.org/tests/242832#step/install_source_graphical/7

still same problem with f29 as per openQA test
https://openqa.stg.fedoraproject.org/tests/350800#step/install_source_graphical/7

We will look at it. Thanks for the report!

(In reply to Michel Normand from comment #20)
> still same problem with f29 as per openQA test
> https://openqa.stg.fedoraproject.org/tests/350800#step/
> install_source_graphical/7

With the f29 GA level there is  still a failure in openQA test:
- setting nfs 10.0.2.110:/repo in "INSTALLATION SOURCE" menu 
- next "INSTALLATION SUMMARY" do not reports a popup as above Id#350800; but a "Error setting up base repository" small message as per https://openqa.stg.fedoraproject.org/tests/388040#step/install_source_graphical/7

The reported anaconda.log do not help to identify the source of the problem:
=== extract anaconda.log
11:12:24,010 DBG ui.gui.hubs: setting SourceSpoke status to: Setting up installation source...
11:12:24,926 DBG payload: Setting up nfs install device
11:12:24,947 DBG payload: getting release version from tree at None (29)
11:12:24,947 DBG payload: using treeinfo release version of 29
11:12:24,951 DBG payload: Updating payload thread state: 5
11:12:24,966 INF payload: Refreshing environmentAddons
11:12:24,967 ERR payload: No base repo configured
11:12:24,967 DBG payload: Updating payload thread state: -1
11:12:24,972 DBG payload: getting release version from tree at None (29)
11:12:24,972 DBG payload: using default release version of 29
11:12:24,975 INF threading: Thread Done: AnaPayloadThread (140735317995888)
...
11:12:25,005 DBG ui.gui.hubs: setting SourceSpoke status to: Error downloading package metadata
11:12:25,008 DBG ui.gui.hubs: spoke is ready: SourceSpoke
11:12:25,008 DBG ui.gui.hubs: setting SoftwareSelectionSpoke status to: Error downloading package metadata
===

Created attachment 1524720 [details]
anaconda_f29GA_20190129.log

anaconda_f29GA_20190129.log associated to above comment#22

Hello,

Could you please provide us other logs from the installation environment. The packaging.log file would be especially interesting.

Thank you

Created attachment 1525034 [details]
install_source_graphical-packaging.log

Created attachment 1525037 [details]
install_source_graphical-dnf.librepo.log

Created attachment 1525038 [details]
install_source_graphical-syslog.log

Created attachment 1525039 [details]
install_source_graphical-program.log

Created attachment 1525040 [details]
install_source_graphical-storage.log

Hello Jiri, were you able to conclude something from last attached files ? Do you need other data to investigate this problem ?

Not yet, sorry. I was looking into the provided logs but except there is some issue with nfs repositories I wasn't able to find out more and unfortunately I don't have much time to spend on this now. I'll try to get onto this soon.

This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30.

There was most probably a significant change in anaconda that make the f30 release to solve this problem as reported by openQA tests:
https://openqa.stg.fedoraproject.org/tests/500193 <= f30
https://openqa.stg.fedoraproject.org/tests/499747 <= Rawhide