Skip to:

Skip to Jira Navigation
Skip to Side Navigation
Skip to Main Content

DCAEGEN2 failed redeployment leaves cloudify orchestrated dev-dcae namespace pods up

Description

This is a known issue with the secondary orchestration - if a helm upgrade fails and dcae is undeployed - it leaves the dep pods behind

result

Environment

None

Attachments

1

Linked issues

blocks

ONAP Deployment Resiliency changes to deploy without POD failures

CD: OOM automated deployment script

Task Force to implement CD (Continuous Deployment)

is blocked by

DCAE pods are not getting purged

Add support to DCAEGEN2

relates to

Deploying DCAEGEN2 late in a sequenced deployment will cause the secondary cloudify orchestration pods DEP* to fail

Common Postgresql PVC management

LOG Pipeline addition for DCAE secondary Cloudify orchestration pods

Activity

Show:

Former user June 20, 2019 at 8:52 PM

https://docs.onap.org/en/latest/submodules/dcaegen2.git/docs/sections/installation_oom.html

before undeploy, the uninstall script should be run to remove the cloudify blueprint deployed services.

Former user May 1, 2019 at 7:16 PM

This will need further discussion. Upgrade on platform components is fine, but bootstrap/Cloudify will have impact on Service components.

Done

Details
Assignee
Former user(Deactivated)
Reporter
Former user(Deactivated)
Labels
cloudifyhelmobrienlabs
Fix versions
Dublin Release
Affects versions
Casablanca Release
Priority
Medium

Created January 8, 2019 at 8:38 PM

Updated August 12, 2023 at 3:45 AM

Resolved June 20, 2019 at 8:53 PM