-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
High
-
None
-
Affects Version/s: JCMA - 1.9.0, JCMA - 1.9.7, JCMA - 1.12.4
-
Component/s: Viper CMAs - Australia
-
28
-
Minor
-
52
Issue Summary
It seems like the connectivity tester (network preflight check) doesn't support outbound proxy settings. When the outbound proxy setting is configured in the Jira Server, every check is green in JCMA but not required URLs check (see attachment). Due to this, the run button is disabled and migration can not be started.
This is reproducible on Data Center: 
Steps to Reproduce
- Make sure the Jira server is behind the proxy.
- Configure the outbound http/https proxy setting as mentioned in the article
- Create a migration plan and run the migration.
- All the preflight checks will be completed except for the network preflight.
Expected Results
Network checks should be completed and appear green. The 'run' button should be enabled too.
Actual Results
The below exception is thrown in the atlassian-jira.log file:
2023-06-26 17:06:00,229+0200 ForkJoinPool.commonPool-worker-3 WARN e97712 1023x1136196x1 1dldy4v 208.127.128.84,10.44.67.202,127.0.0.1 /rest/migration/latest/app [c.a.j.migration.preflight.SocketConnectivityTester] Error opening connection at https://rps--prod-west2--migration-catalogue--migration-storage-v2.s3.us-west-2.amazonaws.com: java.net.SocketTimeoutException: connect timed out at java.base/java.net.PlainSocketImpl.waitForConnect(Native Method) at java.base/java.net.PlainSocketImpl.socketConnect(Unknown Source) at java.base/java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.base/java.net.SocksSocketImpl.connect(Unknown Source) at java.base/java.net.Socket.connect(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.connect(Unknown Source) at java.base/sun.net.NetworkClient.doConnect(Unknown Source) at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source) at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source) at java.base/sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source) at java.base/sun.net.www.protocol.https.HttpsClient.New(Unknown Source) at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source) at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source) at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source) at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source) at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source) at com.atlassian.jira.migration.preflight.SocketConnectivityTester.isReachable(SocketConnectivityTester.kt:19)
Workaround
- Navigate to ${JIRA_URL}/secure/admin/jira/views/SiteDarkFeatures!default.jspa
- Add the below dark feature flag to disable the network preflight.
com.atlassian.jira.migration.disable.network-health-check
!Attention: This workaround is recommended only after ensuring that all required URLs (listed in the document below) have been whitelisted on the proxy/firewall and are accessible from the server/DC.
