Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Addresses (broker pods) are not fully deleted

See original GitHub issue

Describe the bug During running shared test suite we can see that broker pods in infra namespaces are not deleted when addresses are removed.

It caused fails in our systemtests suite because pods consumes all resources on nodes so another tests cannot create another address (pods)

Additional context oc get events

2019-11-12T11:18:06Z   2019-11-12T10:03:20Z   331       standard-controller.1070108445                       Address       <none>    Warning   BrokerDeleteFailed   standard-controller      Error deleting broker cluster broker-b41e7da-pj2k: Failure executing: PATCH at: https://172.30.0.1/apis/apps/v1/namespaces/enmasse-infra/statefulsets/broker-b41e7da-pj2k. Message: StatefulSet.apps "broker-b41e7da-pj2k" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden.. Received status: Status(apiVersion=v1, code=422, details=StatusDetails(causes=[StatusCause(field=spec, message=Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden., reason=FieldValueForbidden, additionalProperties={})], group=apps, kind=StatefulSet, name=broker-b41e7da-pj2k, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=StatefulSet.apps "broker-b41e7da-pj2k" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden., metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Invalid, status=Failure, additionalProperties={}).

Issue Analytics

State:
Created 4 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

lulfcommented, Nov 13, 2019

@kornys @k-wall I’ll have a look, its probably related to CRD refactor

0reactions

k-wallcommented, Dec 3, 2019

@kornys I think this issue is now closable.

Top Results From Across the Web

Force Delete StatefulSet Pods - Kubernetes

This page shows how to delete Pods which are part of a stateful set, and explains the considerations to keep in mind when...

Chapter 4. Configuring Operator-based broker deployments

When you have finished configuring the CR, click Create. (Optional) To delete an address and queue previously added to your deployment using a...

Managing Pods | OpenShift Container Platform 3.11

You can make a pod critical by adding the scheduler.alpha.kubernetes.io/critical-pod annotation to the pod specification so that the descheduler will not remove ......

How do I delete a default AKS node pool when I get an error ...

The solution does not work. I keep getting the same thing whatever I try: the agent pool cannot be deleted because it is...

Troubleshoot issues on Kubernetes/OpenShift | Dynatrace Docs

If your application has already been running, restarting its containers will have the very same effect. No pods scheduled on control-plane nodes. DaemonSet....