Contrail API showing incorrect details for all the services

[musharani]

API showing 2 values for all the nodes like config-nodes, control-nodes, analytics-nodes, database-nodes and vrouters. one is with host name and the other is hostname.englab.juniper.net.

The value of IP address and version are messed up. This issue is seen in master

Build - master-394

Analytics node:
[
{
href: "https://nodec7.englab.juniper.net:8143/proxy?proxyURL=http://10.204.216.153:8081/analytics/uves/analytics-node/nodec7.englab.juniper.net?flat",
name: "nodec7.englab.juniper.net"
},
{
href: "https://nodec7.englab.juniper.net:8143/proxy?proxyURL=http://10.204.216.153:8081/analytics/uves/analytics-node/nodec57.englab.juniper.net?flat",
name: "nodec57.englab.juniper.net"
},
{
href: "https://nodec7.englab.juniper.net:8143/proxy?proxyURL=http://10.204.216.153:8081/analytics/uves/analytics-node/nodec8?flat",
name: "nodec8"
},
{
href: "https://nodec7.englab.juniper.net:8143/proxy?proxyURL=http://10.204.216.153:8081/analytics/uves/analytics-node/nodec8.englab.juniper.net?flat",
name: "nodec8.englab.juniper.net"
},
{
href: "https://nodec7.englab.juniper.net:8143/proxy?proxyURL=http://10.204.216.153:8081/analytics/uves/analytics-node/nodec57?flat",
name: "nodec57"
},
{
href: "https://nodec7.englab.juniper.net:8143/proxy?proxyURL=http://10.204.216.153:8081/analytics/uves/analytics-node/nodec7?flat",
name: "nodec7"
}
]

Vrouters:
https://nodec7.englab.juniper.net:8143/proxy?proxyURL=http://10.204.216.153:8081/analytics/uves/vrouters

Config Node:
https://nodec7.englab.juniper.net:8143/proxy?proxyURL=http://10.204.216.153:8081/analytics/uves/config-nodes

Databse Node:
https://nodec7.englab.juniper.net:8143/proxy?proxyURL=http://10.204.216.153:8081/analytics/uves/database-nodes

Control Node:
https://nodec7.englab.juniper.net:8143/proxy?proxyURL=http://10.204.216.153:8081/analytics/uves/control-nodes

[Shivayogi Ugaji (shivayogi123)]

sajeesh, can you take a look.

[Sajeesh Mathew (smathew)]

Related to 1794210 commit . Can you please take care of it ?

[Sajeesh Mathew (smathew)]

I am able to reproduce this issue on my local setup with 414 build.

This bug is not present on build 375 (Nov 9 with latest commit id 5518510a8d8bdae1a6c711648d1723185b5a1763) . But it is present on build 386 .

This issue seems to be caused by the commit https://review.opencontrail.org/#/c/47023/
(Bug 1794210 )

Michael, Can you please take care of it ?

[Nagendra Prasath (npchandran)]

FYI

From: Shivayogi Ugaji <email address hidden>
Date: Sunday, December 2, 2018 at 10:07 PM
To: Edouard Thuleau <email address hidden>, Kamal Singh <email address hidden>, Nagendra Maynattamai <email address hidden>, Sahil Sabharwal <email address hidden>, Sajeesh Mathew <email address hidden>, Sathish Holla <email address hidden>, Shivayogi Ugaji <email address hidden>, Yijie Xiao <email address hidden>
Cc: Abhay Joshi <email address hidden>
Subject: ETAs for 5.1 bugs

Hi,

Please update the ETA for your 5.1 bugs listed in the following sheet
https://docs.google.com/spreadsheets/d/1GlAJIc_RvtXUcUZSCJAK9AlHd6HmjUzYLx9bjTlSLGI/edit#gid=0

Regards
Shivayogi

[Nagendra Prasath (npchandran)]

+config team

