Bug 1921777

Summary:

Migration toolkit for application Operator installation failing on OCP 4.6

Product:

OpenShift Container Platform

Reporter:

Shveta <sshveta>

Component:

Migration Tooling

Assignee:

John Matthews <jmatthew>

Status:

CLOSED NOTABUG

QA Contact:

Xin jiang <xjiang>

Severity:

high

Docs Contact:

Priority:

unspecified

Version:

4.6

CC:

amsharma, mokumar

Target Milestone:

---

Keywords:

TestBlockerForLayeredProduct

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2021-02-10 04:32:06 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
Ocp error	none

Description Shveta 2021-01-28 15:28:03 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. On Openshift 4.6 , Go to Operator hub and install Migration toolkit for applications.
2. Operator fails to install 
3.

Actual results:


Expected results:


Additional info:
logs 
====================

Starting executor with messaging server 172.30.9.43 as user jms-user
MTA_OPTS: -Xms512m -Xmx2048m -XX:+UseParallelOldGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:MaxMetaspaceSize=256m -XX:ParallelGCThreads=4 -Djava.util.concurrent.ForkJoinPool.common.parallelism=4 -XX:CICompilerCount=2 -XX:+ExitOnOutOfMemoryError
Changing to script home: /opt/mta-cli
Using MTA at /opt/mta-cli
> Migration Toolkit for Applications by Red Hat (MTA) CLI, version 5.1.2-SNAPSHOT.
[0m11:28:11,494 INFO  [org.jboss.windup.bootstrap.listener.GreetingListener] (Furnace Container )

Migration Toolkit for Applications (MTA) CLI, version [  ] - by Red Hat, Inc. [ https://developers.redhat.com/products/mta/overview/ ]

[0m

Migration Toolkit for Applications (MTA) CLI, version [  ] - by Red Hat, Inc. [ https://developers.redhat.com/products/mta/overview/ ]

[0m11:28:28,555 INFO  [org.jboss.windup.web.messaging.executor.ExecutorBootstrap] (main) Starting with arguments: [--messagingExecutor, --user, jms-user, --password, gthudfal, --host, 172.30.9.43, --connectionFactory, jms/RemoteConnectionFactory, --executorQueue, jms/queues/executorQueue, --statusUpdateQueue, jms/queues/statusUpdateQueue, --cancellationTopic, jms/topics/executorCancellation, --pingDir, /opt/mta-cli/ping, --immutableAddonDir, /opt/mta-cli/addons/]
[0m[0m11:28:28,564 INFO  [org.wildfly.naming] (main) WFNAM00025: org.jboss.naming.remote.client.InitialContextFactory is deprecated; new applications should use org.wildfly.naming.client.WildFlyInitialContextFactory instead
[0m[0m11:28:28,569 INFO  [org.wildfly.naming] (main) WildFly Naming version 1.0.11.Final
[0m[0m11:28:28,611 INFO  [org.wildfly.security] (main) ELY00001: WildFly Elytron version 1.10.4.Final
[0m[0m11:28:28,669 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
[0m[0m11:28:28,692 INFO  [org.jboss.remoting] (main) JBoss Remoting version 5.0.15.Final
[0m[31m11:28:28,909 SEVERE [org.jboss.windup.web.messaging.executor.ExecutorBootstrap] (main) Could not start messaging listener due to: WFNAM00018: Failed to connect to remote host: javax.naming.CommunicationException: WFNAM00018: Failed to connect to remote host [Root exception is java.net.ConnectException: Connection refused]
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:110) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:53) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.NamingProvider.getPeerIdentityForNamingUsingRetry(NamingProvider.java:105) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNamingUsingRetry(RemoteNamingProvider.java:91) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:189) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:188) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:60) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_282]
	at org.jboss.windup.web.messaging.executor.DefaultExecutorBootstrap.runServer(DefaultExecutorBootstrap.java:89) [windup-web-messaging-executor-impl-5.1.2-SNAPSHOT.jar:5.1.2-SNAPSHOT]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_282]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_282]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_282]
	at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_282]
	at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87) [furnace-proxy-2.28.4.Final.jar:2.28.4.Final]
	at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) [furnace-api-2.28.4.Final.jar:2.28.4.Final]
	at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103) [furnace-proxy-2.28.4.Final.jar:2.28.4.Final]
	at org.jboss.windup.web.messaging.executor.DefaultExecutorBootstrap_$$_jvstad0_ef.runServer(DefaultExecutorBootstrap_$$_jvstad0_ef.java) [windup-web-messaging-executor-impl-5.1.2-SNAPSHOT.jar:5.1.2-SNAPSHOT]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_282]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_282]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_282]
	at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_282]
	at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124) [furnace-proxy-2.28.4.Final.jar:2.28.4.Final]
	at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) [furnace-api-2.28.4.Final.jar:2.28.4.Final]
	at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97) [furnace-proxy-2.28.4.Final.jar:2.28.4.Final]
	at org.jboss.windup.server.WindupServerProvider_$$_jvstd5e_29.runServer(WindupServerProvider_$$_jvstd5e_29.java) [windup-server-provider-spi-5.1.2-SNAPSHOT-forge-addon.jar:5.1.2-SNAPSHOT]
	at org.jboss.windup.bootstrap.Bootstrap.run(Bootstrap.java:347) [windup-bootstrap-5.1.2-SNAPSHOT.jar:5.1.2-SNAPSHOT]
	at org.jboss.windup.bootstrap.Bootstrap.main(Bootstrap.java:113) [windup-bootstrap-5.1.2-SNAPSHOT.jar:5.1.2-SNAPSHOT]
