[ PCA 2.3.1 Upgrade ] Upgrade fails on the first node with "Error, some other host (XX:XX:XX:XX:XX:XX) already uses address 192.168.140.4. "

(Doc ID 2315844.1)

Last updated on OCTOBER 17, 2017

Applies to:

Private Cloud Appliance - Version 2.1.1 and later
Linux x86-64

Symptoms

On Oracle Private Cloud Appliance, when upgrading to release 2.3.1, after the first node has finished reinstalling its operating system and boots again, it stops at the following step in its /tmp/install.log :

none on /sys/kernel/debug type debugfs (rw)
/nfs/shared_storage/mgmt_image on /mnt type none (rw,bind)
/nfs/shared_storage/ovm_image on /mnt/ovm_server type none (rw,bind)
/nfs/shared_storage/hmp_image on /mnt/hmp type none (rw,bind)
192.168.40.1:/export/MGMT_ROOT on /nfs/shared_storage type nfs
(rw,vers=3,addr=192.168.40.1)
192.168.40.1:/export/Yum on /nfs/shared_storage/yum type nfs
(rw,vers=3,addr=192.168.40.1)
192.168.40.1:/export/Incoming on /nfs/shared_storage/incoming type nfs
(rw,vers=3,addr=192.168.40.1)
Bringing up bond0 for OVMM install...
Determining if ip address 192.168.140.4 is already in use for device bond0...
Error, some other host (00:13:97:93:B0:01) already uses address 192.168.140.4.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms