Hi Ram ,

Will update you in some time.

Regards,

Mithun

From: Abhay Joshi <email address hidden>
Date: Wednesday, 22 August 2018 at 2:37 AM
To: Ram Yadav <email address hidden>, Sudheendra Rao <email address hidden>, Aswani Kumar Gaddam <email address hidden>, Jeba Paulaiyan <email address hidden>, Vinay Vithal Mahuli <email address hidden>, Mithun Mistry <email address hidden>
Cc: Sandip Dey <email address hidden>, Sachchidanand Vaidya <email address hidden>, Marcin Orkiszewski <email address hidden>, Adrian Szczepański <email address hidden>, Amudha R <email address hidden>
Subject: Re: steps to run sanity on vCenter local setup's

Hi Vinay/Mithun,

Can you please help Ram?

Thanks,

Abhay

From: Ram Yadav <email address hidden>
Date: Monday, August 20, 2018 at 5:29 PM
To: Sudheendra Rao <email address hidden>, Aswani Kumar Gaddam <email address hidden>, Jeba Paulaiyan <email address hidden>, Abhay Joshi <email address hidden>
Cc: Sandip Dey <email address hidden>, Sachchidanand Vaidya <email address hidden>, Marcin Orkiszewski <email address hidden>, Adrian Szczepański <email address hidden>, Amudha R <email address hidden>
Subject: Re: steps to run sanity on vCenter local setup's

Hi Abhay,
I tried getting the image from Bangalore registry but it timeouts.


TASK [install_contrail : update image] *************************************************************************************************************************************************************

failed: [10.84.16.23] (item=contrail-node-init) => {"changed": true, "cmd": "docker pull 10.214.217.152:5000/contrail-node-init:ocata-5.0-168", "delta": "0:00:45.032686", "end": "2018-08-20 16:04:29.251094", "item": "contrail-node-init", "msg": "non-zero return code", "rc": 1, "start": "2018-08-20 16:03:44.218408", "stderr": "Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout", "stderr_lines": ["Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout"], "stdout": "", "stdout_lines": []}

failed: [10.84.16.24] (item=contrail-node-init) => {"changed": true, "cmd": "docker pull 10.214.217.152:5000/contrail-node-init:ocata-5.0-168", "delta": "0:00:45.035015", "end": "2018-08-20 16:04:29.273194", "item": "contrail-node-init", "msg": "non-zero return code", "rc": 1, "start": "2018-08-20 16:03:44.238179", "stderr": "Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout", "stderr_lines": ["Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout"], "stdout": "", "stdout_lines": []}

failed: [10.84.16.23] (item=contrail-nodemgr) => {"changed": true, "cmd": "docker pull 10.214.217.152:5000/contrail-nodemgr:ocata-5.0-168", "delta": "0:00:45.030576", "end": "2018-08-20 16:05:14.792332", "item": "contrail-nodemgr", "msg": "non-zero return code", "rc": 1, "start": "2018-08-20 16:04:29.761756", "stderr": "Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout", "stderr_lines": ["Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout"], "stdout": "", "stdout_lines": []}

failed: [10.84.16.24] (item=contrail-nodemgr) => {"changed": true, "cmd": "docker pull 10.214.217.152:5000/contrail-nodemgr:ocata-5.0-168", "delta": "0:00:45.029793", "end": "2018-08-20 16:05:14.790406", "item": "contrail-nodemgr", "msg": "non-zero return code", "rc": 1, "start": "2018-08-20 16:04:29.760613", "stderr": "Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout", "stderr_lines": ["Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout"], "stdout": "", "stdout_lines": []}

failed: [10.84.16.23] (item=contrail-vrouter-kernel-init) => {"changed": true, "cmd": "docker pull 10.214.217.152:5000/contrail-vrouter-kernel-init:ocata-5.0-168", "delta": "0:00:45.025981", "end": "2018-08-20 16:06:00.304874", "item": "contrail-vrouter-kernel-init", "msg": "non-zero return code", "rc": 1, "start": "2018-08-20 16:05:15.278893", "stderr": "Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout", "stderr_lines": ["Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout"], "stdout": "", "stdout_lines": []}

