Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Blocker
Fix Version/s: 7.1.0.DR18
Affects Version/s: 7.1.0.DR14
Component/s: Management, Security
Labels:
- eap71_alpha

Affects Testing:

Regression
CDW blocker:
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.1.0.GA
Workaround:

Workaround Exists
Workaround Description:

Hide

Add attribute username="$local" to the slave host's <domain-controller><remote> element, e.g. in host-slave.xml:

<remote security-realm="ManagementRealm" username="$local">

Show
Add attribute username="$local" to the slave host's <domain-controller><remote> element, e.g. in host-slave.xml: <remote security-realm="ManagementRealm" username="$local">
Git Pull Request:
https://github.com/wildfly/wildfly-core/pull/2363
Steps to Reproduce:
Hide

1. Start a controller host with default host-master.xml configuration:

./dc/bin/domain.sh --host-config=host-master.xml -Djboss.host.name=DC

2. Start a slave host with default host-slave.xml configuration (on the same machine):

./hc1/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=10099 -Djboss.host.name=HC1
Show
1. Start a controller host with default host-master.xml configuration: ./dc/bin/domain.sh --host-config=host-master.xml -Djboss.host.name=DC 2. Start a slave host with default host-slave.xml configuration (on the same machine): ./hc1/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management. native .port=10099 -Djboss.host.name=HC1

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Upon attempting to start a slave host with default host-slave.xml connecting to master host with default host-master.xml, the following error is produced and slave will not boot:

[mjurc@tigris 7.1.0.DR14]$ ./hc1/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=10099 -Djboss.host.name=HC1
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /home/mjurc/testing/eap/7.1.0.DR14/hc1

  JAVA: /usr/java/latest/bin/java

  JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