Thanks Shaju! We’ll use during day time and establish a communication about our usage.

Regards,
Nagendra Prasath

From: "Shaju V.K" <email address hidden>
Date: Tuesday, December 11, 2018 at 11:42 AM
To: Nagendra Maynattamai <email address hidden>
Subject: DCI setup

Hi Nagendra,

Here is the DCI setup details. I have created a screen ‘dev’ and open session for config and neutron are available in tic 0 and tick1. You can login to containers from these screen if needed.

Connect to screen: screen -xr dev

root@66.129.237.139<mailto:root@66.129.237.139>

password: RedHat2018!!

To run the tests.

Example to run with Pdb:

======

sudo ostestr --pdb neutron_tempest_plugin.api.test_security_groups_negative.NegativeSecGroupProtocolTest.test_create_security_group_rule_with_ipv6_protocol_integers

Without pdb to run a single test:
========

sudo ostestr -r neutron_tempest_plugin.api.test_security_groups_negative.NegativeSecGroupProtocolTest.test_create_security_group_rule_with_ipv6_protocol_integers

Note: Please DON’T make any changes in root@66.129.237.139<mailto:root@66.129.237.139> While sharing the setup with your team.

Thanks,
Shaju

[shajuvk (shajuvk)]

Ok.
FYI, the cluster deployment and tempest run takes approximate 6 hrs. If the new trigger happening early morning for example at 6 am, cluster might be available after 12 noon.

Thanks,
Shaju

From: Nagendra Maynattamai <email address hidden>
Date: Tuesday, December 11, 2018 at 12:12 PM
To: "Shaju V.K" <email address hidden>
Cc: Kamal Singh <email address hidden>, Shivayogi Ugaji <email address hidden>, Sajeesh Mathew <email address hidden>
Subject: Re: DCI setup

+config team

Thanks Shaju! We’ll use during day time and establish a communication about our usage.

Regards,
Nagendra Prasath

From: "Shaju V.K" <email address hidden>
Date: Tuesday, December 11, 2018 at 11:42 AM
To: Nagendra Maynattamai <email address hidden>
Subject: DCI setup

Hi Nagendra,

Here is the DCI setup details. I have created a screen ‘dev’ and open session for config and neutron are available in tic 0 and tick1. You can login to containers from these screen if needed.

Connect to screen: screen -xr dev

root@66.129.237.139<mailto:root@66.129.237.139>

password: RedHat2018!!

To run the tests.

Example to run with Pdb:

======

sudo ostestr --pdb neutron_tempest_plugin.api.test_security_groups_negative.NegativeSecGroupProtocolTest.test_create_security_group_rule_with_ipv6_protocol_integers

Without pdb to run a single test:
========

sudo ostestr -r neutron_tempest_plugin.api.test_security_groups_negative.NegativeSecGroupProtocolTest.test_create_security_group_rule_with_ipv6_protocol_integers

Note: Please DON’T make any changes in root@66.129.237.139<mailto:root@66.129.237.139> While sharing the setup with your team.

Thanks,
Shaju

[Nagendra Prasath (npchandran)]

Kuljinder,
After I reimage, I see disk error in b1s7-node2. Please see if anything wrong with the disk.

Also,
I’m planning to use b1s7-node1 and b1s7-node2 to create lab-sim for our config team. could you also allocate us a subnet block to handle ~40 VMs…. (consider using VIPs for HA setups)

Regards,
Nagendra Prasath

[Nagendra Prasath (npchandran)]

I just started another reimage. Will let you know if that resolves. Thx!

Regards,
Nagendra Prasath

From: Nagendra Maynattamai <email address hidden>
Date: Thursday, June 20, 2019 at 3:58 PM
To: Kuljinder Singh <email address hidden>
Cc: Rajit Dang <email address hidden>, Sajeesh Mathew <email address hidden>
Subject: b1s7-node2