failed: [10.84.16.24] (item=contrail-vrouter-kernel-init) => {"changed": true, "cmd": "docker pull 10.214.217.152:5000/contrail-vrouter-kernel-init:ocata-5.0-168", "delta": "0:00:45.029379", "end": "2018-08-20 16:06:00.338697", "item": "contrail-vrouter-kernel-init", "msg": "non-zero return code", "rc": 1, "start": "2018-08-20 16:05:15.309318", "stderr": "Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout", "stderr_lines": ["Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout"], "stdout": "", "stdout_lines": []}

failed: [10.84.16.23] (item=contrail-vrouter-agent) => {"changed": true, "cmd": "docker pull 10.214.217.152:5000/contrail-vrouter-agent:ocata-5.0-168", "delta": "0:00:45.028958", "end": "2018-08-20 16:06:45.814656", "item": "contrail-vrouter-agent", "msg": "non-zero return code", "rc": 1, "start": "2018-08-20 16:06:00.785698", "stderr": "Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout", "stderr_lines": ["Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout"], "stdout": "", "stdout_lines": []}

failed: [10.84.16.24] (item=contrail-vrouter-agent) => {"changed": true, "cmd": "docker pull 10.214.217.152:5000/contrail-vrouter-agent:ocata-5.0-168", "delta": "0:00:45.032826", "end": "2018-08-20 16:06:45.886996", "item": "contrail-vrouter-agent", "msg": "non-zero return code", "rc": 1, "start": "2018-08-20 16:06:00.854170", "stderr": "Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout", "stderr_lines": ["Error response from daemon: Get https://10.214.217.152:5000/v1/_ping: dial tcp 10.214.217.152:5000: i/o timeout"], "stdout": "", "stdout_lines": []}

       to retry, use: --limit @/root/contrail-ansible-deployer/playbooks/install_contrail.retry



PLAY RECAP *****************************************************************************************************************************************************************************************

10.84.16.10                : ok=12   changed=4    unreachable=0    failed=1

10.84.16.23                : ok=18   changed=6    unreachable=0    failed=1

10.84.16.24                : ok=18   changed=6    unreachable=0    failed=1

localhost                  : ok=33   changed=1    unreachable=0    failed=0

Can you ask the ci team to sync up the image from ocata-5.0-168 Bangalore registry to sunnyvale ci-repo registry?

Thanks,
Ram


From: Ram Yadav <email address hidden>
Date: Monday, August 20, 2018 at 3:08 PM
To: Sudheendra Rao <email address hidden>, Aswani Kumar Gaddam <email address hidden>, Jeba Paulaiyan <email address hidden>, Abhay Joshi <email address hidden>
Cc: Sandip Dey <email address hidden>, Sachchidanand Vaidya <email address hidden>, Marcin Orkiszewski <email address hidden>, Adrian Szczepański <email address hidden>, Amudha R <email address hidden>
Subject: Re: steps to run sanity on vCenter local setup's

Forgot to add Jeba and abhay.

From: Ram Yadav <email address hidden>
Date: Monday, August 20, 2018 at 3:07 PM
To: Sudheendra Rao <email address hidden>, Aswani Kumar Gaddam <email address hidden>
Cc: Sandip Dey <email address hidden>, Sachchidanand Vaidya <email address hidden>, Marcin Orkiszewski <email address hidden>, Adrian Szczepański <email address hidden>, Amudha R <email address hidden>
Subject: Re: steps to run sanity on vCenter local setup's

+jeba, abhay.

Hi Jeba/Abhay,
Where to find release ocata-5.0-168?
I couldn’t find it on ci-repo.englab.juniper.net (10.84.5.81:5010).

Thanks,
Ram

From: Sudheendra Rao <email address hidden>
Date: Monday, August 20, 2018 at 1:04 PM
To: Ram Yadav <email address hidden>, Aswani Kumar Gaddam <email address hidden>
Cc: Sandip Dey <email address hidden>, Sachchidanand Vaidya <email address hidden>, Marcin Orkiszewski <email address hidden>, Adrian Szczepański <email address hidden>, Amudha R <email address hidden>
Subject: Re: steps to run sanity on vCenter local setup's

