Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deleting one container in a nested container does not work #173

Closed
noredistribution opened this issue Mar 25, 2020 · 0 comments
Closed

Deleting one container in a nested container does not work #173

noredistribution opened this issue Mar 25, 2020 · 0 comments
Assignees
@titom73 @noredistribution
Labels
module: cv_container Issue related to cv_container module state: accepted Issue is part of the development roadmap status: testing PR under testing type: enhancement New feature or request
Milestone
v1.1.0

Comments

@noredistribution
Copy link
Contributor

Currently it seems like removing a single container only works if the container's parent is the root (by default called Tenant ) container; if the container's parent is a child container of the root container, the playbook gets stuck

e.g.

Non-working vars example

  vars:
      run_tasks: false
      run_mode: delete
      container_delete:
         DC1-Leaf-A:
             parent_container: DC1-Leafs

Working vars example1:

  vars:
      run_tasks: false
      run_mode: delete
      container_delete:
         DC1:
             parent_container: Tenant

Working vars example2:

  vars:
      run_tasks: false
      run_mode: delete
      container_delete:
         DC1:
             parent_container: Tenant
         DC1-Leafs:
             parent_container: Ankara
         DC1-Leaf-A:
             parent_container: DC1-Leafs
         DC1-Leaf-B:
             parent_container: DC1-Leafs
@noredistribution noredistribution added the status: Triage New incoming issue label Mar 25, 2020
@titom73 titom73 added module: cv_container Issue related to cv_container module state: accepted Issue is part of the development roadmap type: enhancement New feature or request and removed status: Triage New incoming issue labels Mar 25, 2020
@titom73 titom73 added this to the v1.1 milestone Mar 25, 2020
titom73 added a commit that referenced this issue Mar 30, 2020
@titom73
Fix issue with cv_container and relative topology
2e44e2d 
Summary:
--------
Update code to support deletion of container topology not using CVP root
container.

Deletion example:

```yaml
    CVP_CONTAINERS:
      POD01:
        parent_container: Leafs
```

Fix: #173

Tested with :
-------------
- Addition of a complete topology
- Deletion of POD01
- Creation with partial topology already deployed
- Deletion of full topology
@titom73 titom73 mentioned this issue Mar 30, 2020
Merged
5 tasks
@titom73 titom73 added the status: To be merged Issue solved in a volatile branch label Apr 4, 2020
titom73 added a commit that referenced this issue Apr 7, 2020
@titom73
Merge pull request #175 from /issues/173-cv-container
c228aa0 
Fix issue with cv_container and relative topology
@titom73 titom73 added status: testing PR under testing and removed status: To be merged Issue solved in a volatile branch labels Apr 7, 2020
@titom73 titom73 closed this as completed Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@titom73 titom73

@noredistribution noredistribution

Labels
module: cv_container Issue related to cv_container module state: accepted Issue is part of the development roadmap status: testing PR under testing type: enhancement New feature or request
Projects
None yet
Milestone
v1.1.0
Development

No branches or pull requests
2 participants
@titom73 @noredistribution