Just upfront: I’m using this for a local configuration work on the bugzilla package. No external connections playing.
SELinux blocks the use of phpMyAdmin (bug logged), and I had big fingertrouble, so I reinstalled Tumbleweed as a VM.
During installation I had the opportunity of manipulating what software to install, so I tried to deselect SELinux, but installation would not proceed then, so I had to switch the selection on again.
OK, booted OK, went to the config file and disabled SELinux and then rebooted.
And as on my first installation attempt, the normal boot option for Tumbleweed then hangs. I had to kill the VM, and reboot using the recovery option, and that works OK, so I could proceed with my fiddling with bugzilla.
But is this boot problem something I had to expect, or what???
There is an article how to switch back to AppArmor:
https://en.opensuse.org/How_to_switch_from_SELinux_to_AppArmor_in_Leap_16
Plse, I’m on Tumbleweed, not Leap, and secondly, I’m not interested in this additional security layers in this instance. I’m already pissed off enough that a default installation of apache does not work as it is.
The document is also valid for Tumbleweed. It just doesn’t say it. Here is another one 
which also includes sd-boot SDB:AppArmor - openSUSE Wiki
But also look at your bootline in grub…
Delete security=selinux from the kernel command line.
Default LSM in openSUSE kernel is AppArmor. If you do not like it, you need to build your own kernel.
So, I’ll believe you, but that default is overruled by the installation procedure of Tumbleweed. I’ll have a look at AppArmor shortly, but worrying whether it would have the same impact on phpMyAdmin.
Editing the grub line got rid of the issue for now. Tx.