Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/558#issuecomment-118881977
Hi @isoutham
Unfortunately the test is failing. Details about my environment and results
below:
Management Server running on CentOS 7.1
Multi-host zone: 2 XenServer 6.2 hosts
It all starts fine: rVPC, tiers and VMs are created. After this...
self.delete_nat_rules()
self.check_master_status(1)
self.do_vpc_test(True)
All the tests work. However, the call to start the router doesnt
self.start_router()
self.add_nat_rules()
time.sleep(60)
self.check_master_status(2)
self.do_vpc_test(False)
The router never starts and the rules are not applied. I tried to give it a
chance and restarted it manually (yes, deliberate action). After the router was
running again, we got timeouts.
I checked the IPs and found out they had no PF rules to port 22, although
the ACLs were properly configured. I added the PF rules and after a while I got:
===SSH to Host 192.168.23.8 port : 22 SUCCESSFUL===
I also connected to the VM manually"
Last login: Mon Jul 6 12:13:11 on ttys004
sbpltk1zffh04:asf_cloudstack wrodrigues$ ping 192.168.23.7
PING 192.168.23.7 (192.168.23.7): 56 data bytes
64 bytes from 192.168.23.7: icmp_seq=0 ttl=63 time=4.225 ms
64 bytes from 192.168.23.7: icmp_seq=1 ttl=63 time=4.085 ms
^C
--- 192.168.23.7 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 4.085/4.155/4.225/0.070 ms
sbpltk1zffh04:asf_cloudstack wrodrigues$ ssh [email protected]
The authenticity of host '192.168.23.7 (192.168.23.7)' can't be established.
RSA key fingerprint is c5:d3:aa:6e:09:b2:c7:6d:41:dd:ea:6c:4c:22:72:80.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.23.7' (RSA) to the list of known hosts.
[email protected]'s password:
# ls /
bin boot dev etc home lib
lib64 linuxrc lost+found media mnt opt proc
root run sbin sys tmp usr var
# date
Mon Jul 6 13:48:23 UTC 2015
Due to the previous failures, the test failed anyway.
I will have a closer look at the changes and try to get it to work - will
probably be part of our next Sprint.
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.
---
