default install not working, missing execution environment

[Christian Ehrhardt ]

As installed by default the service will immediately fail.

● rabbitmq-server.service - RabbitMQ Messaging Server
   Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2018-10-15 14:07:00 UTC; 55s ago
  Process: 11537 ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmq-server-wait (code=exited, status=2)
  Process: 11536 ExecStart=/usr/sbin/rabbitmq-server (code=killed, signal=TERM)
 Main PID: 11536 (code=killed, signal=TERM)

Oct 15 14:07:00 c systemd[1]: Starting RabbitMQ Messaging Server...
Oct 15 14:07:00 c rabbitmq[11537]: /usr/lib/rabbitmq/bin/rabbitmq-server-wait: 1: /usr/lib/rabbitmq/bin/rabbitmq-server-wait: dirname: not found
Oct 15 14:07:00 c rabbitmq[11537]: /usr/lib/rabbitmq/bin/rabbitmq-server-wait: 20: .: Can't open /rabbitmq-env
Oct 15 14:07:00 c systemd[1]: rabbitmq-server.service: Control process exited, code=exited status=2
Oct 15 14:07:00 c rabbitmq[11536]: /usr/sbin/rabbitmq-server: 1: /usr/sbin/rabbitmq-server: basename: not found
Oct 15 14:07:00 c systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'.
Oct 15 14:07:00 c systemd[1]: Failed to start RabbitMQ Messaging Server.

That makes install/upgrades sad and also should not happen.
We need to dig into how it should work and fix it up.

Repro:
 cosmic-container:
 $ apt install rabbitmq-server

[Christian Ehrhardt  (paelzer)]

Could be tackled together with bug 1784757

[Christian Ehrhardt  (paelzer)]

I wondered as the code is the same in Bionic&Cosmic.
And this is used in our openstack a lot.

So I spawned two KVMs B&C and both work fine.
Doing so again with two containers works as well.

So my initial test container must have had some bad broken config triggering this.
Sorry for the noise -> invalid.