If a conversion upgrades SELinux, SELinux itself will be mislabelled. If the guest boots with SELinux in enforcing mode, autorelabel will fail because /lib/libselinux.so.1 cannot be read.
If the guest has SELinux in enforcing mode, we need to set it to permissive mode to do the relabel, and put it back afterwards, presumably in rc.local.
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.6 and Red Hat does not plan to fix this issue the currently developed update.
Contact your manager or support representative in case you need to escalate this bug.
How would I reproduce it? I cannot reproduce it via 2 senarios:
1. Convert a guest registered to rhn
2. Upgrade SELinux
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.