Created attachment 1168719 [details]
anaconda/program.log

Well, I test this on a computer where the RAID 5 was set (with firmware raid). While I followed those steps with raid disk this bug happens, I don't get a Windows entry. So I tried to destroy raid and use normal disks instead. And guess what? It works now.

I followed the steps in description and after installation of Fedora there is Windows grub entry and it works. I'm not sure if it isn't just a coincidence, but it works sometime on some conditions. So I'm now more -1 blocker.

os-prober does the other OS detection, so this bug is most likely there. I didn't have time to try and reproduce this yet.

Discussed during the 2016-06-14 Go/No-Go #2 meeting: [1]

The decision was made to not classify this bug as a blocker as there are other mechanisms (firmware boot) for getting around this bug. This plus the fact that this bug surrounds hardware RAID implementations only, we have reached this conclusion.


[1] https://meetbot.fedoraproject.org/fedora-meeting-2/2016-06-16/f24-final-go_no_go-meeting.2016-06-16-17.00.txt

Correction to above comment, the meeting was hosted on 2016-06-16.

Other installer logs are also needed (actually, the syslog logs is needed).
Also, if you have access to an installed system with that problem, please run os-prober and give its output.

Created attachment 1171464 [details]
/tmp/*.log and output of journal -a

Also this bug really happens just when uefi is used. When the systems are installed on BIOS it works fine.

Created attachment 1171465 [details]
/tmp/*.log and output of journal -a

Also this bug really happens just when uefi is used. When the systems are installed on BIOS it works fine.

Also I tried to run os-prober and here is the output:
#os-prober
/dev/mapper/fedora_dhcp--2--216-root:Fedora release 24 (Twenty Four):Fedora:linux

> Petr Schindler 2016-06-23 08:49 EDT
> 
> Also this bug really happens just when uefi is used. When the systems are
> installed on BIOS it works fine.

In other words, to be "politically" correct, this bug appears when UEFI BIOS is used as true UEFI (CSM = OFF). When Legacy mode is used (CSM = ON), this bug does not appear/GRUB2 works correctly.

_nobody_

Maybe it's a different bug, but my Fedora 26 does not add Centos 7 to the boot menu. It does add however, windows 10 and debian 9 and ubuntu 1604.

Sorry for the silence, I'll come to this bug soon.
But, @cornel, this bug is really about the issue with Windows, so it is likely that it is a different bug. Please provide installer logs and/or run os-prober and see if it finds CentOS or not.

A few things need to be clarified. I don;t remember if the installer found Centos or not, because: after installing Fedora, i've also installed ubuntu, debian and centos so the boot manager was replaced. Then, when i wanted to put Fedora's grub back, i'e found there was not grub.cfg and i had only one empty grub shell to play with. then i ran grub2-mkconfig and recreated grub.cfg and then i've seen Centos is missing.

os-prober is not finding Centos.
On a different system, grub2-mkconfig | grep -i centos shows centos even if os-prober is not seeing it. but that is a different setup. (this happens both before and after upgrading from f25 to f26.). 
I don't see installer logs in /root.

@Petr Schindler: excuse me, do you have still access to that system? I need some info, mainly the output of following command: 
udevadm info -q path -n /dev/md126p2

And, is md126p2 your EFI partition?! It seems so!

@cornel panceac: Do you also have a RAID or LVM setup? If not, you probably need to fill a new bug. As os-prober doesn't find your CentOS, please run this command in a shell:
journalctl -lf > osprober.log

Then, in another shell run os-prober. When finished, use Ctrl+C to terminate the journalctl command in the other shell and send your osprober.log in your bug report.

@Peter: please also give me the output of the following command:
udevadm info -q property -n /dev/md126p2 | grep -E '^ID_PART_ENTRY_(TYPE|SCHEME)='

ok, it definitely looks like a different bug. Centos 7 /boot is in /dev/sda9 .
in the log i can see:

$ cat osprober.log | grep sda9
iul 19 11:46:03 localhost.localdomain cornel[3173]: os-prober: debug: running /usr/libexec/os-probes/50mounted-tests on /dev/sda9
iul 19 11:46:03 localhost.localdomain cornel[3173]: 50mounted-tests: debug: creating device mapper device /dev/mapper/osprober-linux-sda9
iul 19 11:46:03 localhost.localdomain cornel[3173]: 05efi: debug: /dev/sda9 is xfs partition: exiting
...
iul 19 11:46:03 localhost.localdomain cornel[3173]: 50mounted-tests: debug: remove device mapper device /dev/mapper/osprober-linux-sda9

For whatever reason os-prober doesn't care about XFS. However, xfsprogs is installed:

$ rpm -q xfsprogs
xfsprogs-4.10.0-1.fc26.x86_64

Created attachment 1301041 [details]
os-prober log

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

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

@cornel: what is your CentOS 7 / partition? /boot is not enough. And if your CentOS 7 / partition is encrypted (and not unlocked when you run os-prober), os-prober won't find it.

(In reply to Hedayat Vatankhah from comment #18)

Even if /dev/dm-5 (c7-root) is mounted, it is still not added by grub2-mkconfig.
In the new os-prober log, 'dm' does not even appear.

Please open a separate bug with the logs when CentOS partition is unlocked (I don't remember if it is allowed to be also mounted, but preferably give the log when CentOS / partition is unlocked but not mounted. )

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