Ram,

   On this setup also with R5.0 the problem was seen and both these setups (Sandip’s & Aswani’s) are using same vcenter server.
So problem doesn’t seems to be with vcenter server version.

Can you please update your finding with R5.0 on your setup?

Thanks,
Sudhee.

From: Ram Yadav <email address hidden>
Date: Tuesday, 21 August 2018 at 1:26 AM
To: Aswani Kumar Gaddam <email address hidden>, Sudheendra Rao <email address hidden>
Cc: Sandip Dey <email address hidden>, Sachchidanand Vaidya <email address hidden>, Marcin Orkiszewski <email address hidden>, Adrian Szczepański <email address hidden>, Amudha R <email address hidden>
Subject: Re: steps to run sanity on vCenter local setup's

Can we try similar setup to where the problem was recreated on 5.0 ?

From: Aswani Kumar Gaddam <email address hidden>
Date: Monday, August 20, 2018 at 12:41 PM
To: Ram Yadav <email address hidden>, Sudheendra Rao <email address hidden>
Cc: Sandip Dey <email address hidden>, Sachchidanand Vaidya <email address hidden>, Marcin Orkiszewski <email address hidden>, Adrian Szczepański <email address hidden>, Amudha R <email address hidden>
Subject: Re: steps to run sanity on vCenter local setup's

Ram,

Tried mainline-ocata-235 single interface
Not able to reproduce the problem
Launched like 8 vms manually and through script all of them got ip.

Thanks,
Aswani Kumar

From: Ram Yadav <email address hidden>
Date: Monday, 20 August 2018 at 11:49 PM
To: Madhava Rao Sudheendra Rao <email address hidden>
Cc: Sandip Dey <email address hidden>, Aswani Kumar Gaddam <email address hidden>, Sachchidanand Vaidya <email address hidden>, Marcin Orkiszewski <email address hidden>, Adrian Szczepański <email address hidden>, Amudha R <email address hidden>
Subject: Re: steps to run sanity on vCenter local setup's

Sudhee,
Let us know when this fix is checked-in, lot of people will start using the test containers and we don’t want this to be the first issue to be looked at.

Thanks,
Ram

From: Sudheendra Rao <email address hidden>
Date: Saturday, August 18, 2018 at 8:26 PM
To: Ram Yadav <email address hidden>
Cc: Sandip Dey <email address hidden>, Aswani Kumar Gaddam <email address hidden>, Sachchidanand Vaidya <email address hidden>, Marcin Orkiszewski <email address hidden>, Adrian Szczepański <email address hidden>, Amudha R <email address hidden>
Subject: Re: steps to run sanity on vCenter local setup's

Hi Ram,

    The error is same as that we saw earlier and we can make out that it’s not fixed.
Anyways we will fix this, but is there a requirement that you have to use SRV1 only and not server1?
If there is no requirement then it just a matter of changing the name in your vcenter_vars.yaml and you are not blocked from testing.

Thanks,
Sudhee.
Sent from my iPhone

On 19-Aug-2018, at 3:38 AM, Ram Yadav <<email address hidden><mailto:<email address hidden>>> wrote:
Hi Sudhee,
I picked the latest master test container from master 241, I thought Sandip removed the dependency and checked in the fix.
Can you have him check-in the fix?

Regards,
Ram

From: Sudheendra Rao <<email address hidden><mailto:<email address hidden>>>
Date: Saturday, August 18, 2018 at 4:15 AM
To: Ram Yadav <<email address hidden><mailto:<email address hidden>>>, Sandip Dey <<email address hidden><mailto:<email address hidden>>>, Aswani Kumar Gaddam <<email address hidden><mailto:<email address hidden>>>
Cc: Sachchidanand Vaidya <<email address hidden><mailto:<email address hidden>>>, Marcin Orkiszewski <<email address hidden><mailto:<email address hidden>>>, Adrian Szczepański <<email address hidden><mailto:<email address hidden>>>, Amudha R <<email address hidden><mailto:<email address hidden>>>
Subject: Re: steps to run sanity on vCenter local setup's

