cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wilder Rodrigues <WRodrig...@schubergphilis.com>
Subject RE: [TRAVIS] - failing for pull request #18
Date Fri, 12 Sep 2014 02:02:53 GMT
Hi Ian,

I closed the old PR and created a new one, based on a new branch containing all the changes
(including the commit from Frank Zhang for the CLOUDSTACK-6278 Baremetal Advanced Networking
support with commit id e06fa18ed2ee2ee6a417e089cf5ac6bde11d0079).

Except for the vm life cycle tests (which is failing for everybody), all the tests are green.
You can see the results here: https://travis-ci.org/apache/cloudstack/builds/35069594

The pull request can be found here: https://github.com/apache/cloudstack/pull/19

If anyone else wants to do a review, please do not hesitate.
Everything was tested using the Simulator and my environment:

Cheers,
Wilder

From: Wilder Rodrigues
Sent: donderdag 11 september 2014 11:25
To: 'Ian Duffy'
Cc: CloudStack Dev; int-toolkit; int-cloud
Subject: RE: [TRAVIS] - failing for pull request #18

Hi Ian,

One job is fixed. What happened? I would say one should not stay awake until 2AM doing cloudstack.
;) There were things I did not push, sorry by that.

Concerning the other 2 jobs, I just got the simulator environment running and already found
the reason why they are failing. In the refactor of the deployRouter() method, the code related
to the support hypervisor has changed in term of behaviour. The refactor should have been
done in 2 steps: first restructure the code; then make it better. Along our hard 10 weeks
of work those 2 steps were mix[messed]-up a bit.

Sorry for bothering you with that, I will fix it.

Cheers,
Wilder


From: Wilder Rodrigues
Sent: Wednesday, September 10, 2014 12:44 PM
To: 'Ian Duffy'
Cc: CloudStack Dev; int-toolkit; int-cloud
Subject: RE: [TRAVIS] - failing for pull request #18

Okay…

I’m cloning it in a different place, just to make sure I follow the same steps as you.

Once I get it tested… will share my thoughts again. ☺

Thanks again for the support.

Cheers,
Wilder

From: Ian Duffy [mailto:ian@ianduffy.ie]
Sent: woensdag 10 september 2014 12:06
To: Wilder Rodrigues
Cc: CloudStack Dev; int-toolkit; int-cloud
Subject: Re: [TRAVIS] - failing for pull request #18

> You clone the “test-cmd-rebase” branch,  right?

Yes positive:
$ git status
On branch test-cmd-rebase
Your branch is up-to-date with 'origin/test-cmd-rebase'.

Try your work against the simulator.

On 10 September 2014 10:44, Wilder Rodrigues <WRodrigues@schubergphilis.com<mailto:WRodrigues@schubergphilis.com>>
wrote:
Thanks Ian,

I will follow the same steps, because it’s really weird.

I’m running with mvn –pl :cloud-ui jetty:run, but no simulator.

Accounts page looks fine, I even executed the accounts related tests. Advance zone was also
deployed successfully.

The data form my accounts page:

admin  Admin  ROOT  enabled
baremetal-system-account     User     ROOT  enabled
test-a-TestVpcRemoteAccessVpn-4SYLK3   User     ROOT  enabled
test-a-TestVpcRemoteAccessVpn-5WDDUJ User     ROOT  enabled

You clone the “test-cmd-rebase” branch,  right?

I was busy running all the tests I have again, the result was successful and I also kept tracking
the “running.txt” Marvin log file during execution.

The only difference IPs I have in the advanced.cfg, because I do not use the ranges that are
there.



Test Create Account and user for that account ... === TestName: test_01_create_account | Status
: SUCCESS ===
ok
Test Sub domain allowed to launch VM  when a Domain level zone is created ... === TestName:
test_01_add_vm_to_subdomain | Status : SUCCESS ===
ok
Test delete domain without force option ... === TestName: test_DeleteDomain | Status : SUCCESS
===
ok
Test delete domain with force option ... === TestName: test_forceDeleteDomain | Status : SUCCESS
===
ok
Test update admin details ... === TestName: test_updateAdminDetails | Status : SUCCESS ===
ok
Test update domain admin details ... === TestName: test_updateDomainAdminDetails | Status
: SUCCESS ===
ok
Test user update API ... === TestName: test_updateUserDetails | Status : SUCCESS ===
ok
Test login API with domain ... === TestName: test_LoginApiDomain | Status : SUCCESS ===
ok
Test if Login API does not return UUID's ... === TestName: test_LoginApiUuidResponse | Status
: SUCCESS ===
ok

