Changes to Action Policy do not Get Saved

Introduction

This document describes an issue where changes when made to the Action policy, do not get saved.

Prerequisites 

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

• Cisco CloudCenter 4.7.1.1.
• Cisco CloudCenter 4.8.0.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Problem

When you use parameter to change the Action policy and save the policy, it says that the changes are applied, however, GUI does not save the expected change by the user.

Execute for: Application Deployment

On Event: Status Changed

Action Type: Execute a command

Script: Selects the name of the script

1. 'Job Status' Action Policy.

2. Saving 'Job Status' Action Policy changes with a Script Name.

3. Confirmation that Action Policy 'Job Status' was saved successfully.

4. Action Policy 'Job Status' did not save the changes as expected.

Solution

The fix is provided in 4.8.1. version of CloudCenter. 

http://docs.cloudcenter.cisco.com/display/CCD48/4.8.1

Issue: When a user tried to deploy an application with an action policy, the Action policy did not executed according to the script.
Resolution: The MongoDB was down and hence the notification service was also down – this prevented the policy from being executed. Once the MongoDB was up and running, the script executed as designed.