-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.14-SNAPSHOT is generating WaiterException: CleaningProject #308
Comments
Are you using same fabric8 client version as the xtf release? |
With aligning client versions this problem is gone. What are we experiencing now is much more longer testsuite run - it has nearly doubled. From nearly 5 hours to 9 hours. Have you noticed something similar? |
@dsimansk Now with 0.14-SNAPSHOT I run into situation that ReplicaSet was not deleted
After manual delete through web console problem was away. |
@mchoma The issue is that |
[#308] Clean does not remove ReplicaSets
Resolved in #321. |
We are missing way to specify deletion policy in kubernetes client [1].
(And probably with 0.13 default becomes orphan policy??)
Anyway, currently we are experiencing
*-deploy
pods not beeing deleted because they havefinalizer: orphan
andownerReference
filled to parent object (I think it was ReplicaSet) in same time.So either
OpenShift.clean()
does not clean parent objects properly. Should we return tocascading(true)
?ownerReference
is not cleared properly from child objectsShouldnt we apply
cleanFinalizers
workaround [2] again to cover this scenario?[1] fabric8io/kubernetes-client#1614
[2] caa00a4
The text was updated successfully, but these errors were encountered: