Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: prashanthvarma <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
References: <git-pr-1577-cloudstack@git.apache.org>
In-Reply-To: <git-pr-1577-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack issue #1577: CLOUDSTACK-9321 : Multiple Internal LB rules (more t...
Content-Type: text/plain
Message-Id: <20161121181819.6EBC0E00E5@git1-us-west.apache.org>
Date: Mon, 21 Nov 2016 18:18:19 +0000 (UTC)
archived-at: Mon, 21 Nov 2016 18:18:21 -0000

Github user prashanthvarma commented on the issue:

    https://github.com/apache/cloudstack/pull/1577
  
    @rhtyd @jburwell I have briefly investigated the above failed tests "test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL" and "test_oobm_enabledisable_across_clusterzones", here are my findings:
    
    1) "test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL " fails during establishment of SSH connection to the VM via its public IP (SSH connection failed to setup, timeout error). Moreover, this test passed in the previous blueorangutan run (refer my previous comment on investigations of the previous blueorangutan run).
    
    2) "test_oobm_enabledisable_across_clusterzones" failure looks like a test environment (i.e. host hardware issue). Moreover, this test passed in the previous blueorangutan run (refer my previous comment on investigations of the previous blueorangutan run).
    
    Here is the error from the logs:
    errorcode : 530, errortext : u'Out-of-band Management action (STATUS) on host (d2049cf2-47ba-4a81-8e72-d01c1dc77dd0) failed with error: > Error: no response from RAKP 1 message\nError: Unable to establish IPMI v2 / RMCP+ session\nRunning Get PICMG Properties my_addr 0x20, transit 0, target 0x20\nNo Response from Get PICMG Properties\nNo PICMG Extenstion discovered\nUnable to get Chassis Power Status\n'}
    
    IMHO, the above failing tests are most likely due to test environment issues, and has nothing to do with the code changes in this PR.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---