----------------------------------------------------------------------
Ran 9 tests in 832.310s

OK

test_privategw_acl (ekholabs.acs.tests.test_privategw_acl.TestPrivateGwACL) ... === TestName:
test_privategw_acl | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 1 test in 100.582s

OK

Test reset virtual machine on reboot ... === TestName: test_01_reset_vm_on_reboot | Status
: SUCCESS ===
ok

----------------------------------------------------------------------
Ran 1 test in 183.507s

OK

Test router internal basic zone ... SKIP: Marvin configuration has no host credentials to
check router services
Test router internal advanced zone ... SKIP: Marvin configuration has no host credentials
to check router services
Test restart network ... === TestName: test_03_restart_network_cleanup | Status : SUCCESS
===
ok
Test restart network without cleanup ... SKIP: Marvin configuration has no host credentials
to check router services
Test router basic setup ... === TestName: test_05_router_basic | Status : SUCCESS ===
ok
Test router advanced setup ... === TestName: test_06_router_advanced | Status : SUCCESS ===
ok
Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS ===
ok
Test start router ... === TestName: test_08_start_router | Status : SUCCESS ===
ok
Test reboot router ... === TestName: test_09_reboot_router | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 9 tests in 354.245s

OK (SKIP=3)

Test to create service offering ... === TestName: test_01_create_service_offering | Status
: SUCCESS ===
ok
Test to update existing service offering ... === TestName: test_02_edit_service_offering |
Status : SUCCESS ===
ok
Test to delete service offering ... === TestName: test_03_delete_service_offering | Status
: SUCCESS ===
ok

----------------------------------------------------------------------
Ran 3 tests in 158.207s

OK

Test start/stop of router after addition of one guest network ... === TestName: test_01_start_stop_router_after_addition_of_one_guest_network
| Status : SUCCESS ===
ok
Test reboot of router after addition of one guest network ... === TestName: test_02_reboot_router_after_addition_of_one_guest_network
| Status : SUCCESS ===
ok
Test migrate of router after addition of one guest network ... SKIP: No host available for
migration. Test requires atleast 2 hosts
Test to change service offering of router after addition of one guest network ... === TestName:
test_04_chg_srv_off_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test destroy of router after addition of one guest network ... === TestName: test_05_destroy_router_after_addition_of_one_guest_network
| Status : SUCCESS ===
ok
Test to stop and start router after creation of VPC ... === TestName: test_01_stop_start_router_after_creating_vpc
| Status : SUCCESS ===
ok
Test to reboot the router after creating a VPC ... === TestName: test_02_reboot_router_after_creating_vpc
| Status : SUCCESS ===
ok
Test migration of router to another host after creating VPC ... SKIP: No host available for
migration. Test requires atleast 2 hosts
Tests to change service offering of the Router after ... === TestName: test_04_change_service_offerring_vpc
| Status : SUCCESS ===
ok
Test to destroy the router after creating a VPC ... === TestName: test_05_destroy_router_after_creating_vpc
| Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 10 tests in 626.704s

OK (SKIP=2)

Test VPN in VPC ... === TestName: test_vpc_remote_access_vpn | Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 2 tests in 445.923s

OK

From: Ian Duffy [mailto:ian@ianduffy.ie<mailto:ian@ianduffy.ie>]
Sent: woensdag 10 september 2014 11:35
To: Wilder Rodrigues
Cc: CloudStack Dev; int-toolkit; int-cloud

Subject: Re: [TRAVIS] - failing for pull request #18

HI Wilder,

I cloned your branch, compiled it and ran it in simulator mode.

mvn -pl :cloud-client-ui jetty:run -D simulator

I browsed about the UI for a bit, I seen an exception been thrown when I went to the accounts
page, the page would not successfully load.

I went ahead and deployed the advanced.cfg file with marvin:

python -m marvin.deployDataCenter setup/dev/advanced.cfg

I executed the first set of tests travis does and seen some failures:
=== TestName: test_DeployVmAntiAffinityGroup | Status : EXCEPTION ===
=== TestName: test_deployvm_firstfit | Status : EXCEPTION ===
=== TestName: test_deployvm_userconcentrated | Status : EXCEPTION ===
=== TestName: test_deployvm_userdispersing | Status : EXCEPTION ===
=== TestName: test_delete_account | Status : EXCEPTION ===

