Loading...

XML

Word

Printable

Steps to Reproduce:
Hide

Edit the at JBoss-Product-Stability and JBoss-Product-Minimum-Stability at https://github.com/wildfly/wildfly/blob/eaee3db3047012378421bcf6ae2fb92410c1df02/ee-feature-pack/product-conf/pom.xml#L40-L41 and change them to use default.

Build the project with: mvn clean install -X -DskipTests -Dgalleon.fork.embedded=false
Show
Edit the at JBoss-Product-Stability and JBoss-Product-Minimum-Stability at https://github.com/wildfly/wildfly/blob/eaee3db3047012378421bcf6ae2fb92410c1df02/ee-feature-pack/product-conf/pom.xml#L40-L41 and change them to use default. Build the project with: mvn clean install -X -DskipTests -Dgalleon.fork.embedded=false
Git Pull Request:
https://github.com/wildfly/wildfly-core/pull/5928

Although the issue is in WildFly Core, it can only be reproduced with WildFly without modifying any source code to force it.

When we configure the server to manage only one permissible stability level, the server cannot detect the --stability argument.

That leads to an issue where Galleon gets stuck and never ends up provisioning the server.