Status: Closed (View Workflow)
Affects Version/s: 11.0.0.Alpha1
Fix Version/s: 11.0.0.Beta1
Component/s: Web (Undertow)
Steps to Reproduce:call migrate operation on web subsystem looking like this: <subsystem xmlns="urn:jboss:domain:web:2.2" default-virtual-server="default" native="false"> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/> <virtual-server name="default" enable-welcome-root="true"> <alias name="localhost"/> <alias name="example.com"/> </virtual-server> </subsystem>
JBEAP-10033 and discussion at JBEAP-10200 there was discovered issue related to virtual hosts migration which was hidden till now.
When migrating web -> undertow for migrating virtual hosts. In web there is on subsystem level default-virtual-server option, which per description corresponds more to the one in undertow default-host option on server level and currently it is migrated to it. Still in Undertow there is also default-virtual-host at undertow subsystem level which stays unchanged.
Now with capabilities implemented on Undertow subsystem it points out that it is actually invalid configuration as the default-virtual-host points to non existing host (in case of the original virtual server being named differently than default-host), resulting in server failing to start afterwards  without any migration warning shown.
The migration operation should update both default-virtual-host at subsystem level and default-host at server level.
As there is no migration warning and the resulting configuration causes server start to fail, marking as blocker.