Cannot configure a static IP address on Hipchat Server 1.4.1
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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.
*Except Fisheye and 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.
Problem
The admin of Hipchat Server cannot configure the static IP address of the instance using the steps mentioned in the official documentation for Configuring a static IP address after deploying the brand new OVA for 1.4.1
Diagnosis
Environment
- Fresh installations of the Hipchat Server 2, build 1.4.1 OVA.
Steps to Reproduce
Deploy a brand new Hipchat Server 1.4.1 OVA on the hypervisor.
Attempt to configure the static IP address of the Hipchat Server by following the steps in the documentation
hipchat network -m static -i <IP> -s <netmask> -g <gateway> -r <DNS>
Confirm the changes by running the following command:
hipchat network --show
Actual Results
- The command above reveals that the changes to the network are not applied.
Expected Results
- The static IP address settings are applied.
Cause
- New installations of Hipchat Server 2, build 1.4.1 are missing the /etc/init.d/ovflan file, which is required to complete the network address changes.
Workaround
Applying the workaround below to Hipchat Server versions newer than build 2.0.6 may trigger the following bug: - HCPUB-2588Getting issue details... STATUS
There are 3 possible workarounds available to address this, depending on the environment where the Hipchat Server OVA is deployed:
Option1: If the Hipchat Server has Internet Access
Log in to the Hipchat Server command line console and run the following commands:
sudo dont-blame-hipchat
wget https://s3.amazonaws.com/uploads.hipchat.com/10804/3712034/ddZc6NMKeQm8orE/ovflan -O /etc/init.d/ovflan
chmod a+x /etc/init.d/ovflan
..then proceed with configuring a static IP address for the Hipchat server as usual.
Option 2: If the Hipchat Server is on an isolated network with NO Internet Access
Download the ovflan script from this URL to a local workstation:
https://s3.amazonaws.com/uploads.hipchat.com/10804/3712034/ddZc6NMKeQm8orE/ovflan
Copy the ovflan script to the Hipchat server using a preferred file transfer tool. For workstations with the ability to scp a file to the server, the command will look like the following:
scp /path/to/ovflan admin@local.hipchat.server:/home/admin
...where "/path/to/ovflan" is the actual path to where the ovflan file was saved and "local.hipchat.server" is the actyak Fully Qualified Domain Name (FQDN) of the Hipchat Server.
Log in to the Hipchat Server's command line console and run the following commands:
sudo dont-blame-hipchat
cp /home/admin/ovflan /etc/init.d/
chmod a+x /etc/init.d/ovflan
...then proceed with configuring a static IP address for the Hipchat server.
Option 3: If the Hipchat Server is not Accessible at all over the network:
Log in to the local console of the Hipchat Server. VirtualBox and VMWare, for example, both provide this capability.
Run the following command to change to the root user:
sudo dont-blame-hipchat
In a preferred text editor (nano or vim for example), please open and edit the /etc/network/interfaces file and add the desired networking configurations.
Below is an example of what a static IP address configuration will look like. Please substitute the respective values in the example below for the actual IP, netmask, gateway, and dns server for the environment in question:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 172.16.53.138
netmask 255.255.255.0
gateway 172.16.53.2
dns-nameservers 8.8.8.8
Save the file and copy it to /home/admin/config/etc/network/interfaces so that you changes persist over server reboots or upgrades.
Run the hipchat network command so that the changes take effect. Use the values for ip address, gateway, netmask, and dns servers that were used in the file edit above, for example:
hipchat network -m static -i 172.16.53.138 -s 255.255.255.0 -g 172.16.53.2 -r 8.8.8.8
Once this is done, and the system is accessible over the network, please proceed with downloading and / or copying the ovflan file using either of the first two methods above to the Hipchat Server so that any future networking changes will take effect properly.
Resolution
This is a known bug in the Hipchat Server 1.4.1 release that was fixed in 1.4.2.
- HCPUB-896Getting issue details... STATUS