Bug 1460401 - Container Nodes should be archived instead of being deleted
Container Nodes should be archived instead of being deleted
Status: ON_DEV
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
5.8.0
Unspecified Unspecified
high Severity high
: GA
: 5.8.2
Assigned To: zakiva
Pavel Zagalsky
container
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-09 18:54 EDT by Federico Simoncelli
Modified: 2017-06-23 17:24 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Container Management


Attachments (Terms of Use)

  None (edit)
Description Federico Simoncelli 2017-06-09 18:54:08 EDT
Description of problem:
Currently when a node disappears from the OpenShift cluster it is deleted in CloudForms. We should instead archive it (as other entities).

Version-Release number of selected component (if applicable):
5.8

How reproducible:
100%

Steps to Reproduce:
1. Remove one Node from the OpenShift cluster

Actual results:
The node is removed from the database.

Expected results:
The node should be archived (not visible in the UI but still in the database).

Additional info:
This would allow also old performance collection for Nodes that have been removed and also for Containers that were running on those Nodes.

Note You need to log in before you can comment on or make changes to this bug.