Bug 1717211
| Summary: | Project not terminating without error | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Vladislav Walek <vwalek> |
| Component: | openshift-apiserver | Assignee: | Lukasz Szaszkiewicz <lszaszki> |
| Status: | CLOSED NOTABUG | QA Contact: | Xingxing Xia <xxia> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.11.0 | CC: | aos-bugs, cstark, jokerman, mfojtik, mirollin, mmccomas, nagrawal, pvarma, rekhan, sponnaga, ssadhale, sttts, xxia |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | 3.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-21 09:39:07 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Vladislav Walek
2019-06-04 22:24:53 UTC
Please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1703521#c6 which again refers to https://bugzilla.redhat.com/show_bug.cgi?id=1625194#c25 to see if caused by other aggregated apiserver. Hello Xingxing, what would be the fix as it is not clear from the bugzilla: - run "oc get apiservices | grep False" and open bugzilla about the component? - deleting the "v1beta1.servicecatalog.k8s.io" apiservice - it is still needed? Thx Then I have no idea, need help from Dev colleague. @Michal, could you help check when having time? Saw you "controllers logs", it contains 'unable to register configz...register config "componentconfig" twice', which looks similar to bug 1689000 (see its 11th and 16th comments): I0605 13:28:30.627181 1 controller_manager.go:35] Starting controllers on 0.0.0.0:8444 (v3.11.59) I0605 13:28:30.649975 1 start_kube_scheduler.go:62] `kube-scheduler [--leader-elect=true ...snipped... ... I0605 13:28:30.696360 1 standalone_apiserver.go:101] Started health checks at 0.0.0.0:8444 I0605 13:28:30.722406 1 leaderelection.go:185] attempting to acquire leader lease kube-system/openshift-master-controllers... ... I0605 13:28:30.866861 1 start_kube_controller_manager.go:87] `kube-controller-manager [--kube-api-content-type=application/vnd.kubernetes.protobuf ...snipped... ... E0605 13:28:30.930723 1 controllermanager.go:134] unable to register configz: &{%!c(string=register config "componentconfig" twice)} I0605 13:28:30.930844 1 leaderelection.go:185] attempting to acquire leader lease kube-system/kube-controller-manager... E0605 13:28:31.184642 1 reflector.go:136] k8s.io/client-go/informers/factory.go:130: Failed to list *v1beta1.PodDisruptionBudget: Get https://bdb-pr-vm-master-2:443/apis/policy/v1beta1/poddisruptionbudgets?limit=500&resourceVersion=0: dial tcp 10.88.48.8:443: connect: connection refused Not sure if this causes the terminating issue. @Michal, any idea? Thanks. I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint. This issue was assigned to me just yesterday. It seems it hasn't been updated for a while and all linked customer cases were closed. https://access.redhat.com/support/cases/02408525 and https://access.redhat.com/support/cases/02570051 indicate that the root cause of the issue was a custom finalizer on an object. Thus I'm closing this issue, feel free to reopen. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |