[ https://issues.redhat.com/browse/WFCORE-4882?page=com.atlassian.jira.plug... ] Chao Wang updated WFCORE-4882: ------------------------------ Description: Broken 'domain.xml' after migration of <host-scoped-roles> leading to 'Boostrap error' in HAL. A broken domain configuration {code:xml} <host-scoped-roles> <role name="custom-role-name" base-role="Administrator"> </role> </host-scoped-roles> {code} This broken configuration doesn't bother the old HAL, so user only see the issue from HAL after the migration. The correct one should be: {code:xml} <host-scoped-roles> <role name="dbaish" base-role="Administrator"> <host name="master"/> </role> </host-scoped-roles> {code} https://github.com/wildfly/wildfly-core/blob/11.0.0.Final/server/src/main... show minOccurs="1", which is incorrect, the minOccurs should be 0 here. was: When migrating a domain configuration from JBoss EAP 7.1.6 having a broken {{<host-scoped-roles>}} configuration, the resulting {{domain.xml}} on EAP 7.2 is broken as well. JBoss EAP 7.1 is relaxed during accessing the HAL and simply ignores the broken configuration, whereas JBoss EAP 7.2 will not allow access to the HAL and report a *_Bootstrap error_*. The {{jboss-server-migration.[sh|bat]}} should identify this broken configuration and *deny* the migration of it. -- This message was sent by Atlassian Jira (v7.13.8#713008)