Unable to change staging configuration if the remote environment no longer exists

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.2.10 EE GA1, 6.2.X EE, 7.0.0 M3
• Fix Version/s: 6.2.4 CE GA5, 6.2.X EE, 7.0.0 M3
• Component/s: Content Publishing > Staging
• Labels:
  • liferay-fixpack-portal-69-6210
• Branch Version/s:
  6.2.x
• Backported to Branch:
  Committed
• Story Points: 17
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/21710

1. Create staged site on http://172.16.21.247:8090
2. Create initial remote site on http://172.16.21.247:8080
3. Enable remote staging
4. Drop the database connected to the remote site on http://172.16.21.247:8080
5. Create a new Portal on a machine with a different address/port, appending the tunnel.servlet.hosts.allowed and axis.servlet.hosts.allowed properties with the machine's address (i.e. 172.16.17.43)
6. Create a user that coincides with the user who is publishing on the staged server (i.e. [email protected])
7. Attempt to modify the staged site's connection to the new remote site (site id 10462) on the new address/port (i.e. http://172.16.17.43:9080)
Expected Result: Changes are successfully implemented.
Actual Result: We are unable to change the Staging settings. The Portal continues to reference the old
Your request failed to complete.
Could not connect to address http://172.16.21.247:9080. Please verify that the specified port is correct and that the remote server is configured to accept requests from this server.
8. When trying to disable staging, the same message appears:
Your request failed to complete.
Could not connect to address http://172.16.21.247:9080. Please verify that the specified port is correct and that the remote server is configured to accept requests from this server.
Branch:
commit 45ba28f25b4d91783623bc4696d81c97d53cb15c
Issue is reproduced
Master:
commit 4f01c5e20b5113b5422e159828d699ce0c14998b
Errors during startup. Cannot test.