Cloud profiles update doesn't work properly about garden-setup HOT 3 CLOSED

I tried to reproduce this issue using garden-setup 1.16.1, but I failed.

What I tried:

1. deploy garden-setup
2. remove one kubernetes version from the list of kubernetes versions
   2.1 list of kubernetes versions is taken from defaults
   2.2 list of kubernetes versions is taken from acre.yaml (defaults overwritten by profile section in iaas entry)
3. deploy cloudprofile again using sow deploy gardencontent/profiles

In each case, the deleted kubernetes version has also been removed from the cloudprofile. I even tried it with an active shoot on that version, but it still got removed from the profile.

Since I'm unable to reproduce the issue, I assume it is fixed in the current version of garden-setup. Maybe by the new cloudprofile design (new apigroup) introduced with garden-setup 1.16.0.
I'll close the issue, feel free to reopen if you can reproduce the problem with garden-setup 1.16+.

from garden-setup.

probably it was fixed by #108. Considering the text below:

Due to a bug in the current Gardener version, Openstack shoots that are created with the new manifest (core.gardener.cloud/v1alpha1) have some issues right now. If you are manually creating shoots, use the old manifest to avoid the issues. Since garden-setup uses the new manifest for shooted seeds, you should skip this release and wait for a fix in case you are using a shooted Openstack seed.

Is it already safe to use 1.16 with openstack?

from garden-setup.

Unfortunately not yet. The fix is in master (gardener/gardener#1506 / gardener/gardener@dcdbd48), but there hasn't been any release of Gardener since, therefore the current version of garden-setup will still have this issue.

from garden-setup.