Closed saberkan closed 4 years ago
@cnuland would you be able to look into this issue?
@saberkan I have been trying to reproduce it, but no success:
NAME CREATED AT
overcommit-limits 2020-07-31T01:46:59Z
Name: overcommit-limits
Namespace: saberkan
Type Resource Min Max Default Request Default Limit Max Limit/Request Ratio
---- -------- --- --- --------------- ------------- -----------------------
Container cpu - - - - 100
Container memory - - - - 2
NAME CREATED AT
overcommit-limits 2020-07-31T01:46:59Z
Name: overcommit-limits
Namespace: saberkan
Type Resource Min Max Default Request Default Limit Max Limit/Request Ratio
---- -------- --- --- --------------- ------------- -----------------------
Container cpu - - - - 100
Container memory - - - - 2
NAME CREATED AT
overcommit-limits 2020-07-31T01:46:59Z
Name: overcommit-limits
Namespace: saberkan
Type Resource Min Max Default Request Default Limit Max Limit/Request Ratio
---- -------- --- --- --------------- ------------- -----------------------
Container cpu - - - - 100
Container memory
not sure how to help, any suggestion?
I was actually able to reproduce it, but only with the operator deployed from OLM... Will look into it more tomorrow.
Great, thank you @raffaelespazzoli, I couldn't neither reproduce it every single time. I though it was something with my environment. But it seems not, and the bug doesn't occur every single time but at least a majority of times in my case.
@saberkan I thin the last merge should fix the issue, but as you know it's not easy to reproduce. Would you be able to make a build from master and test it before I cut a release?
@raffaelespazzoli thank you for the fix, I confirm It works now for me under. OCP 4.4.8, and OCP 3.11.200.
Issue:
When installing version v0.2.1 resources still disappear after reconciliation. I though this was related to my environnement (when closing issue #55), but even with a different cluster and operator installation from scratch it still behaving the same. We tried to debug on OCP 4 and OCP 3 cluster, and the issue still remain.
How to reproduce
1 - Install v0.2.1 manually 2 - create and label project:
3 - Create CR
oc apply -f examples/namespace-config/overcommit-limitrange.yaml
4 - Check CR created5 - Edit examples/namespace-config/overcommit-limitrange.yaml and set memory: 2 6 - Apply edited file
oc apply -f examples/namespace-config/overcommit-limitrange.yaml
7 - Check limit object:Additional logs
From OCP 4
From OCP 3