Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.

Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |

Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
Known issues, limitations, and workarounds
Codar
General
Codar 1.70.RC3. Privacy Statement is missing in Codar Login Page
ID |
|
Problem |
The privacy statement does appear to show up on 4.8MR bits on the initial MPP login screen at /org/<ORG_NAME>. However, the next IDM screen you are navigated to when clicking "Log in" is where the issue lies. The screen apparently should, but does not show the privacy statement. |
Cause |
Code defect |
Workaround |
The user could always manually go to the privacy link they have configured for the organizations privacy statement. This link is available in the Organizations > Organization Name > General Settings area. Or, the user could simply return back to the main portal login page to view the privacy link. |
Orchestration Tile: 403 Error when LDAP Users does not exist in OO
ID |
|
Problem |
Operation Orchestration displays: 403 Error when trying to use direct link from HPE CSA using menu Workflows -> Orchestration in case that LDAP Users does not Exist in OO |
Cause |
Caused by defect QCCR8C32250 in product HPE Operation Orchestration |
Workaround |
Modify URL of HPE Operation Orchestration to end with /oo/login/login-form or use seeded user admin for login to HPE CSA. |
SQL statement execution timeout cannot be applied to install/upgrade scripts.
ID |
|
Problem |
upgrade fails with "Read timed out" during processing "csa_remove_createdby_updatedby.plsql" file on SQL Server (check CSA\_CSA_4_80_0_installation\Logs\install.log to ensure it) |
Cause |
csa_remove_createdby_updatedby.plsql contains ALTER TABLE ... REBUILD statements that goes through all rows in table. So the REBUILD operation could timeout on huge databases. |
Workaround |
1) Edit CSA\scripts\mssql\csa_remove_createdby_updatedby.plsql and comment out all "ALTER TABLE ... REBUILD" statements at the end of the file. You can comment it out by enclosing all REBUILD statements to /* and */ (SQL comments). Save the file. 2) Restart the upgrade process. It should end successfully. 3) After upgrade it is recommended to apply the commented REBUILD statements manually, For example, using Microsoft SQL Server Management Studio. Note: It could take several hours on big databases with millions of artifacts. |
Semantic Validation for properties in User Operations->Public Action fails to recognize the variable
ID |
|
Problem |
If [CLIENT:<prop>] token is used as parameter value of semantic validation parameters, then test (validation) fails with following error message: Option property with the name <prop> is not found. If this refers to a new property, ensure that it is saved. Test fails even if the [CLIENT:<prop>] is used on property <prop> and user filled "Input Validation" input fields. Note: it is test issue only. In runtime tokens are resolved correctly. |
Cause |
1) if token [CLIENT:<prop>] is used as parameter value of validation parameter on user operation parameter <prop> and user filled Input Validation field input -> it is caused by UI, which does not replaces the [CLIENT:<prop>] token with string entered to Input Validation input field. 2) if token [CLIENT:<prop>] refers to another parameter of user operation -> it is caused by backend, which does not resolve tokens pointing to parameters of user operation when test is requested 3) if token [CLIENT:<prop>] refers option model property -> such token cannot be resolved because a) user operation does not have access to option model (e.g., user operation is on resource offering), b) option model can define more than one property of the name, so it is not possible to identify the property |
Workaround |
For all causes 1), 2), and 3) the workaround is * enter value instead of token [CLIENT:<prop>] used as user operation parameter value - once tested, change parameter value back to the token |
In CSA 4.8 Content Store, after installing a content through file, if we try installing the same content through HPLN, it does not prompt for re-install dialog for the first attempt.
ID |
|
Problem |
CSA 4.8 Content Store, after installing a content through file, if we try installing the same content through HPLN, it does not prompt for re-install dialog for the first attempt. |
Cause |
Product Limitation |
Workaround |
1. Install the content from file system 2.Install the same content from HPLN it will fail for the first time 3. Re-installing the same capsule from HPLN will pass for the second time showing the Reinstall dialog box. Refresh your browser after every attempt in case your browser is slow or lagging. |
Import Preview fails for a design while the actual Import succeeds with the same design
ID |
|
Problem |
Import Preview fails while previewing the import of a design from an upgraded CSA instance into a fresh CSA 4.8 instance. |
Cause |
A constraint violation is indicated in the Preview |
Workaround |
Result of Import Preview can be ignored, and the design can be imported by clicking on Import button instead. |
SAML configuration got reset after upgrading to 4.8 with 1.10.4-129 IdM build
ID |
|
Problem |
SAML configuration is lost after upgrade to CSA 4.8 from CSA 4.7 |
Cause |
Process Limitation |
Workaround |
If SAML is configured in CSA 4.7 and you have upgraded to CSA 4.8, you need to configure SAML again. |
Resuming a failed upgrade is failing on Oracle PCoE Environment because of the created_by and updated_by references in the scripts.
ID |
|
Problem |
Resuming a failed upgrade is failing on Oracle PCoE Environment because of the created_by and updated_by references in the scripts. |
Cause |
Resuming a failed upgrade is failing and csa\_CSA_4_80_0_installation\Logs\install.log contains error message that UPDATED_BY_ID columns is missing For example error message from Oracle database: PL/SQL: ORA-00904: "UPDATED_BY_ID": invalid identifier |
Workaround |
Restore the database from backup taken prior upgrade and resume the upgrade again. |
Health status is not updated for servers deployed on Helion Openstack (HOS) provider.
ID |
|
Problem |
Health status is not updated for servers deployed on Helion Openstack (HOS) provider. |
Cause |
CSA is unable to retrieve the health status since CO is not supporting HOS 3.0. |
Workaround |
It is a product limitation. No workaround available. |
CO Dependency: When the VM is powered OFF, CO is not sending the ideal data points (zero values) to be displayed for Memory & CPU graph in Health tab.
ID |
|
Problem |
Missing data points when VM is powered OFF or Suspended. |
Cause |
Unable to plot the graph for missing data points. |
Workaround |
No workaround available. |
Currently we do not support hybrid Cloud Slang-AFL flows in any combination.
ID |
|
Problem |
Currently we do not support hybrid Cloud Slang-AFL flows in any combination. |
Cause |
It is a product limitation. |
Workaround |
The procedure on ‘Creating a topology Design with CloudSlang’ is available in the Topology Components Guide (Whitepaper). Refer to this guide for a workaround. |
Unexpected Error occurred when a Component having Provider property mapping but not associated to any Provider Type is being used in Design.
ID |
|
Problem |
Unexpected Error occurred when a Component having Provider property mapping but not associated to any Provider Type is being used in Design. |
Cause |
User did not configure the provider prior to deployment. |
Workaround |
The log files will contain the appropriate error message about the missing provider. Once the provider is created, the error message will not be shown. |
Configure Pools should come only to Designs which have XI component.
ID |
|
Problem |
Configure Pools should come only to Designs which have existing server component. |
Cause |
There is currently no check in place to show Configure Pools only for Designs that have an existing server component since in case of Partial Designs, it is not possible to determine if the design will have an existing server component. |
Workaround |
No workaround available. This would not impact the other designs even though it is visible. |
Installation, initial configuration, upgrade, and uninstallation
SAML Authorization will not work for the CSA Provider, if the access control is provided till the OU Level.
ID |
|
Problem |
The SAML Authorization does not work if the access control is configured with the LDAP sub tree. |
Cause |
CSA does not support the LDAP sub tree for ACL when SAML is enabled. |
Workaround |
None |
IdM Dependency -- Upgrade Blocker - Upgrade from 4.6 to 4.8 is failing for windows with MS-SQL database
ID |
|
Problem |
Upgrade from 4.6 to 4.8 is failing for windows with MS-SQL database |
Cause |
Snapshot Isolation not enabled for IDM. |
Workaround |
For Microsoft SQL Server, it is mandatory to enable the snapshot isolation for Identity management database which can be achieved through following two database statements: ALTER DATABASE idmdb SET ALLOW_SNAPSHOT_ISOLATION ON; ALTER DATABASE idmdb SET READ_COMMITTED_SNAPSHOT ON; |
After an HA upgrade, the Elasticsearch configuration file resets and custom changes in the elasticsearch.yml file are lost
ID |
|
Problem |
Custom changes in Elasticsearch configuration may be discarded during an HA upgrade installation. |
Cause |
Product defect. |
Workaround |
Custom changes from upgraded installation are stored in a backup folder in /elasticsearch/config/. Transfer custom changes from the older installation file into the upgraded file. |
Codar Management Console
Topology component boolean and integer properties are not correctly mapped to Chef attributes
ID |
|
Problem |
Topology components imported from Chef include an attributes parameter in their deploy operation, allowing customization of the provisioning of the Chef recipe. Properties passed in the attributes parameter are automatically converted to Strings. For example, an Integer component property of 3306 will be converted to "3306", and a Boolean component property of true will be converted to "true". If the Chef recipe is written to expect an Integer or Boolean input and not a String, the provisioning of the component will fail. |
Cause |
Product limitation |
Workaround |
The Chef recipe should be written or modified to expect String inputs. |
SMC login is failing if we disable HP SSO Only configuration manually on CSA 4.8 HA build#1500
ID |
|
Problem |
SMC login fails if we disable HP SSO configuration manually on CSA 4.8 HA |
Cause |
Product limitation |
Workaround |
Open the file $CSA-HOME\jboss-as\standalone\deployments\csa.war\WEB-INF\applicationContext-security.xml and set checkSSOCookie value to false in the below mentioned section of bean and restart CSA service. <beans:bean id="tokenValidityFilter"class="com.hp.csa.security.TokenValidityFilter"> <beans:property name="checkSSOCookie" value="true"/> </beans:bean> |
Imported topology component does not present a list of values for a multi-select Input property
ID |
|
Problem |
When importing an Operations Orchestration flow in the Designs / Topology / Components area of the Codar Management Console, if that flow contains an Input property with Type value of List of Values and From value of Prompt User from List – Selection List, the resulting component imported into CSA will have a property value of type String for this Input property. Instead of a list of values from which one or more can be selected, a single text input will be presented to the user for this property in both the Components and Designer areas. |
Cause |
The Designs / Topology / Components and Designs / Topology / Designer areas of the Codar Management Console do not have graceful support for multi-select properties such as these. |
Workaround |
In the text input for such a property, encode the property values using the appropriate delimiter, which is determined by the method the flow uses to parse the Input property. If the flow uses the Selection List Iterate operation that is provided with the Base content pack in Operations Orchestration, the delimiter (separator) is configurable and has a default of ‘|’. For example, the values ‘red’, ‘green’, and ‘blue’ would be specified as ‘red|green|blue’ (unquoted) if using the Selection List Iterate operation with the default separator value. |
Pipeline management
A simple design with server group enabled for redeploy does not prompt for instance count value during redeploy
ID |
|
Problem |
User cannot redeploy a package and scale out in a single operation. |
Cause |
Internally, redeploy and scale out are handled as two different operations. An operation is not designed to redeploy as well as scale out. |
Workaround |
Codar does not support scale out during redeploy in this release. In this release the user must first redeploy and update the instance. After the instance is updated, the user can scale out the deployed instance. Redeploy and scale out are not supported in a single operation. They must be performed as different operations. |
The infrastructure design is not displayed in the drop-down list in the Edit dialog box during a deploy release gate action.
ID |
|
Problem |
Though an infrastructure design is selected, it is not displayed in the drop-down list in the Edit dialog box during a deploy release gate action. |
Cause |
Edit custom actions for partial design does not work properly. |
Workaround |
Do not edit the custom action. To update the custom action, delete it and add a new action. |
Unable to search Add Group under Designer Access Control once group name is modified under Organizations.
ID |
|
Problem |
Unable to search Add Group under Designer Access Control once a group name is modified under Organizations. |
Cause |
The group search works based on the name and not display name, hence when the display name is modified the underlying name remains unchanged. |
Workaround |
User should not modify the group name in Access Control Page, and rather delete and create a new group instead of modifying it. |
Release Manager (RM) should be restricted from accessing the Design tab for which the RM does not have the permission as per OOTB Roles defined.
ID |
|
Problem |
Release Manager (RM) should be restricted from accessing the Design tab for which the RM does not have the permission as per OOTB Roles defined. |
Cause |
Role permission checks are not working for Release Manager after the new IDM changes. |
Workaround |
User can see the Design tab, but will not be able to perform any operations. |
User not able to navigate to Release Pipeline and other tabs under Release Automation.
ID |
|
Problem |
User is not able to navigate to Release Pipeline and other tabs under Release Automation. |
Cause |
This issue is occurring in Internet Explorer 11. |
Workaround |
Use supported versions of other browsers like Chrome. |
Add Script Action - Previous data value is not cleared when user changes OS Type.
ID |
|
Problem |
Add Script Action – The previous data value is not cleared when the user changes OS Type. |
Cause |
This is a UI behavior. |
Workaround |
No workaround. |
In XI Machine update one scenario, two machines are getting updated with same IP Address.
ID |
|
Problem |
During XI Machine update, in one scenario, two machines are getting updated with same IP Address. |
Cause |
Missing validation in case of update. |
Workaround |
Edit the machine name and re-save to a different name. |
Exception seen for Empty Design under RPM when Life Cycle Default is set for just 2 Life Cycle.
ID |
|
Problem |
Exception is seen for an empty design under release pipeline management when lifecycle default is set for just 2 lifecycles. |
Cause |
Validation Error due to an empty design. |
Workaround |
Workaround is to add a component to the design. |
Pools Search Not working based on Filter Search criteria.
ID |
|
Problem |
Search for pools is not working based on filter search criteria |
Cause |
This is a UI issue. |
Workaround |
No workaround available. |
Sequence designs are not visible in the Release Management tile because the 'Restricted User Access' is getting enabled by default.
ID |
AGMCR10C15744 |
Problem |
Sequence designs are not visible in the Release Management tile because the 'Restricted User Access' is getting enabled by default. |
Cause |
This is in the case where CSA license is applied first and then Codar license is applied. |
Workaround |
The Administrator can go to Access Control on the Design and disable Restricted User Access. |
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to clouddocs@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: