Broker.id = 0 for all the control nodes in a HA setup - centOS 7

[Fawad]

2.23 - 127 CentOS7
Hi,
Broker.id = 0 for all the control nodes in a HA setup - centOS 7 after provisioning. This causes an issue which leads to Kafka flaps and your database node goes down. Seems like this issue is not only for 2.23 but for other releases as well pertaining to centOS. After talking to Ranjeet, logging a defect as a place holder.

Please let me know if you need anything else.

Thanks,
~Fawad

[Megh Bhatt (meghb)]

This is not upgrade? If so, then it does not matter, since contrail-alarm-gen and kafka are not going to run.
If upgrade, then you already filed 1562220

Please confirm.

Thanks

Megh

> On Mar 25, 2016, at 5:42 PM, Fawad <email address hidden> wrote:
>
> Private bug reported:
>
> 2.23 - 127 CentOS7
> Hi,
> Broker.id = 0 for all the control nodes in a HA setup - centOS 7 after provisioning. This causes an issue which leads to Kafka flaps and your database node goes down. Seems like this issue is not only for 2.23 but for other releases as well pertaining to centOS. After talking to Ranjeet, logging a defect as a place holder.
>
> Please let me know if you need anything else.
>
> Thanks,
> ~Fawad
>
> ** Affects: juniperopenstack
> Importance: Undecided
> Status: New
>
>
> ** Tags: haproxy
>
> --
> You received this bug notification because you are a member of Contrail
> Systems engineering, which is subscribed to Juniper Openstack.
> https://bugs.launchpad.net/bugs/1562223
>
> Title:
> Broker.id = 0 for all the control nodes in a HA setup - centOS 7
>
> Status in Juniper Openstack:
> New
>
> Bug description:
> 2.23 - 127 CentOS7
> Hi,
> Broker.id = 0 for all the control nodes in a HA setup - centOS 7 after provisioning. This causes an issue which leads to Kafka flaps and your database node goes down. Seems like this issue is not only for 2.23 but for other releases as well pertaining to centOS. After talking to Ranjeet, logging a defect as a place holder.
>
> Please let me know if you need anything else.
>
> Thanks,
> ~Fawad
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juniperopenstack/+bug/1562223/+subscriptions

[Fawad (fshaikh)]

Hi Megh,
Yes, this was an upgrade. I discussed with Ranjeet and we did not know from what release would “kafka” and “alarm-gen” are being supported. If it’s only 3.0 then we can close this defect.

Ccing Ranjeet

Thanks,
~Fawad

On 3/25/16, 6:01 PM, "<email address hidden> on behalf of Megh Bhatt" <<email address hidden> on behalf of <email address hidden>> wrote:

>This is not upgrade? If so, then it does not matter, since contrail-alarm-gen and kafka are not going to run.
>If upgrade, then you already filed 1562220
>
>Please confirm.
>
>Thanks
>
>Megh
>
>> On Mar 25, 2016, at 5:42 PM, Fawad <email address hidden> wrote:
>>
>> Private bug reported:
>>
>> 2.23 - 127 CentOS7
>> Hi,
>> Broker.id = 0 for all the control nodes in a HA setup - centOS 7 after provisioning. This causes an issue which leads to Kafka flaps and your database node goes down. Seems like this issue is not only for 2.23 but for other releases as well pertaining to centOS. After talking to Ranjeet, logging a defect as a place holder.
>>
>> Please let me know if you need anything else.
>>
>> Thanks,
>> ~Fawad
>>
>> ** Affects: juniperopenstack
>> Importance: Undecided
>> Status: New
>>
>>
>> ** Tags: haproxy
>>
>> --
>> You received this bug notification because you are a member of Contrail
>> Systems engineering, which is subscribed to Juniper Openstack.
>> https://bugs.launchpad.net/bugs/1562223
>>
>> Title:
>> Broker.id = 0 for all the control nodes in a HA setup - centOS 7
>>
>> Status in Juniper Openstack:
>> New
>>
>> Bug description:
>> 2.23 - 127 CentOS7
>> Hi,
>> Broker.id = 0 for all the control nodes in a HA setup - centOS 7 after provisioning. This causes an issue which leads to Kafka flaps and your database node goes down. Seems like this issue is not only for 2.23 but for other releases as well pertaining to centOS. After talking to Ranjeet, logging a defect as a place holder.
>>
>> Please let me know if you need anything else.
>>
>> Thanks,
>> ~Fawad
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/juniperopenstack/+bug/1562223/+subscriptions
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1562223
>
>Title:
> Broker.id = 0 for all the control nodes in a HA setup - centOS 7
>
>Status in Juniper Openstack:
> New
>Status in Juniper Openstack r2.20 series:
> New
>
>Bug description:
> 2.23 - 127 CentOS7
> Hi,
> Broker.id = 0 for all the control nodes in a HA setup - centOS 7 after provisioning. This causes an issue which leads to Kafka flaps and your database node goes down. Seems like this issue is not only for 2.23 but for other releases as well pertaining to centOS. After talking to Ranjeet, logging a defect as a place holder.
>
> Please let me know if you need anything else.
>
> Thanks,
> ~Fawad
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/juniperopenstack/+bug/1562223/+subscriptions