Bug 1565369

Hi Adam,

Could you please attach installation logs. Thank you.

Created attachment 1420117 [details]
anaconda.log

Created attachment 1420118 [details]
dbus.log

Created attachment 1420119 [details]
ifcfg.log

Created attachment 1420120 [details]
journalctl -b output

Created attachment 1420121 [details]
lvm.log

Created attachment 1420122 [details]
program.log

Created attachment 1420123 [details]
storage.log

Created attachment 1420124 [details]
X.log

This is the case also in F28 Beta, Dusty do you care to have this fixed in F28?

It would be nice to have this fixed for f28, but I don't necessarily think it's critical. Is it possible we can have someone do quick investigation to see if the solution is simple?

It should be simple:
https://github.com/rhinstaller/anaconda/pull/1435

Yeah, in that case I prefer F28 :)

Offhand...

NetworkSpoke.py:
    @property
    def completed(self):
        """ Check whether this spoke is complete or not. Do an additional
            check if we're installing from CD/DVD, since a network connection
            should not be required in this case.
        """
        return (not can_touch_runtime_system("require network connection")
                or nm.nm_activated_devices())

I suspect Anaconda doesn't understand that we injected the ostree content in - it's a different process from the classical "DVD" model with RPMs that is generated by pungi.

Proposed as a Freeze Exception for 28-final by Fedora user walters using the blocker tracking app because:

 Part of the installation experience for FAW.  Not a blocker though.

Are there any other Anaconda changes pending for F28?  If not I'm happy to do a build/test for this.  I do see https://bugzilla.redhat.com/show_bug.cgi?id=1566621 but it's not clear that's going to be worked on soon.

It's best to leave it to the anaconda team, there's a process and a schedule for doing the builds. This will still have time to get in. They usually build on Mondays, so there's a good chance it'll go in then.

Discussed during the 2018-04-16 blocker review meeting: [1]

The decision to classify this bug as an AcceptedFreezeException was made as it:

"there's clearly a benefit to having the appstream data as up to date as possible with the packages included in Final, so updating it after freeze is a good idea"

[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2018-04-16/f28-blocker-review.2018-04-16-16.00.log.txt

Whoops, wrong decision... :

Discussed during the 2018-04-16 blocker review meeting: [1]

The decision to classify this bug as an AcceptedFreezeException was made as it:

"this isn't a super important fix, but it is to the installer (so cannot be done post-install) and is pretty isolated and safe, so accepted as an FE issue so long as it lands soon"

[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2018-04-16/f28-blocker-review.2018-04-16-16.00.log.txt

anaconda-28.22.8-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-7c1909bd31

anaconda-28.22.8-1.fc28, initial-setup-0.3.58-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-7c1909bd31

anaconda-28.22.8-1.fc28, initial-setup-0.3.58-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

can someone confirm this is fixed now?

Just tested it with the ISO from today's F28 two-week Atomic nightly build, worked fine.