Hi Ram,

    Sandip had already mentioned that automation code expects that vcenter_vars.yaml has ‘server1’ only under ‘vcenter_servers’, anything else will result in error.

Change all occurrence of SRV1 in vcenter_vars.yaml to server1 and launch new test container using test_runner.sh
I tried and it got past that stage, but seeing below error, I don’t understand this, please check – the test container is ab0e1c12eb88

[root@ab0e1c12eb88 contrail-test]# python -m testtools.run scripts.vm_regression.test_vm_basic.TestBasicVMVN.test_ping_within_vn
:
:

[root@10.84.16.10<mailto:root@10.84.16.10>] out: Created symlink from /etc/systemd/system/multi-user.target.wants/nfs-server.service to /usr/lib/systemd/system/nfs-server.service.
[root@10.84.16.10<mailto:root@10.84.16.10>] out:

[root@10.84.16.10<mailto:root@10.84.16.10>] sudo: systemctl start nfs-server.service
======================================================================
ERROR: setUpClass (scripts.vm_regression.test_vm_basic.TestBasicVMVN)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "scripts/vm_regression/test_vm_basic.py", line 27, in setUpClass
    super(TestBasicVMVN, cls).setUpClass()
  File "scripts/vm_regression/base.py", line 12, in setUpClass
    super(BaseVnVmTest, cls).setUpClass()
  File "test_v1.py", line 38, in setUpClass
    cls.admin_isolated_creds.setUp()
  File "common/isolated_creds.py", line 132, in setUp
    password=self.password)
  File "common/connections.py", line 68, in __init__
    self.vnc_lib = self.get_vnc_lib_h()
  File "common/connections.py", line 167, in get_vnc_lib_h
    env[attr].setUp()
  File "/contrail-test/fixtures/vnc_api_test.py", line 113, in setUp
    if self.orch:
  File "/contrail-test/fixtures/vnc_api_test.py", line 178, in orch
    self._orch = self.get_orch_h()
  File "/contrail-test/fixtures/vnc_api_test.py", line 201, in get_orch_h
    logger=self.logger)
  File "/contrail-test/fixtures/vcenter.py", line 144, in __init__
    self._nfs_ds = NFSDatastore(self._inputs, self)
  File "tcutils/util.py", line 997, in __call__
    Singleton, cls).__call__(*args, **kwargs)
  File "/contrail-test/fixtures/vcenter.py", line 92, in __init__
    host.configManager.datastoreSystem.CreateNasDatastore(spec)
  File "/usr/lib/python2.7/site-packages/pyVmomi/VmomiSupport.py", line 580, in <lambda>
    self.f(*(self.args + (obj,) + args), **kwargs)
  File "/usr/lib/python2.7/site-packages/pyVmomi/VmomiSupport.py", line 386, in _InvokeMethod
    return self._stub.InvokeMethod(self, info, args)
  File "/usr/lib/python2.7/site-packages/pyVmomi/SoapAdapter.py", line 1366, in InvokeMethod
    raise obj # pylint: disable-msg=E0702
vim.fault.DuplicateName: (vim.fault.DuplicateName) {
   dynamicType = <unset>,
   dynamicProperty = (vmodl.DynamicProperty) [],
   msg = "The name 'nfs-ds' already exists.",
   faultCause = <unset>,
   faultMessage = (vmodl.LocalizableMessage) [],
   name = 'nfs-ds',
   object = 'vim.Datastore:10.84.16.10:/nfs'
}

Ran 0 tests in 25.285s
FAILED (failures=1)


Thanks,
Sudhee.

From: Ram Yadav <<email address hidden><mailto:<email address hidden>>>
Date: Saturday, 18 August 2018 at 6:21 AM
To: Sandip Dey <<email address hidden><mailto:<email address hidden>>>
Cc: Sachchidanand Vaidya <<email address hidden><mailto:<email address hidden>>>, Sandip Dey <<email address hidden><mailto:<email address hidden>>>, Marcin Orkiszewski <<email address hidden><mailto:<email address hidden>>>, Sudheendra Rao <<email address hidden><mailto:<email address hidden>>>, Adrian Szczepański <<email address hidden><mailto:<email address hidden>>>, Amudha R <<email address hidden><mailto:<email address hidden>>>
Subject: Re: steps to run sanity on vCenter local setup's