Caused by: java.net.ConnectException: Connection refused
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [rt.jar:1.8.0_282]
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716) [rt.jar:1.8.0_282]
	at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:327) [xnio-nio-3.7.3.Final.jar:3.7.3.Final]
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:591) [xnio-nio-3.7.3.Final.jar:3.7.3.Final]
	at ...asynchronous invocation...(Unknown Source)
	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:599) [jboss-remoting-5.0.15.Final.jar:5.0.15.Final]
	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:565) [jboss-remoting-5.0.15.Final.jar:5.0.15.Final]
	at org.jboss.remoting3.ConnectionInfo$None.getConnection(ConnectionInfo.java:82) [jboss-remoting-5.0.15.Final.jar:5.0.15.Final]
	at org.jboss.remoting3.ConnectionInfo.getConnection(ConnectionInfo.java:55) [jboss-remoting-5.0.15.Final.jar:5.0.15.Final]
	at org.jboss.remoting3.EndpointImpl.doGetConnection(EndpointImpl.java:499) [jboss-remoting-5.0.15.Final.jar:5.0.15.Final]
	at org.jboss.remoting3.EndpointImpl.getConnectedIdentity(EndpointImpl.java:445) [jboss-remoting-5.0.15.Final.jar:5.0.15.Final]
	at org.jboss.remoting3.UncloseableEndpoint.getConnectedIdentity(UncloseableEndpoint.java:52) [jboss-remoting-5.0.15.Final.jar:5.0.15.Final]
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getFuturePeerIdentityPrivileged(RemoteNamingProvider.java:151) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.remote.RemoteNamingProvider.lambda$getFuturePeerIdentity$0(RemoteNamingProvider.java:138) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_282]
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getFuturePeerIdentity(RemoteNamingProvider.java:138) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentity(RemoteNamingProvider.java:126) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:106) [wildfly-naming-client-1.0.11.Final.jar:1.0.11.Final]
	... 30 more

Comment 1 Shveta 2021-01-28 17:18:43 UTC

Created attachment 1751776 [details]
Ocp error

Comment 2 Xin jiang 2021-01-29 02:36:34 UTC

The Component "Migration Tooling" is not for MTA produce.

Comment 3 Shveta 2021-01-29 03:00:15 UTC

Sorry I didn't know what else I can use . Can you please suggest ?

Comment 5 Shveta 2021-02-10 04:32:06 UTC

Hi Mohan , 


The issue seems to be on MTA side . We are tracking it here 
https://issues.redhat.com/browse/WINDUP-2976.

Closing this BZ.