Comment # 11 on bug 1231482 from Cathy Hu

> How I see it is that all this should be hidden from any installer. It's a special action needed by the specific solution (SELinux).

the problem is that yast creates a snapshot after install and there is no
mechanism for me on the selinux packaging side to relabel that. so it has to be
done in the place where the snapshot was created unfortunately.

> And it's definitely not "An Installer Bug", it might be a feature request though. But a feature request definitely needs a proper description.

currently if a user enables selinux and tries to boot into the snapshot that
was created by yast and is named "after installation", they will not be able to
log in. could you point me to an example how i can describe that as a yast
feature request? i have not done that before

> Is it really YaST that creates a volume label during firstboot? I find that hard to believe.

i think so, but let me know if i am wrong:
https://github.com/yast/yast-installation/blob/master/src/lib/installation/snapshots_finish.rb#L71
https://github.com/yast/yast-installation/blob/41dfed17b2e467697162d640708c4a7f34b84ea7/test/snapshots_finish_test.rb#L157

> There is no useful hint in *any* of the screenshots what is going on there. If there is a firstboot workflow, it's not part of those screenshots. But as it is, it leaves everything to wild guessing.

I think you should be able to reproduce it with a tumbleweed image where you
select "SELinux"->"enforcing" in yast and then install the system. then boot
into the first snapshot named "after installation". 

thanks a lot people, i will check if i can give you more logs :)