Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/381#issuecomment-110800931
@isoutham
The KVM tests are running. I had problems with my environment (as you might
have seen on Slcak) and had to restart them. However, when I try to run the
tests on XenServer62 I get the following error:
CSLog: CRITICAL: EXCEPTION: None: ['Traceback (most recent call last):\n',
' File "/usr/lib/python2.7/site-packages/nose-1.3.6-py2.7.egg/nose/suite.py",
line 209, in run\n self.setUp()\n', ' File
"/usr/lib/python2.7/site-packages/nose-1.3.6-py2.7.egg/nose/suite.py", line
292, in setUp\n self.setupContext(ancestor)\n', ' File
"/usr/lib/python2.7/site-packages/nose-1.3.6-py2.7.egg/nose/suite.py", line
315, in setupContext\n try_run(context, names)\n', ' File
"/usr/lib/python2.7/site-packages/nose-1.3.6-py2.7.egg/nose/util.py", line 471,
in try_run\n return func()\n', ' File
"/data/git/cs2/cloudstack/test/integration/component/test_vpc_network_pfrules.py",
line 195, in setUpClass\n cls.zone.id,\n', "AttributeError: 'str' object
has no attribute 'id'\n"]
On line 195 we have the following:
cls.template = get_template(
cls.api_client,
195 here ===> cls.zone.id,
cls.services["ostype"]
)
It seems that the test can't retrieve the zone when using XenServer, which
is very weird.
As I mentioned above, KVM runs just fine! Tests haven't completed yet, but
everything seems okay:
====Trying SSH Connection: Host:192.168.23.5 User:root
Port:22 RetryCnt:14===
====Trying SSH Connection: Host:192.168.23.5 User:root
Port:22 RetryCnt:14===
===SSH to Host 192.168.23.5 port : 22 SUCCESSFUL===
===SSH to Host 192.168.23.5 port : 22 SUCCESSFUL===
=== TestName: test_02_network_services_VPC_CreatePF | Status : SUCCESS ===
Do you have any idea what that might be?
Cheers,
Wilder
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
