In addition I've noticed that delete object are using: finalizers. And I believed that this is main issue. The deletionTimestamp is wrong. But I don't know why it is using wrong date and time.
<https://docs.openshift.org/latest/admin_guide/custom_resource_definitions.html#finalizers> Finalizers Custom objects support *finalizers*, which allow controllers to implement conditions that must be completed before the object can be deleted. You can add a finalizer to a custom object like this: apiVersion: "stable.example.com/v1"kind: CronTabmetadata: finalizers: - finalizer.stable.example.com The first delete request on an object with finalizers sets a value for the metadata.deletionTimestamp field instead of deleting the object. This triggers controllers watching the object to execute any finalizers they handle. Each controller then removes the finalizer from the list and issues the delete request again. This request deletes the object only if the list of finalizers is empty, meaning all finalizers are done. 2018-05-02 10:39 GMT+02:00 Łukasz Strzelec <[email protected]>: > Hi Jessica:) > > What I've observed is that each object, that I want to be deleted from UI, > has got timestamp with 2h earlier than current time. Looks like some > proccess is puting wrong hour into datestamp. > I also notice that time on master container is diffrent then on atomic > host from where it is running, on Atomic host I have UTC settings, on > master container CEST. Do you thing that this might be a problem ? > I can start the pod with timezone settings mounted, but question is which > process and how to debug it is putting timestamps into objects ?? > Thx in advance:). > > 2018-04-30 13:13 GMT+02:00 Jessica Forrester <[email protected]>: > >> The console deletes objects with foreground propagation policy for >> garbage collection. After you delete something I would check that the >> resource has a deletionTimestamp set on it and then check if there is a >> section called finalizers. If there are any finalizers those would be >> blocking the resource from going away completely. If GC is failing >> somewhere then its finalizers are not getting removed. >> >> If this is what's happening then I recommend checking the logs for the >> master. >> >> On Mon, Apr 30, 2018, 3:55 AM Łukasz Strzelec <[email protected]> >> wrote: >> >>> Dear all, >>> >>> I have strange issue with my cluster. When I'm deleting builds, dc, bc >>> from WebUI, these object are not being deleted. I see information in the >>> corner " object marked for deletion" but nothing happend. >>> >>> >>> >>> >>> >>> >>> >>> >>> *-bash-4.2$ oc versionoc v3.7.2+5eda3fa-5kubernetes >>> v1.7.6+a08f5eeb62features: Basic-Auth GSSAPI Kerberos SPNEGOServer >>> https://<acme-org>:443openshift v3.7.2+5eda3fa-5kubernetes >>> v1.7.6+a08f5eeb62* >>> >>> >>> When I'm doing the same operation from OC CLI tools, everything works >>> fine. >>> Can you help me to solve this mystery:) ? Where I should start debugging >>> this. I cannot find anything in logs. >>> >>> >>> Best regards >>> -- >>> Ł.S. >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>> >> > > > -- > Ł.S. > -- Ł.S.
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
