E-CLOUD: Cloud Manager Cannot Delete An Environment After Orchestration Has Been Created

(Doc ID 2334758.1)

Last updated on DECEMBER 01, 2017

Applies to:

PeopleSoft Cloud Manager - Version 05 and later
Information in this document applies to any platform.

Symptoms

On : 05 version, PeopleSoft Cloud Manager

ACTUAL BEHAVIOR
---------------

Cloud Manager cannot delete an environment after the environment has been migrated to orchestration i.e. an orchestration has been created for the environment

EXPECTED BEHAVIOR
-----------------------

Cloud Manager should be able to delete an environment even after an orchestration has been created for it

STEPS
-----------------------

The issue can be reproduced at will with the following steps:
1. Provision an environment using Cloud Manager
2. Create an orchestration with the created environment
3. Try to delete the environment from within the Cloud Manager

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms