ServerView Resource Orchestrator Cloud Edition V3.0.0 Reference Guide for Infrastructure Administrators (Resource Management)

4.5 Operations for Images or Cloning Images

After Collection of Images Fails, Images Not Registered in the Image Pool Remain on VM Management Software.

[Description]

When image creation fails due to the following problems during image collection, images which are not registered in the image pool may remain on VM management software. In this case, the following messages will be output in the event log.

• Occurred Problems

  • System failure, or reboot of the admin server or manager

  • Server switchover in which managers are operating using the HA function of cluster software or server virtualization software

• Messages

  • FJSVrcx:ERROR:61143:creating cloning image:failed

  • FJSVrcx:ERROR:67397:failed to create image. detail=(clone VM_guest_name:task result error,vmerrno=104,ip=IP_address)

  • FJSVrcx:ERROR:67397:failed to create image. detail=(Message,vmerrno=104,ip=IP_address,host=VM_host_IP_address)

  • FJSVrcx:ERROR:67397:failed to create image. detail=(PowerShell script execution error : create_image:create image failed. See details in the job result in System Center Virtual Machine Manager.,vmerrno=518,ip=IP_address,host=VM_host_IP_address)

For details on these messages, refer to "Message number 67397" in this manual, and "Message number 61143" in the "Messages VE".

[Corrective Action]

Make sure that the manager is running, and use the following procedure for restoration:

1. Check the resource name related to the error message above with the event log on the ROR console. The image name is displayed for the resource name of "Message number 61143" in the "Messages VE".

2. Wait until a "Message number 21161" containing the image name confirmed in 1. is output in the event log. This message displays the image name and generation.

3. Display the VM management console and check if the image of Image_name@Version exists.

4. If there was an image in 3., delete it from the VM management console.

   For details on how to delete images, refer to the server virtualization software manual.

5. Wait until a "Message number 21162" containing the image name deleted in 4. is output in the event log. After that, perform the collection of the image again.

   
   

When Collecting a Cloning Image, "Message number 21161" or "Message number 21162" is Displayed.

[Description]

When collection of a cloning image is performed for an L-Server with the virtual L-Server of the Hyper-V VM type, one of the following messages may be output in the event log.

The VM guest name whose name starts with "!temp_ror" is displayed for obj.

• FJSVrcx:INFO:21161:obj:VM guest is detected.

• FJSVrcx:INFO:21162:obj:VM guest is lost.

For details on the messages, refer to "Message number 21161" and "Message number 21162".

[Corrective Action]

No action is necessary.

When Creation of an L-Server Specifying Images Fails and "Message number 67390" is Displayed.

[Description]

Creation of an L-Server specifying images fails, and the following message is output.

FJSVrcx:ERROR:67390:creating VM guest failed. detail=(customize VM_guest_name:task result error,vmerrno=104,ip=IP_address)

For details on the message, refer to "Message number 67390".

[Corrective Action]

The OS type specified for images when creating L-Servers and the OS type of the installed OS may be different.

The OS type for images is inherited from the L-Server that is the source of image collection. Check if the OS type of the L-Server that is the source of collection and the installed OS type are the same.

If the OS types are not the same, collect images again after configuring the correct OS type of L-Server as the source for collection, and create an L-Server.

However, the type of OS for an L-Server created specifying images cannot be changed. When the OS type of the L-Server cannot be changed, use server virtualization software to collect images again after configuring the correct OS type for the VM guest, and then create the L-Server.

Delete collected images that have the wrong configurations.

For details on how to change the OS type of an L-Server, refer to "11.2.1 Modifying Specifications" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
For details on how to change the OS types of VM guests using server virtualization software, refer to the server virtualization software manual.

When Collecting a Cloning Image on an L-Server with the VM Type "RHEL-Xen","Message number 67999" is Displayed, and Cloning Image Collection may Fail.

[Description]

When collecting a cloning image on an L-Server with the VM Type "RHEL-Xen", the following message is displayed, and cloning image collection may fail.

FJSVrcx:ERROR:67999:internal error, database conflict

[Corrective Action]

The character string specified for the -name option when collecting the cloning image may exceed the specifiable number of characters. Specify the name correctly and perform the operation again.

For details on the -name option, refer to "1.4.1 rcxadm image".