The netinst tests for updates (that I added recently) don't include the package(s) from the update in the installed package set. So we can't test that a bug like #1669256 is fixed (because it's an install-time only bug that needs the fix to exist in the package set that gets installed - the fix isn't in the installer environment).
Doing this will probably involve running a support server that calls repo_setup then serves out the generated repository via HTTP or NFS or something so the install test can add that repository. We could conditionalize support_server itself to work this way for updates tests, or something...I'll figure it out.
repo_setup
support_server
This is fixed by d1006a3 (for F29+, doing it on F28 is kinda painful and not worth the effort really).
Metadata Update from @adamwill: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.