Revised error messages
The following table describes the error messages that are revised in this release.
Revised error messages in BMC Bladelogic Server Automation
Revised error messages in BMC BladeLogic Server Automation
Scenario | Error message in version 4.1 | Revised error message in 4.5 |
|---|---|---|
RSCD Agent version | Error: VG creation failed: | Could not fetch System Information for server rj-1. BladeLogic (BSA) Appserver version: Suggested action: Please make sure that the BladeLogic (RSCD) (or is compatible) with the BladeLogic (BSA) Application Server version. |
Invalid URI : | Root Cause Info: | Could not connect to BladeLogic (BSA) Webservice Suggested action: Please make sure that the BladeLogic Also, please make sure that the BBSA configuration |
Invalid web services or | Root Cause Info: | Could not connect to BladeLogic (BSA) Suggested action: Please make sure that the BladeLogic (BSA) Webservice is running |
USP Job fail: BSA took Error 65: | SOI remains in Provisioning state | Could not connect to the BladeLogic Suggested action: Please make sure that the BladeLogic (BSA RSCD) Agent |
Software | Root Cause Info: Severity: CRITICAL Error: BBSA returned the following unknown error code: Root Cause Info: | Failed to install software Deploy_SSH on server sup-rj-4. Suggested action: Please check BlPackage referenced in job: |
VM Customization | Error: BBSA returned the following unknown error code: | Failed to customize the cloned Server: rj-11 on Virtual Cluster: cluster_1, Virtual Center: aus-clm-pod2-wt-vc.bmc.com Suggested action: Please check the information specified in Virtual Guest Package VMW-W2k3-Wrong-Key in BSA - E.g. Product Keys, Server Domain etc. You can also refer to BSA job: rj-11_VG_Job_1414578860623 logs for more information |
BSA AppServer is | Transaction ID: 44649a69-8c40-4fb8-8a0e-e0bd8d73497e | Could not connect to BladeLogic (BSA) Webservice https://bmcstrykerclmonbmc:10843/. Suggested action: Please make sure that the BladeLogic (BSA) Webservice is running and reachable from the CLM Platform Manager. Also, please make sure that the BBSA configuration (specifically Host, Port and Protocol) under Providers workspace (in the CLM Administration Console) is correct. |
Revoked privileges for | Error: VG creation failed:Could not find | Authentication failed while connecting to the BladeLogic (BSA) webservice: https://bmcstrykerclmonbmc:10843/. BSA error: Authentication failure: please verify user credentials. Suggested action: Please specify correct value for BBSA_PASSWORD under Providers workspace (in the CLM Administration Console) or in providers.json. Also, please verify if the user BLAdmin is enabled in BSA. |
Incorrect credentials | "errorCause" : "INTERNAL_PROVIDER_FAILURE: | Authentication failed while connecting to the BladeLogic (BSA) webservice: https://bmcstrykerclmonbmc:10843/. BSA error: Authentication failure: please verify user credentials. Suggested action: Please specify correct value for BBSA_PASSWORD under Providers workspace (in the CLM Administration Console) or in providers.json. Also, please verify if the user BLAdmin is enabled in BSA. |
Invalid RSCD or | Root Cause Info: | Failed to create server: sup-rj-20. Could not query the target infrastructure information for creating the server from BladeLogic (BSA). Suggested action: Please make sure that you have distributed the Configuration Objects for VMWare. Also make sure that appropriate permissions are configured in the BladeLogic (BSA RSCD) Agent exports/users/users.local file on the server where you have distributed the Configuration Objects. |
Unable to | Error: VG creation failed:BBSA job run log items: | Failed to create server: rj-13 on Virtual Cluster: cluster_1, Virtual Center: aus-clm-pod2-wt-vc.bmc.com. VM folder path mentioned in the BSA Virtual Guest Package VMW-W2k8-64B-20GB does not exist on the Virtual Center. Suggested action: Please specify a valid VM folder path in the package. You can also refer to BSA job: rj-13_VG_Job_1414589314744 logs for more information |
VG creation failed: | BBSA returned the following unknown error code: BMC-BSA-99999999. | Failed to create server: rj-16 on Virtual Cluster: cluster_1, Virtual Center: aus-clm-pod2-wt-vc.bmc.com. Number of devices (Network Interfaces/Disks) specified in the Blueprint or BSA Virtual Guest Package VMW-W2k8-64B-20GB exceeds the maximum supported. Suggested action: Please try to reduce the number of devices and try again. You can also refer to BSA job: rj-16_VG_Job_1414667382410 logs for more information |
Invalid or Corrupt software package | Transaction ID: 78b971e9-679d-4c75-81ca-fa0e1a8f4c86 |
|
Revised error messages in Tags
Scenario | Error message in version 4.1 or earlier | Revised error message in 4.5 |
|---|---|---|
Network Container | Error: Policy Engine cannot match the tags on filtered | Error: System could not match the tags on eligible Network Containers with either of the Tenant or the tags specified in the Service Blueprint. Error Resolution: Please verify that the Service Blueprint, Tenant and Network Container(s) are tagged appropriately.You can see the Platform Manager logs for more details on Placement. |
Compute Pool tag is | Error: Policy Engine cannot match the tags on filtered | Error: System could not match the tags on eligible Compute Pools(Virtual Cluster) with either of the Tenant or the tags specified in the Service Blueprint.
Error Resolution: Please verify that the Service Blueprint, Tenant and Compute Pools(Virtual Cluster) are tagged appropriately.You can see the Platform Manager logs for more details on Placement. |
VDR tag is missing | Error: Policy Engine cannot match the tags on filtered Virtual Disk Repository Pools with tags on Network Containers or Tenants or the tags in the Blueprint. | Error: System could not match the tags on filtered Compute Pools(Virtual Disk Repository) with either of the Tenant or the tags specified in the Service Blueprint. Error Resolution: Please verify that the Service Blueprint, Tenant and the Compute Pools(Virtual Disk Repository) are tagged appropriately.You can see the Platform Manager logs for more details on Placement. |
Network tag is missing | Error: Policy Engine could not match the tags on filtered Logical Network with either of the Tenant or the tags in the Blueprint. | Error: System could not match the tags on filtered Network with either of the Tenant or the tags in the Blueprint. Error Resolution: Please verify that the Service Blueprint, Tenant and Network are tagged appropriately.You can see the Platform Manager logs for more details on Placement. |
If Virtual DataStorePool | Severity: MAJOR Error: Could not retrieve any Virtual Datastore | Error: Cannot find any Compute Pool of type Virtual Disk Repository configured in the system. Error Resolution: Please create a Compute Pool of type Virtual Disk Repository and make sure it has appropriate resources added to it. |
Compute Container | Could not find any non-default Compute Pools from CloudDB. | Error: Cannot find any Compute Pool of type Virtual Disk Repository based on the selected target Virtual Cluster on which the Server will be created. Error Resolution: Please make sure that datastore resources exists on the Virtual Cluster and they are added to one of the Compute Pools (of type Virtual Disk Repository). |
SOI provisioning fails | Error: Could not find any non-default Compute Pools from CloudDB. | Error: Could not find any non-default Virtual Cluster Compute Pools configured in the system. Error Resolution: Please create a Virtual Cluster Compute Pool with appropriate resources in the Compute Pools section under Resource Management. |
Tagging errors should |
| Error: System could not match the tags on eligible Compute Pools(Virtual Cluster/Virtual Resource Pool/Virtual Host) with either of the Tenant or the tags specified in the Service Blueprint. |
Revised error messages in Callouts
Scenario | Error message in version 4.1 | Revised error message in 4.5/ |
|---|---|---|
SOI provisioning fails | Error: Error occurred while invoking the HTTP callout. Got HTTP Response Code : com.bmc.cloud.client.connection.RequestProcessingError: | Error: HTTP server could not process the Callout request. HTTP Response code : 413. URL: http://www.google.com/, Name: HTTP1, Type: PRE_CALLOUT, Class: ComputeContainer , Operation: CONSTRUCTOR. Error Resolution: Make sure that the specified URL is valid and supports the HTTP request. |
SOI provisioning fails | Error: javax.xml.ws.soap.SOAPFaultException: | Error: Could not invoke AO Workflow : Workflow Name: CSMTest:callout_test_success, Callout Name: AO, Type: PRE_CALLOUT, Class: ResourceSet , Operation: bulkcreate Error Resoution: Please make sure that the AO workflow name is correct and it has valid arguments. |
SSO authentication fails because the domain name of AO-host is missing from the AO-CDP URL configured in providers.json | Error: com.sun.xml.internal.ws.client.ClientTransportException: Error Resolution: Make sure that the following requirements are met:
| Error: com.sun.xml.internal.ws.client.ClientTransportException: Error Resolution: Make sure that the following requirements are met:
|
SOI provisioning fails due to | Error: com.sun.xml.internal.ws.client.ClientTransportException: | Error: Could not invoke AO Workflow : Workflow Name: :CSMTest:callout_test_success, Callout Name: AO, Type: PRE_CALLOUT, Class: ResourceSet , Operation: bulkcreate. Service AO Configuration Distribution is not reachable Error Resolution: Please check that the service is running and reachable from Platform Manager. |
SOI provisioning fails | Error: Error occurred while invoking the HTTP callout. Got error : org.apache.http.conn.HttpHostConnectException: Connection to http://10.1.48.24:9091/ refused | Error: HTTP server could not process the Callout request. HTTP Response code : 404. [ URL: http://10.1.48.14/, Name: HTTP, Type: PRE_CALLOUT, Class: ComputeContainer , Operation: CONSTRUCTOR ]. Error Resolution: Action: Make sure that the specified URL is valid and supports the HTTP request. |
SOI provisioning fails due to | Error: javax.xml.ws.soap.SOAPFaultException: com.sun.xml.wss.XWSSecurityException: com.sun.xml.wss.impl.WssSoapFaultException: Authentication of Username Password Token Failed | Error: Could not invoke AO Workflow : Workflow Name: :CSMTest:callout_test_success, Callout Name: AO, Type: PRE_CALLOUT, Class: ResourceSet , Operation: bulkcreate. Service AO Access Manager is not reachable. Error Resolution: Please check that the service is running and reachable from Platform Manager. |
SOI provisioning fails | Severity: CRITICAL | ERROR: Runtime error occured while executing AO workflow. ERROR RESOLUTION: Please check the logs for more details and make sure CDP configurations are correct. |
Revised error messages in BMC Network Automation
Scenario | Error message in version 4.1 | Revised error message in 4.5 |
|---|---|---|
SOI fails when network path creation fails to a external IP | Error: Cannot create network path : [Exception while creating network path in BBNA : No supporting network path found for Path Rule "NP0_ca192d5d-0b36-4587-a741-2d3534aa2753" with destination endpoint: { hostAddress=10.1.46.6 } and source endpoint: { hostAddress=10.10.14.2 } ]. | Cannot create network path : [Exception while creating network path in BBNA : No supporting BNA network path found for Path Rule "NP0_6831d7fd-15ec-49df-ac26-e427f4ffb750" with destination endpoint: { hostAddress=10.10.15.10 } and source endpoint: { hostAddress=10.1.63.134 } in the network container "NCrsanas21"]. Suggested action: Please check if the Network Path(s) defined the Blueprint: NetworkpathBlue are supported on the Network Container: NCrsanas21 in BNA under: Networks->Containers->NCrsanas21->Network Paths. Either update your blueprint to change the Network Path(s) accordingly OR adjust your tags on the Blueprint NetworkpathBlue so that the service is created on a different Network Container where these Network Path(s) are supported. |
Load Balancer Pool can't be located on a qualifying Network Container with Disable Load Balancer | Error: Could not find existing LoadBalancerPool with name specified in service blueprint: [LBP1] or it does not belong to NetworkContainer selected. | Could not find existing Load Balancer Pool with name: LBP1 in Service Blueprint: LoadBalancerPool or it does not belong to the selected Network Container: NCrsanas21. Suggested action: Please make sure that Load Balancer configuration is enabled in Network Container: NCrsanas21 and a Load Balancer Pool with name LBP1 exists OR adjust your tags in the Blueprint: LoadBalancerPool so as to map to a Network Container having this Load Balancer Pool. |
Load Balancer Pool can't be created on a qualifying Network Container with Disable Load Balancer | Error Resolution: Check if an enabled Load Balancer is configured for the Logical Hosting Environment. | Load Balancer configuration is not enabled for Network Container: NCrsanas21 Suggested action: Please enable Load Balancer configuration for Network Container: NCrsanas21 OR adjust your tags in the Blueprint: LoadBalancerPool so as to map to a Network Container having Load Balancer configuration enabled. |