search

odpi / egeria-samples

various samples that can be useful either for learning or as initial starting points for working with Egeria
Apache License 2.0
13 stars 8 forks source link

Deleting helm chart results in deletion errors #19

Closed planetf1 closed 3 years ago

planetf1 commented 5 years ago

May be related to odpi/egeria#825 but recording here for now

  egeria git:(helm25) helm delete jazzy-aardwolf                                                                                                                                                                                                                                                              git:(helm25|) 
Error: deletion completed with 11 error(s): release "jazzy-aardwolf": object "" not found, skipping delete; release "jazzy-aardwolf": object "" not found, skipping delete; release "jazzy-aardwolf": object "" not found, skipping delete; release "jazzy-aardwolf": object "" not found, skipping delete; release "jazzy-aardwolf": object "" not found, skipping delete; release "jazzy-aardwolf": object "" not found, skipping delete; release "jazzy-aardwolf": object "" not found, skipping delete; release "jazzy-aardwolf": object "" not found, skipping delete; release "jazzy-aardwolf": object "" not found, skipping delete; release "jazzy-aardwolf": object "" not found, skipping delete; release "jazzy-aardwolf": object "" not found, skipping delete

Since the objects are not named, need to retry and capture more info. Could indicate template errors on naming of objects. Or could be jobs removed via hooks. either way should be cleaned for the user

Checking resources manually, any jobs running at the time 'helm delete' is issues get left behind. In my case *job-01-data-loader - when this area is investigated the focus should be to ensure a clean deletion in all cases.

cmgrote commented 5 years ago

Checking resources manually, any jobs running at the time 'helm delete' is issues get left behind. In my case *job-01-data-loader - when this area is investigated the focus should be to ensure a clean deletion in all cases.

This seems to be a problem ("feature"?) in Helm itself when it comes to Jobs... It will only remove them if they've run successfully, and within the timeout specified when running the helm install; otherwise it does indeed leave them behind, unfortunately.

(See https://github.com/helm/helm/issues/4434)

github-actions[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

planetf1 commented 3 years ago

The VDC environment will need significant re-work to adapt to the many changes made in Egeria to better support metadata integration. Additionally the helm charts used for the lab & a simple base config have evolved to better support different types of services, exposing of ports, persistent storage etc.

As such specific incremental changes to the current - now old - charts do not really add value.

As such closing for now