My Oracle Support Banner

When Upgrading PCA Management Node, secondary MN Becomes Unresponsive After PXE Boot (Doc ID 2273824.1)

Last updated on JUNE 12, 2017

Applies to:

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

Symptoms

During upgrade of PCA from 2.0.1 to 2.0.5, you noticed that the "slave" MN stops after booting up with PXE

In Master MN (usually ovcamn05, "MN05") ovca.log:

[2017-05-23 15:00:24 5359] DEBUG (ilom:35) Command output is set /HOST boot_device=pxe
Set 'boot_device' to 'pxe'

[2017-05-23 15:00:24 5359] DEBUG (ilom:23) Command output is show /System power_state

/System
Properties:
power_state = On

[2017-05-23 15:00:24 5359] DEBUG (ilom:26) targetRegex is(?Ppower_state) = (?P.*?)[\n\r\f\v]+
[2017-05-23 15:00:24 5359] DEBUG (ilom:139) Inside ILOM reset workaround; reset&start /System ignoring output
[tguo@amomv0027 ovca]$

 

It is seen that MN05 was trying to restart MN06, thus MN06 should have restarted and boot up with PXE. On the slave/to-be-upgraded MN console, an error message is issued:

FATAL ERROR: Management system setup failed


The update task status on master node shows as:

[root@ovcamn05r1 log]# ovca-updater -m update -l
Mgmt Node IP Update Started Update Ended Elapsed
192.168.4.4 2017-05-22 08:55:59 ------------------- 1:03:24



The /tmp/install.log (ovca's installation log) on MN06 shows:

[05/23/2017 13:51:07 3338] DEBUG (connectionpool:289) "DELETE /xms/resource/rest/xmsSession HTTP/1.1" 200 None
P addresses of both the IO directors.. Pls check the hardware connections to OPUS switch
The ping result of IO director1 is 0
master has created clouds
Seen exception cannot ping the IP addresses of both the IO directors.. Pls check the hardware connections to OPUS switch
The ping result of IO director1 is 0
master has created clouds
Traceback (most recent call last):
 File "/usr/sbin/pca-factory-init", line 366, in
  main()
 File "/usr/sbin/pca-factory-init", line 326, in main
  init_xms_spooler(master_ip, my_hostname)
 File "/usr/sbin/pca-factory-init", line 138, in init_xms_spooler
  raise Exception("FATAL ERROR: Could not reach master management node to complete cloud creation.")
Exception: FATAL ERROR: Could not reach master management node to complete cloud creation.
[05/23/2017 13:51:07 3338] DEBUG (connectionpool:289) "DELETE /xms/resource/rest/xmsSession HTTP/1.1" 200 None
FATAL ERROR: Management system setup failed

 

Changes

 Upgrading PCA from 2.0.1 to 2.0.5.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.