Hipchat Server networking malfunctions after migrating the Virtual Machine to a new VMWare 6 cluster
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
This is for an outdated version of Hipchat Server
This article applies to a version of Hipchat Server which will be deprecated soon. After that period the version will no longer be supported.
You should upgrade to a more recent version of Hipchat Server as soon as you can to take advantage of new features, and security and bug fixes.
問題
After migrating a Hipchat Server virtual machine from a VMWare ESX 5.1 cluster to a new cluster running VMware ESX 6.0 U2, networking on the Hipchat Server stops working properly.
診断
環境
- Hipchat Server 1.4.1 and earlier
Diagnostic Steps
- The local IP address of the server can be reached with a ping; the gateway IP address cannot not be reached with a ping.
- Bringing down the ethernet adapter on the Hipchat Server (eth0) and rebooting the Virtual Machine does not resolve the issue.
Steps to reproduce
- Upgrade the Hipchat Server from version 1.2.x to version 1.4.1.
- Perform the migration to VMWare ESX 6.0 US
原因
The Hipchat Server Virtual Machine was not shut down completely prior to migrating it to the new cluster.
ソリューション
- Perform a complete shutdown of the Hipchat Server Virtual Machine
- Migrate the Virtual Machine using tools such as vMotion to the new cluster
- Restart the Hipchat Server Virtual Machine