If you run them on your own machine you'll see the JSON response from cloudstack that causes
the exceptions within: /tmp//MarvinLogs and you can begin to debug.
From what I can tell the failures are genuine and the changes do break things.

On 10 September 2014 08:15, Wilder Rodrigues <WRodrigues@schubergphilis.com<mailto:WRodrigues@schubergphilis.com>>
wrote:
Hi Ian,

Super thanks!

I’m executing the tests again to see if there is any hiccup with the environment, although
I did that twice yesterday.

In case you find some strangeness in the pull request, please, do not hesitate to contact
me.

Cheers,
Wilder

From: Ian Duffy [mailto:ian@ianduffy.ie<mailto:ian@ianduffy.ie>]
Sent: woensdag 10 september 2014 9:05
To: CloudStack Dev
Cc: int-toolkit; int-cloud
Subject: Re: [TRAVIS] - failing for pull request #18

Hi Wilder,

The travis stuff is experimental.

I will take a look at this for you and see if its anything to be concerned about.

Thanks,

Ian

On 10 September 2014 07:00, Wilder Rodrigues <WRodrigues@schubergphilis.com<mailto:WRodrigues@schubergphilis.com>>
wrote:
Hi guys,

Last night I sent a pull request, after rebasing and fixing some conflicts in VirtualNetworkApplianceManagerImpl
class. Unfortunately, the 3 builds are not okay on Travis. For the first job, I got the following:


Still running (30 of 30): ./tools/travis/before_script.sh

Timeout (30 minutes) reached. Terminating "./tools/travis/before_script.sh"

The command "travis_wait 30 ./tools/travis/before_script.sh" failed and exited with 1 during
.

The second job is a bit stranger than that because all the tests that I actually executed
on our environment, and passed, just failed on that job:

test_privategw_acl
test_01_reset_vm_on_reboot
test_routers

Concerning the 3rd job, same story: tests that have passed are now failing:

test_service_offerings
test_vpc_vpn

Stil on the 3rd job I got problems with test_volumes and test_templates. The test_vm_life_cycle
is still failing for everybody.

My test environment is the following:


·         XenServer (host) running in our VMWare zone (which is managed by CloudStack).

o   MySQL

o   Secondary Storage

o   Local Primary Storage

·         Management Server

o   Debian 7 VM (inside Virtual Box)

o   Pre/Post routing to allow my Debian to get connected to the host via its public IPs

o   SSH reverse tunnel to allow communication between the host and the management server (for
the Agent)

·         Tests

o   I create a separate project with a bunch of ACS Marving tests

§  Changed storage type in my tests from "shared" to "local"

§  Changed DataCenter configuration

·         IP ranges

§  Changed VPCs CIDRs and Network Gatways

·         To cope with my IP ranges

·         All the tests below are passing:

o   test_01_create_account

o   test_01_add_vm_to_subdomain

o   test_DeleteDomain

o   test_forceDeleteDomain

o   test_updateAdminDetails

o   test_updateDomainAdminDetails

o   test_updateUserDetails

o   test_LoginApiDomain

o   test_LoginApiUuidResponse

o   test_privategw_acl

o   test_01_reset_vm_on_reboot

o   test_03_restart_network_cleanup

o   test_05_router_basic

o   test_06_router_advanced

o   test_07_stop_router

o   test_08_start_router

o   test_09_reboot_router

o   test_01_create_service_offering

o   test_02_edit_service_offering

o   test_03_delete_service_offering

o   test_01_start_stop_router_after_addition_of_one_guest_network

o   test_02_reboot_router_after_addition_of_one_guest_network

o   test_04_chg_srv_off_router_after_addition_of_one_guest_network

o   test_05_destroy_router_after_addition_of_one_guest_network

o   test_01_stop_start_router_after_creating_vpc

o   test_02_reboot_router_after_creating_vpc

o   test_04_change_service_offerring_vpc

o   test_05_destroy_router_after_creating_vpc

o   test_vpc_remote_access_vpn

o   test_vpc_site2site_vpn

Unfortunately, Travis does not give much help about what is going on, it only says "exception".
Is there anyone out there that could give some help?

The pull request is: VPC and Virtual Network Managers refactor. Part of the VPC Redundant
Router work #18

Thanks in advance.

Cheers,
Wilder



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message