minikube: Rabbit MQ does not start correctly in minikube 1.5.0

The exact command to reproduce the issue:

{
   "apiVersion": "apps/v1",
   "kind": "Deployment",
   "metadata": {
      "labels": {
         "name": "rabbit"
      },
      "name": "rabbit"
   },
   "spec": {
      "replicas": 1,
      "selector": {
         "matchLabels": {
            "name": "rabbit"
         }
      },
      "template": {
         "metadata": {
            "labels": {
               "name": "rabbit"
            }
         },
         "spec": {
            "containers": [
               {
                  "image": "rabbitmq:3.8-management",
                  "imagePullPolicy": "IfNotPresent",
                  "name": "rabbit",
                  "ports": [
                     {
                        "containerPort": 5672
                     },
                     {
                        "containerPort": 15672
                     }
                  ]
               }
            ]
         }
      }
   }
}

The full output of the command that failed: There was no log records from rabbitmq container, and no one is listen on ports 5672 and 15672 but this deployment worked fine on version 1.4

The output of the minikube logs command:

[minikube.log](https://github.com/kubernetes/minikube/files/3783720/minikube.log)

The operating system version: Linux hobo 5.0.0-32-generic #34~18.04.2-Ubuntu SMP Thu Oct 10 10:36:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 2
Comments: 23 (1 by maintainers)

Most upvoted comments

1.5.1 fixes it for me too (for all services that were broken with 1.5.0)

andrebrait on Oct 30, 2019

Can someone confirm whether or not this is fixed by the v1.5.1 release?

tstromberg on Oct 30, 2019

I am still testing, but there seems to be some specific misbehavior on 1.15 launched VMs for ALL erlang processes (of which RabbitMQ is one example)

running e.g. kubectl run --rm -it --image elixir:1.9.0-alpine iex hangs after process start but prior to giving an iex prompt* for ~9 minutes on my machine. Similar slow downs can be seen with simple hello world elixir programs and mix tasks in a on-cluster docker build.

The problem persists across kubernetes versions of at least 1.16.2 and 1.14.7 (so I imagine more).

For me the hang also includes a high CPU load.

There are no such problems when running python workloads on the same cluster.

*it is notable that the BEAM has started insofar as sending an interrupt gives the conventional erlang BREAK prompt

BREAK: (a)bort (c)ontinue (p)roc info (i)nfo (l)oaded
       (v)ersion (k)ill (D)b-tables (d)istribution

but the process as all seems unable to start in a timely fashion

donaldguy on Oct 29, 2019