New Environment Jobs Blocked and Process Error - Flows Initialization Failed. reason: Unknown

Products

• CA Release Automation - Release Operations Center (Nolio)
• CA Release Automation - DataManagement Server (Nolio)

Issue/Introduction

Deployments executed after creating a newly created/duplicated environment result in either:

• Pre-plan step/job being "blocked" or;
• Deployment step resulting in "<step name> has a process error - Flows Initialization Failed. reason: Unknown"

 

Environment

Release : 6.6

Component : CA RELEASE AUTOMATION RELEASE OPERATIONS CENTER

Cause

Corrupt cache. 

Resolution

After using the KB below to cleanup the cache, also taking care to remove the files/folders in NAC_INSTALL_DIR/temp/* (not the folder itself), manually creating a new environment fixed this problem. 

Knowledge Base Article: CA Release Automation Clean up and Troubleshooting best practices

 

Important

Do not use forward slashes "/" in Environment names. 

• While duplicating Environments, the new name prompt does not give an error if you supply a forward slash "/" in the name.
• Supplying a forward slash "/" while manually creating a new Environment does give an error and will not let you save the name if a forward slash is used.