-
Bug
-
Resolution: Done
-
Major
-
AMQ 7.7.0.CR4, AMQ 7.8.0.dev
-
None
-
None
-
False
-
False
-
Undefined
-
-
Applying memory limit to a broker pod leads to an error during spawn (about 10 minutes after initial pod creation):
(combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = reserving pod sandbox name: error reserving pod name k8s_ex-aao-ss-0_mkr-bug3_800a41f6-4fb1-4c55-bf16-b37fee0ac4d2_0 for id e26a7213d4a07283cb717c70733a7f11564ea4610de809f90165fa897cfd1841: name is reserved
Pod is stuck in "ContainerCreating" state. I've tried to increase and decrease memory to different values, and only thing which affects this is the fact of resource limit existing. If there is no memory limit in CR yaml, then all is fine, as soon as any memory limit is applied, pod fails to start.
- is caused by
-
ENTMQBR-3445 Doc: [OCP] Provide a mechanism to change stateful set resource limits via operator in AMQ 7 on OCP
- Closed