Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2227955.1
Update Date:2017-01-28
Keywords:

Solution Type  Problem Resolution Sure

Solution  2227955.1 :   CD-ROM Reimage to the BDA 4.5 Base Image Fails with "makebdaimage: Invalid BDADeploy json file : makebdaimage: deploy is not a valid v1 or v2 network config file"  


Related Items
  • Big Data Appliance X4-2 Hardware
  •  
Related Categories
  • PLA-Support>Eng Systems>BDA>Big Data Appliance>DB: BDA_EST
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-14057197351>

Applies to:

Big Data Appliance X4-2 Hardware - Version All Versions and later
Linux x86-64

Symptoms

Performing CD-ROM reimage to the BDA 4.5 base image using: Steps For Re-imaging a Single BDA Server Using CD-ROM Redirection (Doc ID 1559505.1) fails when running makebdaimage.

The failure looks like below when running the makebdaimage command from Node 1 to reimage node <x>. 

# ./makebdaimage BDABaseImage-ol6-4.5.0_RELEASE.iso deploy <x>
  
makebdaimage: BDABaseImage-ol6-4.5.0_RELEASE.iso deploy <x>
BDABaseImage-ol6-4.5.0_RELEASE.iso: OK
./json-select: "deploy" No such file.
./json-select: "deploy" No such file.
cp: target '/tmp/server<x>-BDABaseImage/Extras/network.json' is not a directory
tar: Extras/network.json: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
./json-select: "config" No such file.
makebdaimage: Invalid BDADeploy json file : makebdaimage: deploy is not a valid v1 or v2 network config file

Additionally it is observed that the rest of the nodes in the rack have been reimaged to the original factory ship network settings. This is determined by the content of "/opt/oracle/bda" on the rest of the rack nodes.

Output showing reimage to factory settings looks like:

# ls -l /opt/oracle/bda
  
total 64
-rwxr-xr-x 1 root root 2667 May 18 2016 BdaShip.json
-rwxr-xr-x 1 root root 2 May 18 2016 BDCS_VERSION
drwxr-xr-x 2 root root 4096 Jan 13 08:20 bin
drwxr-xr-x 3 root root 4096 Jan 13 08:14 cloud
drwxr-xr-x 2 root root 4096 Jan 13 08:19 compmon
-rw-r--r-- 1 root root 1551 Jan 13 08:20 factory_serial_numbers
drwxr-xr-x 2 root root 4096 Jan 13 08:14 firmware
drwxr-xr-x 2 root root 4096 Jan 13 08:14 Infiniband
drwxr-xr-x 2 root root 4096 Jan 13 08:14 install
drwxr-xr-x 2 root root 4096 Jan 13 08:14 lib
drwxr-xr-x 2 root root 4096 Jan 27 03:43 network
-rwxr-xr-x 1 root root 9023 May 18 2016 networkshipfull.json
-rw-r--r-- 1 root root 4130 Jan 17 03:51 networkship.json

Cause

It is not possible to CD-ROM reimage to original factory ship network settings following Steps For Re-imaging a Single BDA Server Using CD-ROM Redirection (Doc ID 1559505.1).

In the case here the rest of the rack was individually reimaged to the original factory ship network settings via: The "Instructions for Re-Imaging a Single BDA Server" section of: Oracle Big Data Appliance Base Image Version 4.5.0 for New Installations or Reprovisioning Existing Installations on Oracle Linux 5 (Doc ID 2174219.1).  However one node did not reimage due to a corrupt/bad USB. Once the USB was restored, however, the node could only boot into rescue mode.  It is not possible to CD-ROM reimage the node to original factory ship settings using: 1559505.1.

 

Solution

To reimage to original factory ship network settings on a node which can only be booted into rescue mode see: How to Reimage a BDA Server in Rescue Mode to Original Factory Ship Network Settings for 4.5 and Lower Base Images (Doc ID 2227956.1).


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback