cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3617) Test case test_custom_hostname.TestInstanceNameFlagTrue failed with unexpected vmname
Date Thu, 25 Jul 2013 10:05:49 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719464#comment-13719464
] 

ASF subversion and git services commented on CLOUDSTACK-3617:
-------------------------------------------------------------

Commit 9e8663c7cab525910f26396dc3c58633ae88bfd8 in branch refs/heads/master from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9e8663c ]

CLOUDSTACK-3617: Skip the test if config is not suitable

Provided a utility method to ensure the config is suitable for running
the test. If vm.instancename.flag is unset then skip the tests.

Signed-off-by: Prasanna Santhanam <tsp@apache.org>
(cherry picked from commit 8b8cee52f09f9f2c1b612ece16fc7ffc4b2c9176)

                
> Test case test_custom_hostname.TestInstanceNameFlagTrue failed with unexpected vmname

> --------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3617
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3617
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: 4.2.0
>         Environment: Automation 
> 4.2
>            Reporter: Rayees Namathponnan
>            Assignee: Prasanna Santhanam
>             Fix For: 4.2.0
>
>
> Below 2 test cases failed with unexpected vmname WRT to test case
> integration.component.test_custom_hostname.TestInstanceNameFlagTrue.test_01_user_provided_hostname
	integration.component.test_custom_hostname.TestInstanceNameFlagTrue.test_02_instancename_from_default_configuration

> Observed below error
> VM internal name should match with that of the format
> -------------------- >> begin captured logging << --------------------
> testclient.testcase.TestInstanceNameFlagTrue: DEBUG: Deploying VM in account: test-J0LLUE
> testclient.testcase.TestInstanceNameFlagTrue: DEBUG: Checking if the virtual machine
is created properly or not?
> testclient.testcase.TestInstanceNameFlagTrue: DEBUG: vm.displayname: TestVM, original:
TestVM
> testclient.testcase.TestInstanceNameFlagTrue: DEBUG: select id from account where uuid
= 'fad8043b-9e3c-4dfb-ae9e-4c1da1bd2382';
> testclient.testcase.TestInstanceNameFlagTrue: DEBUG: select id from vm_instance where
uuid = '7816fa2a-45e1-4a56-a0a2-160a40df59bb';
> testclient.testcase.TestInstanceNameFlagTrue: DEBUG: Query result: 280
> testclient.testcase.TestInstanceNameFlagTrue: DEBUG: Internal name: i-214-280-TestVM
> --------------------- >> end captured logging << ---------------------
> Stacktrace
>   File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
>     testMethod()
>   File "/data/Repo2/qa/cloudstack/test/integration/component/test_custom_hostname.py",
line 258, in test_01_user_provided_hostname
>     "VM internal name should match with that of the format"
>   File "/usr/local/lib/python2.7/unittest/case.py", line 494, in assertEqual
>     assertion_func(first, second, msg=msg)
>   File "/usr/local/lib/python2.7/unittest/case.py", line 902, in assertMultiLineEqual
>     self.fail(self._formatMessage(msg, standardMsg))
>   File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
>     raise self.failureException(msg)
> VM internal name should match with that of the format

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message