Hi Sandip,
I pulled in the docker image:
contrail-test-test:master-221

And followed the steps for single sanity test case run.
I’m getting the following error:

ERROR: setUpClass (scripts.vm_regression.test_vm_basic.TestBasicVMVN)

----------------------------------------------------------------------

Traceback (most recent call last):

  File "scripts/vm_regression/test_vm_basic.py", line 27, in setUpClass

    super(TestBasicVMVN, cls).setUpClass()

  File "scripts/vm_regression/base.py", line 12, in setUpClass

    super(BaseVnVmTest, cls).setUpClass()

  File "test_v1.py", line 13, in setUpClass

    super(BaseTestCase_v1, cls).setUpClass()

  File "test.py", line 79, in setUpClass

    cls.inputs = ContrailTestInit(cls.input_file,logger = cls.logger)

  File "common/contrail_test_init.py", line 853, in __init__

    self.inputs = TestInputs(input_file, self.logger)

  File "tcutils/util.py", line 997, in __call__

    Singleton, cls).__call__(*args, **kwargs)

  File "common/contrail_test_init.py", line 102, in __init__

    self.parse_yml_file()

  File "common/contrail_test_init.py", line 589, in parse_yml_file

    self.vcenter_dc = _parse_vcenter.vcenter_dc

  File "common/contrail_test_init.py", line 1466, in vcenter_dc
























Test container is spawned on 10.84.16.10.

/root/contrail-ansible-deployer has the contrail_test_input.yml and vcenter_vars.yml













Thanks,

Ram












From: Ram Yadav <<email address hidden><mailto:<email address hidden>>>
Date: Tuesday, August 14, 2018 at 4:31 PM
To: Adrian Szczepański <<email address hidden><mailto:<email address hidden>>>, Amudha R <<email address hidden><mailto:<email address hidden>>>
Cc: Sachchidanand Vaidya <<email address hidden><mailto:<email address hidden>>>, Sandip Dey <<email address hidden><mailto:<email address hidden>>>, Marcin Orkiszewski <<email address hidden><mailto:<email address hidden>>>
Subject: steps to run sanity on vCenter local setup's

Hello,

Below is the instruction to run sanity

1.wget https://github.com/Juniper/contrail-test/raw/master/testrunner.sh
2.docker pull 10.204.217.152:5000/contrail-test-test:ocata-5.0-<build-id>
3../testrunner.sh run -s -P contrail_test_input.yml,vcenter_vars.yml 10.204.217.152:5000/contrail-test-test:ocata-5.0-<build-id>
4.cd contrail-test
5.export TEST_CONFIG_FILE=contrail_test_input_useit.yaml
6./run_tests.sh -T venter --send-mail -















To run a single test case
1.wget https://github.com/Juniper/contrail-test/raw/master/testrunner.sh
2.docker pull 10.204.217.152:5000/contrail-test-test:ocata-5.0-<build-id>
3../testrunner.sh run -s -P contrail_test_input.yml,vcenter_vars.yml 10.204.217.152:5000/contrail-test-test:ocata-5.0-<build-id>
4.cd contrail-test
5.export PYTHONPATH=$PATH:$PWD:$PWD/fixtures:$PWD/scripts
6.export TEST_CONFIG_FILE=contrail_test_input_useit.yaml
7.python -m testtools.run scripts.vm_regression.test_vm_basic.TestBasicVMVN.test_ping_within_vn

Docker pull needs to be done on ci-repo.englab.juniper.net<http://ci-repo.englab.juniper.net> or local repo as mentioned in the above step which is Bangalore local repo.

Apart from this you will need set of vmdk file which was copied by Sandip Dey at some sunnyvale location.

Sandip,
Can provide detail on the file’s that we need to copy say to codilime’s server locally for sanity to run on there setup?

Thanks,
Ram