Bug 1585237
| Summary: | Kuryr-controller crashes when creating a NodePort type service | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Jon Uriarte <juriarte> |
| Component: | openstack-kuryr-kubernetes | Assignee: | Antoni Segura Puimedon <asegurap> |
| Status: | CLOSED ERRATA | QA Contact: | Jon Uriarte <juriarte> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 13.0 (Queens) | CC: | asegurap, jamsmith, jjoyce, joflynn, jschluet, tsedovic |
| Target Milestone: | z2 | Keywords: | Triaged, ZStream |
| Target Release: | 13.0 (Queens) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-kuryr-kubernetes-0.4.3-2.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Kuryr supports clusterIP and Loadbalancer services and reads parameters specific to these services. Nodeport's specification is different and does not have the same parameters.
When the controller tried to access parameters that are not present in Nodeport, the controller crashed. The user must not create Nodeport services because they are not supported. However, Nodeport services should not crash the controller.
Now the controller ignores the Nodeport services and the controller does not crash when Nodeport services are present.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-08-29 16:32:35 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
Jon Uriarte
2018-06-01 15:26:02 UTC
Fixed upstream: https://review.openstack.org/#/c/571719/ And backported to Queens: https://review.openstack.org/#/c/572024/ This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field. Verified on OSP 13 2018-08-16.1 puddle / openshift-ansible-3.10.34-1, and: openstack-kuryr-kubernetes-cni-0.4.3-2.el7ost.noarch openstack-kuryr-kubernetes-controller-0.4.3-2.el7ost.noarch Verification steps: 1. Deploy OCP on OSP with kuryr 2. From master node: $ oc new-project test $ oc run --image=kuryr/demo demo $ oc get pods NAME READY STATUS RESTARTS AGE demo-1-5pgdh 1/1 Running 0 1m $oc -n openshift-infra get pods NAME READY STATUS RESTARTS AGE bootstrap-autoapprover-0 1/1 Running 0 1h kuryr-cni-ds-7klr7 2/2 Running 0 1h kuryr-cni-ds-dfr9j 2/2 Running 0 1h kuryr-cni-ds-qm6tp 2/2 Running 0 1h kuryr-cni-ds-vmhrr 2/2 Running 0 1h kuryr-controller-59fc7f478b-cbqjf 1/1 Running 0 1h $ oc expose dc/demo --port 80 --target-port 8080 --type=NodePort $ oc get pods NAME READY STATUS RESTARTS AGE demo-1-5pgdh 1/1 Running 0 2m $ oc -n openshift-infra get pods NAME READY STATUS RESTARTS AGE bootstrap-autoapprover-0 1/1 Running 0 1h kuryr-cni-ds-7klr7 2/2 Running 0 1h kuryr-cni-ds-dfr9j 2/2 Running 0 1h kuryr-cni-ds-qm6tp 2/2 Running 0 1h kuryr-cni-ds-vmhrr 2/2 Running 0 1h kuryr-controller-59fc7f478b-cbqjf 1/1 Running 0 1h kuryr-controller pod does not crash/restart, it remains in Running status, and does not show any error message on its logs. 3. Delete the project: $ oc delete project test Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2573 |