Kuljinder,
After I reimage, I see disk error in b1s7-node2. Please see if anything wrong with the disk.

Also,
I’m planning to use b1s7-node1 and b1s7-node2 to create lab-sim for our config team. could you also allocate us a subnet block to handle ~40 VMs…. (consider using VIPs for HA setups)

Regards,
Nagendra Prasath

[Nagendra Prasath (npchandran)]

Kuljinder, second reimage fixed the issue.

Rajit,
Please work on below items
1. Create a contrail cluster R5.1 based with both nodes (have computes in both nodes but all controllers in one node)
2. Get network block from Kuljinder and create a floating ip pool

Sajeesh please guide Rajit through this process. Thanks!

Regards,
Nagendra Prasath
________________________________
From: Nagendra Maynattamai
Sent: Thursday, June 20, 2019 4:00 PM
To: Kuljinder Singh
Cc: Rajit Dang; Sajeesh Mathew
Subject: Re: b1s7-node2

I just started another reimage. Will let you know if that resolves. Thx!

Regards,
Nagendra Prasath

From: Nagendra Maynattamai <email address hidden>
Date: Thursday, June 20, 2019 at 3:58 PM
To: Kuljinder Singh <email address hidden>
Cc: Rajit Dang <email address hidden>, Sajeesh Mathew <email address hidden>
Subject: b1s7-node2

Kuljinder,
After I reimage, I see disk error in b1s7-node2. Please see if anything wrong with the disk.

Also,
I’m planning to use b1s7-node1 and b1s7-node2 to create lab-sim for our config team. could you also allocate us a subnet block to handle ~40 VMs…. (consider using VIPs for HA setups)

Regards,
Nagendra Prasath

[Nagendra Prasath (npchandran)]

- Kuljinder

Can you try libvirt instead of contrail? Looking for a light weight solution here.. first read about libvirt, virsh
Our requirement is to have public ips (lab) for VMs and easy command line to launch VMs, Network so it's easy to automate

Regards,
Nagendra Prasath
________________________________
From: Nagendra Maynattamai
Sent: Thursday, June 20, 2019 5:59 PM
To: Rajit Dang; Sajeesh Mathew
Cc: Kuljinder Singh
Subject: Re: b1s7-node2

Kuljinder, second reimage fixed the issue.

Rajit,
Please work on below items
1. Create a contrail cluster R5.1 based with both nodes (have computes in both nodes but all controllers in one node)
2. Get network block from Kuljinder and create a floating ip pool

Sajeesh please guide Rajit through this process. Thanks!

Regards,
Nagendra Prasath
________________________________
From: Nagendra Maynattamai
Sent: Thursday, June 20, 2019 4:00 PM
To: Kuljinder Singh
Cc: Rajit Dang; Sajeesh Mathew
Subject: Re: b1s7-node2

I just started another reimage. Will let you know if that resolves. Thx!

Regards,
Nagendra Prasath

From: Nagendra Maynattamai <email address hidden>
Date: Thursday, June 20, 2019 at 3:58 PM
To: Kuljinder Singh <email address hidden>
Cc: Rajit Dang <email address hidden>, Sajeesh Mathew <email address hidden>
Subject: b1s7-node2

Kuljinder,
After I reimage, I see disk error in b1s7-node2. Please see if anything wrong with the disk.

Also,
I’m planning to use b1s7-node1 and b1s7-node2 to create lab-sim for our config team. could you also allocate us a subnet block to handle ~40 VMs…. (consider using VIPs for HA setups)

Regards,
Nagendra Prasath

[Nagendra Prasath (npchandran)]

My car windshield has a big crack, need an immediate replacement. will be away between 3pm-5pm

Available over phone.

Regards,
Nagendra Prasath

[Nagendra Prasath (npchandran)]

My car windshield has a big crack, need an immediate replacement. will be away between 3pm-5pm

Available over phone.

Regards,
Nagendra Prasath