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

 This accidentally regressed due to a timing issue between when the original PR was submitted and when it got applied (we branched in the middle, resulting in Rawhide/F28 not picking up the change).

This BZ is meant to track the issue for FE purposes.

+1 FE.

+1 FE

+1 FE from me as well.

That's +3, setting accepted - that means the PRs can be merged.

...well in fact, pbrobinson already merged it. *bad* pbrobinson!

setting ON_QA, should be fixed in next compose - please test and confirm. Thanks!

NetworkManager-wifi is still not present on Fedora-Server-armhfp-28-20180421.n.1-sda.raw.xz

In addition, 

$ sudo dnf install NetworkManager-wifi

Last metadata expiration check: 0:44:29 ago on Tue 24 Apr 2018 04:25:50 PM CEST.
Dependencies resolved.
=================================================================================================
 Package                       Arch             Version                    Repository       Size
=================================================================================================
Installing:
 NetworkManager-wifi           armv7hl          1:1.10.6-1.fc28            fedora          156 k
Installing dependencies:
 wpa_supplicant                armv7hl          1:2.6-14.fc28              fedora          993 k
Downgrading:
 NetworkManager                armv7hl          1:1.10.6-1.fc28            fedora          1.5 M
 NetworkManager-libnm          armv7hl          1:1.10.6-1.fc28            fedora          1.3 M
 NetworkManager-team           armv7hl          1:1.10.6-1.fc28            fedora          128 k

The downgrading thing is odd. There is a 1.10.6-2.fc28 build but it is not stable, it should not be pulled into anything. Can you check what NetworkManager is installed *before* the downgrade? Thanks.

Oh, actually, if you've updated since you installed, that's just the usual 'updates-testing got disabled' trap. If you *didn't* update after installing, I'm still confused.

I believe the ARM server images are built by fedora-arm-server.ks in fedora-kickstarts, and its %packages looks like this:

%packages
# install the default groups for the server evironment since installing the environment is not working
@server-product
@standard
@headless-management
@container-management
@domain-client
-initial-setup-gui
-generic-release*
%end

i.e. it doesn't use the environment group, so the PR that fixed the environment group wouldn't fix the ARM disk image. We need to update the kickstart to also include the necessary groups.

https://pagure.io/fedora-kickstarts/pull-request/385 (F28)
https://pagure.io/fedora-kickstarts/pull-request/384 (master)

Pete merged the PRs, so setting ON_QA again.

Can anyone confirm the fix in RC-1.1? Thanks!

(In reply to Adam Williamson from comment #13)
> Can anyone confirm the fix in RC-1.1? Thanks!

Negative, this appears to still be missing in RC-1.1.

The previous fix was incomplete, I'm afraid. We fixed it on armhfp (aka armv7hl) via fedora-arm-server.ks, but it turns out that aarch64 needed to have the fedora-disk-server.ks updated to get these packages. We just merged https://pagure.io/fedora-kickstarts/pull-request/387 to address this if we end up respinning the Fedora 28 for another release candidate, but if not we'll probably need a Common Bugs entry for it.

Slight correction, https://pagure.io/fedora-kickstarts/pull-request/388 is the PR for F28; the earlier one was for Rawhide/F29.

(In reply to Adam Williamson from comment #13)
> Can anyone confirm the fix in RC-1.1? Thanks!

On armv7hl, NetworkManager-wifi-1.10.6-1 is here and the command "nmcli device wifi list" works.

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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

I think we can say this got fixed at last...