A second run of setup_all can cause rabbitmq.config to be corrupt

[Vedamurthy Joshi]

R1.10 34
This is a Centos 65 single node setup.
Without installing pkgs, run setup_all once. This sets up /etc/rabbitmq/rabbitmq.config once.
After installing the packages correctly, run setup_all again. Now, the duplicate entries are added to rabbitmq.config as shown below
and rabbitmq-server startup fails.

Logs will be in http://10.204.216.50/Docs/bugs/#

[root@nodea9 rabbitmq]# cat /etc/rabbitmq/rabbitmq.config
[
   {rabbit, [ {tcp_listeners, [{"10.204.216.47", 5672}]},
   {loopback_users, []},
   {log_levels,[{connection, info},{mirroring, info}]} ]
    }
].[
   {rabbit, [ {tcp_listeners, [{"10.204.216.47", 5672}]},
   {loopback_users, []},
   {log_levels,[{connection, info},{mirroring, info}]} ]
    }
].[root@nodea9 rabbitmq]#

[Ignatious Johnson Christopher (ijohnson-x)]

Fixed in Mainline with commit https://github.com/Juniper/contrail-fabric-utils/commit/6f69ddf5cb689ea2502675622f9d7ffd83dc38cd

and in R1.10 with commit https://github.com/Juniper/contrail-fabric-utils/commit/0aebc7e5b67e0795d62fbae8dff03df722cc3e6f