09:18:32,658 INFO  [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta6-redhat-1
09:18:32,839 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
[Host Controller] 09:18:33,269 INFO  [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta6-redhat-1
[Host Controller] 09:18:33,565 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1-redhat-1
[Host Controller] 09:18:33,617 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Beta9-redhat-1) starting
[Host Controller] 09:18:34,286 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=hc1/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 09:18:34,288 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 09:18:34,345 INFO  [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.1.0.Beta31-redhat-1
[Host Controller] 09:18:34,377 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.5.0.Beta2-redhat-1
[Host Controller] 09:18:34,385 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.5.0.Beta2-redhat-1
[Host Controller] 09:18:34,438 INFO  [org.jboss.as.patching] (MSC service thread 1-7) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none
[Host Controller] 09:18:34,449 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.0.Beta19-redhat-1
[Host Controller] 09:18:34,469 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-8) WFLYDM0111: Keystore /home/mjurc/testing/eap/7.1.0.DR14/hc1/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
[Host Controller] 09:18:34,519 INFO  [org.jboss.as.remoting] (MSC service thread 1-7) WFLYRMT0001: Listening on 127.0.0.1:10099
[Host Controller] 09:18:34,848 WARN  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote://127.0.0.1:9999: java.lang.IllegalStateException: WFLYHC0043: Unable to connect due to authentication failure.
[Host Controller] 	at org.jboss.as.host.controller.RemoteDomainConnectionService.rethrowIrrecoverableConnectionFailures(RemoteDomainConnectionService.java:674)
[Host Controller] 	at org.jboss.as.host.controller.RemoteDomainConnectionService.register(RemoteDomainConnectionService.java:293)
[Host Controller] 	at org.jboss.as.host.controller.DomainModelControllerService.connectToDomainMaster(DomainModelControllerService.java:918)
[Host Controller] 	at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:672)
[Host Controller] 	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:337)
[Host Controller] 	at java.lang.Thread.run(Thread.java:745)
[Host Controller] Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
[Host Controller]    JBOSS-LOCAL-USER: javax.security.sasl.SaslException: Server rejected authentication
[Host Controller]    DIGEST-MD5: javax.security.sasl.SaslException: Server rejected authentication
[Host Controller] 	at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:108)
[Host Controller] 	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:395)
[Host Controller] 	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:241)
[Host Controller] 	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
[Host Controller] 	at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
[Host Controller] 	at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
[Host Controller] 	at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
[Host Controller] 	at ...asynchronous invocation...(Unknown Source)
[Host Controller] 	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:465)
[Host Controller] 	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:427)
[Host Controller] 	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:415)
[Host Controller] 	at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:177)
[Host Controller] 	at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:113)
[Host Controller] 	at org.jboss.as.host.controller.RemoteDomainConnection.lambda$openConnection$0(RemoteDomainConnection.java:223)
[Host Controller] 	at org.wildfly.common.context.Contextual.runExceptionAction(Contextual.java:108)
[Host Controller] 	at org.wildfly.security.auth.client.AuthenticationContext.run(AuthenticationContext.java:296)
[Host Controller] 	at org.jboss.as.host.controller.RemoteDomainConnection.openConnection(RemoteDomainConnection.java:223)
[Host Controller] 	at org.jboss.as.host.controller.RemoteDomainConnection$InitialConnectTask.connect(RemoteDomainConnection.java:592)
[Host Controller] 	at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
[Host Controller] 	at org.jboss.as.host.controller.RemoteDomainConnection.connect(RemoteDomainConnection.java:147)
[Host Controller] 	at org.jboss.as.host.controller.RemoteDomainConnectionService.register(RemoteDomainConnectionService.java:288)
[Host Controller] 	... 4 more
[Host Controller] 	Suppressed: javax.security.sasl.SaslException: Server rejected authentication
[Host Controller] 		at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:716)
[Host Controller] 		at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:560)
[Host Controller] 		at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
[Host Controller] 		at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
[Host Controller] 		at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
[Host Controller] 		at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
[Host Controller] 	Suppressed: javax.security.sasl.SaslException: Server rejected authentication
[Host Controller] 		at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:716)
[Host Controller] 		at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:560)
[Host Controller] 		at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
[Host Controller] 		at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
[Host Controller] 		at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
[Host Controller] 		at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
[Host Controller] 
[Host Controller] 09:18:34,849 WARN  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain.
[Host Controller] 09:18:34,849 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect
[Host Controller] 09:18:34,850 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99
[Host Controller] 09:18:34,867 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0050: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Beta9-redhat-1) stopped in 13ms
[Host Controller] 
09:18:35,188 INFO  [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) WFLYPC0011: Process 'Host Controller' finished with an exit status of 99
09:18:35,189 INFO  [org.jboss.as.process] (Thread-8) WFLYPC0017: Shutting down process controller
09:18:35,190 INFO  [org.jboss.as.process] (Thread-8) WFLYPC0016: All processes finished; exiting

This issue renders managed domain unusable out of the box. This is a regression introduced in JBoss EAP 7.1.0.DR14.

Master log with trace level logging for remoting subsystem is attached.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

host-controller.log
39 kB
2017/03/17 5:05 AM

is cloned by

WFCORE-2731 Slave hosts with default host-slave.xml configuration are not able to connect to master host with default host-master.xml configuration

Resolved

is incorporated by

JBEAP-10508 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta21

Closed

is related to

JBEAP-10084 Backward compatibility: Slave hosts (default host-slave.xml from EAP 7.0.0) are not able to connect to master host (default host-master.xml from EAP 7.0.0)

Closed

JBEAP-10921 Remove username="$local" workaround from default domain host slave configuration

Closed

Assignee:: Brian Stansberry

Reporter:: Michal Jurc

Votes:: 0 Vote for this issue

Watchers:: 11 Start watching this issue

Created:: 2017/03/17 4:26 AM

Updated:: 2024/09/02 4:56 PM

Resolved:: 2017/05/11 4:23 AM

Details

Description

Attachments

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates