DescriptionKevin Alon Goldblatt
2023-12-07 17:11:03 UTC
Created attachment 2003127[details]
PVC label selector
Description of problem (please be detailed as possible and provide log
snippests):
Applying DR Policy to app set application, the system is suggesting a label that cannot work, it should be filtered out. Only labels with appname= should be recommended
Version of all relevant components (if applicable):
Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Is there any workaround available to the best of your knowledge?
Creating your github resource with a short label e.g. appname=kubevirt
Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2
Can this issue reproducible?
yes
Can this issue reproduce from the UI?
yes
If this is a regression, please provide more details to justify this:
Steps to Reproduce:
1. Create an app set application from here: https://github.com/kgoldbla/ocm-kubevirt-samples/blob/vm9-application/vm-standalone-pvc-odr-regional/pvc.yaml
2. selected the app:kebernetes/instance-app-set-vm-standalone-dv-odr-regional option
3. Relocating will not work with this.
4. Only the appname=<label> should be recommended
5. ...instance-of= should not be used
Actual results:
...instance-of= was recommended as an option and won't work for dr
Expected results:
On appname= should be recommended
Additional info:
See attached screenshots
Comment 4krishnaram Karthick
2024-02-22 11:50:05 UTC
Moving the bug to 4.14.7.
We have reached the limit for fixes in 4.14.6