ZZ00410: YAML FUNCTIONS CANNOT HANDLE THE DOUBLE BACK SLASH (\\)

IBM Cloud Orchestrator Fix Pack 3 (2.4.0.3) for 2.4

APAR status

• Closed as documentation error.

Error description

• SCOrchestrator Heat Support Toolkit code wrongly replaces
  user_data using "Embeddable Deploy Heat Template" Human Service
  
  
  heat template has
  $TmpDir='C:\\temp'\n
  
  get replaced with
  $TmpDir='C:undefinedtemp'\n
  
  
  for test only
  

Local fix

• User data should not contain '\' and this should be replaced
  with '/'
  

Problem summary

• ****************************************************************
  
  * USERS AFFECTED:
  All users of  IBM Cloud Orchestrator 2.4 FP1 documentation and
  writing its own Heat templates.
  
  ****************************************************************
  
  * PROBLEM DESCRIPTION:
  IBM Cloud Orchestrator 2.4 FP1 documentation does not point out
  some constrains working with Heat templates with contained back
  slashes.
  
  ****************************************************************
  
  * RECOMMENDATION:
  Review the next update of SmartCloud Orchestrator 2.4 FP 3
  Information Center when available. The documentation changes can
  also be found in the conclusion section below.
  

Problem conclusion

• ****************************************************************
  
  * PROBLEM CONCLUSION:
  In chapter "IBM Cloud Orchestrator 2.4.0.3>Working with
  self-service>Using self-service>Managing resources>Working with
  Heat templates and stacks>Deploying a Heat template" the
  following will be added:
  
  Note: When you write the Heat stack template, use the forward
  slash character (/) instead of the backslash character (\) in
  the user_data section (for example, in path names).
  
  A Heat stack template is written in YAML format, and is
  translated into a JSON object when the self-service offering is
  processed by Business Process Manager. If you use the backslash
  character and the target system is a Microsoft Windows system,
  the YAML-to-JSON parser inserts a second backslash character as
  an escape character. If the escaped backslash character (\\) is
  combined with a newline character (\n), the YAML code cannot be
  processed by the parser. To work around this problem, use the
  forward slash character instead. Microsoft Windows can process
  path names that contain forward slashes, if the path names do
  not include any spaces.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels