Re: test day reminder
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/02/2014 09:40 AM, Daan Hoogland wrote: > H all, > > The test day has been a moderate success, I would say. I heard > apologies of people not participating apart from these reactions so > I think we should repeat this effort. Of course we are working hard > on more forms of continuous integration but these won't suffice > before David has 4.5 out the door so I would move we have one of > these every other week. > > Is this to often/sparse? > I'd love to continue doing this, but I also have to fix a Jenkins slave ;) Anyway, on the positive side: I also tested the KVM Agent (4.5/master) against a 4.4.1 Management Server and that is working for me just fine. > regards, Daan > > On Tue, Sep 30, 2014 at 9:26 AM, Daan Hoogland > wrote: > >> H all, >> >> As you might remember, we agreed on a test day for the master >> branch on Wednesday the 1st October, during our last meeting in >> Schihol-Rijk with some folks. Please feel invited to test master >> so that we can report to our RM for 4.5 for the current state and >> he can have a short and quick journey to releasing. >> >> optimistically yours, -- (almost former RM) Daan >> > > > -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJULR+eAAoJEAGbWC3bPspCZycP+weF81AYfHr98575ESKg+mKZ NkCrhlIUbQ/JqjaIpqqKrA3KEfDGt35UFr17Qi2+eu0rKs+roYmAhGxmzlSQJUE6 +tb6a40fY/drwit0+NQxvKiw327vGwrUvDYhTmMEz+JUfETbySfE+w78BMU137o9 oJz3YXSrpC2QWBOpMRCLhwpA6cGsYnBgMwZ8sxhjm8vuz9NCbsj+6D9Fyyqlf8Bh J6+3soCw2usz2rNJJk3G+IEFfUKAN7bwcc10vJDpXQ/QK7ds5BjvM06c+niNp1/s SXn0WXx1orEeFSzDK8qMJSRHQDuf2PXjE67i9zoczADunwbbfVcxl8v+U7Up21vz pEUblYJdI5yFrqaLed+8h2BqgJVCUbJy9L2rtrxat0egxdU2Pd9BQ12acsvoSpaP jzuIKEtGRaG+lCrKjlw/QWUQPmp1lohDroZIaqTkRvy49cj4cZf1FSJOxScov2hp BtrDtAAyjuAc4dFkRfddjhJ3SmddP9fDsUadTjY951IPzyJlwdRmdSRccix8ePXV hMpsVhy0Ysc8OH25WdbsLiIMiC7wCNBb+ctKYpvAv/tuyb5vk/PZBqoU5/wSAl23 QOuER3yxmr54bwfWFyq+sEqzUh63HW6/En5I9RA9UwC7H+xj2PA9k4U8w2EgZwFM 5OG+5ZVnlokuyyPmVdff =jFyI -END PGP SIGNATURE-
Re: test day reminder
H all, The test day has been a moderate success, I would say. I heard apologies of people not participating apart from these reactions so I think we should repeat this effort. Of course we are working hard on more forms of continuous integration but these won't suffice before David has 4.5 out the door so I would move we have one of these every other week. Is this to often/sparse? regards, Daan On Tue, Sep 30, 2014 at 9:26 AM, Daan Hoogland wrote: > H all, > > As you might remember, we agreed on a test day for the master branch on > Wednesday the 1st October, during our last meeting in Schihol-Rijk with > some folks. Please feel invited to test master so that we can report to our > RM for 4.5 for the current state and he can have a short and quick journey > to releasing. > > optimistically yours, > -- > (almost former RM) > Daan > -- Daan
Re: test day reminder
On 09/30/2014 09:26 AM, Daan Hoogland wrote: H all, As you might remember, we agreed on a test day for the master branch on Wednesday the 1st October, during our last meeting in Schihol-Rijk with some folks. Please feel invited to test master so that we can report to our RM for 4.5 for the current state and he can have a short and quick journey to releasing. optimistically yours, Stod up master in an environment where 4.4.1 and prior works. Environment is updated OEL65 for management head and hypervisors. Last commit in master build is; 70efe1507c3bc1cf6c3a9477bae4f31afc35375f The management head does not start, aborts early with; 2014-10-02 08:31:38,748 DEBUG [c.c.u.c.DBEncryptionUtil] (main:null) Error while decrypting: GPU as last entry in management log. Looks connected to; https://issues.apache.org/jira/browse/CLOUDSTACK-7242 /Ove -- Ove Everlid System Administrator / Architect / SDN- & Automation- & Linux-hacker Mobile: +46706668199 (dedicated work mobile) Country: Sweden, timezone; Middle Europan Time (MET or GMT+1)
Re: test day reminder
Instance successfully booted with above noted workaround. Created a ingress security group rule to allow SSH access to the instance. The rule applied as expected and ssh access was allowed. Created an egress security group rule to allow HTTP access out from the instance. The rule applied as expected all traffic out of the VM was blocked excluding http. Created a new volume, successfully attached it to the booted instance. Added a new ISO. ISO was successfully downloaded and installed. Was successfully able to download the ISO from secondary storage via the UI. I was unable to delete the ISO using the UI. (No button present) I created a new project, the UI was inconsistent http://ianduffy.ie/cloudstack/testing45/project-ui.png I noticed the baremetal-system-account as documented over here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Baremetal+Advanced+Networking+Support It felt confusing/unclear. It should be hidden like the system account in my view. Clicking add guest network and then pressing cancel resulted in an api error: http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2002.12.11.png Successfully created a new account and created new instances with this account. I was able to submit an invalid email for this e.g. not @. Successfully created a subdomain, UI didn't display it until the parent domain was collapsed and expanded. Creating enough nested subdomains allowed the tree to go off the screen. no scroll bar was provided. http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2002.16.48.png If I: 1) Create a subdomain of root labelled test 2) Create a subdomain of the subdomain created in step one, again labelling it test e.g. test/test 3) I rename test subdomain directly under root to rubbishdata 4) I attempt to rename rubbishdata back to test I get a message saying: "specified domain id with name 'test' already exists in the system" On 2 October 2014 01:55, Ian Duffy wrote: > Appear to be able to work around the virtual router issue by modifying the > version field in the domain_router table. It will read Cloudstack Release > Mon Sep 29 23:17:27 UTC 2014 changing to Cloudstack Release 4.5 Mon Sep 29 > 23:17:27 UTC 2014 allowed me to boot an instance (note the 4.5 before Mon). > > will continue testing > > On 2 October 2014 01:51, Ian Duffy wrote: > >> Hi All, >> >> Using the following environment: >> >> - XenServer 6.2 >> - The RPM build that was created on October 1st 2015 4:51am >> http://jenkins.buildacloud.org/job/package-rhel63-master/3361/ >> - The system vm that was build on September 29th 2015 7:07am >> http://jenkins.buildacloud.org/job/build-systemvm64-master/425/ >> >> I brought up a basic zone using marvin to do all the configuration. If >> anybody wants re-create the exact same environment there is code over at >> https://github.com/imduffy15/cookbook_cloudstack_wrapper adjust >> chef_configuration.json as necessary to change the repo and systemvm and >> then do a vagrant up (if your on windows expect issues). >> >> Configuration was successful, my systemvms were successfully created: >> http://ianduffy.ie/cloudstack/testing45/version%2bsystemvms-up.png >> >> There was an issue with a table header on the system vms page: >> http://ianduffy.ie/cloudstack/testing45/strange-labeling-on-ui.png >> >> Another labelling issue was noted on the alerts section on the initial >> screen: >> http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2001.40.18.png >> >> The cluster configuration table under infrastructure had a white block as >> its header, on hovering text would appear: >> http://ianduffy.ie/cloudstack/testing45/cluster-table-renders-oddly.png >> >> The system vms complained about a file not being found: >> http://ianduffy.ie/cloudstack/testing45/system-vm-reports-script-not-found.png >> >> Rapidly clicking the search button resulted in duplicate entries: >> http://ianduffy.ie/cloudstack/testing45/clicking-the-search-button-multiple-times-results-in-duplicates.png >> >> Add instance UI had a random scroll bar for no reason: >> http://ianduffy.ie/cloudstack/testing45/add-instance-scroll-bar-for-no-reason.png >> >> I attempted to create an instance, it failed. I believe this is due to an >> issue with the version field populated for the virtual router logs >> available at https://gist.github.com/imduffy15/5879718ce38f8a67bebd >> After this error was created I got random prompt boxes on the UI: >> http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2001.40.18.png >> >> I stopped my testing at this stage. >> >> Thanks, >> >> Ian >> >> On 1 October 2014 17:26, Daan Hoogland wrote: >> >>> I have been looking at using my collegues integration work for the master >>> branch. So far the packaging part is holding my back as it uses >>> 'SNAPSHOT' >>> in the build and does not allow for patch levels (in package.sh) I am >>> looking at a solution. >>> >>> what I am thinking of is making rpms
Re: test day reminder
Appear to be able to work around the virtual router issue by modifying the version field in the domain_router table. It will read Cloudstack Release Mon Sep 29 23:17:27 UTC 2014 changing to Cloudstack Release 4.5 Mon Sep 29 23:17:27 UTC 2014 allowed me to boot an instance (note the 4.5 before Mon). will continue testing On 2 October 2014 01:51, Ian Duffy wrote: > Hi All, > > Using the following environment: > > - XenServer 6.2 > - The RPM build that was created on October 1st 2015 4:51am > http://jenkins.buildacloud.org/job/package-rhel63-master/3361/ > - The system vm that was build on September 29th 2015 7:07am > http://jenkins.buildacloud.org/job/build-systemvm64-master/425/ > > I brought up a basic zone using marvin to do all the configuration. If > anybody wants re-create the exact same environment there is code over at > https://github.com/imduffy15/cookbook_cloudstack_wrapper adjust > chef_configuration.json as necessary to change the repo and systemvm and > then do a vagrant up (if your on windows expect issues). > > Configuration was successful, my systemvms were successfully created: > http://ianduffy.ie/cloudstack/testing45/version%2bsystemvms-up.png > > There was an issue with a table header on the system vms page: > http://ianduffy.ie/cloudstack/testing45/strange-labeling-on-ui.png > > Another labelling issue was noted on the alerts section on the initial > screen: > http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2001.40.18.png > > The cluster configuration table under infrastructure had a white block as > its header, on hovering text would appear: > http://ianduffy.ie/cloudstack/testing45/cluster-table-renders-oddly.png > > The system vms complained about a file not being found: > http://ianduffy.ie/cloudstack/testing45/system-vm-reports-script-not-found.png > > Rapidly clicking the search button resulted in duplicate entries: > http://ianduffy.ie/cloudstack/testing45/clicking-the-search-button-multiple-times-results-in-duplicates.png > > Add instance UI had a random scroll bar for no reason: > http://ianduffy.ie/cloudstack/testing45/add-instance-scroll-bar-for-no-reason.png > > I attempted to create an instance, it failed. I believe this is due to an > issue with the version field populated for the virtual router logs > available at https://gist.github.com/imduffy15/5879718ce38f8a67bebd > After this error was created I got random prompt boxes on the UI: > http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2001.40.18.png > > I stopped my testing at this stage. > > Thanks, > > Ian > > On 1 October 2014 17:26, Daan Hoogland wrote: > >> I have been looking at using my collegues integration work for the master >> branch. So far the packaging part is holding my back as it uses 'SNAPSHOT' >> in the build and does not allow for patch levels (in package.sh) I am >> looking at a solution. >> >> what I am thinking of is making rpms like >> >> >> cloudstack.el6_64.rpm >> >> this seems quite verbose but it gives us space to do continuous >> integration >> on the artifact. I am sure a scheme like this can be deviced for .deb >> packages as well. >> >> thoughts? >> >> The actual testing, for as little far as I got to do, did not yield issues >> yet. >> >> Daan >> >> On Wed, Oct 1, 2014 at 5:28 PM, Marcus wrote: >> >> > I'd be curious to know if it works by re-adding the host. I remember >> > running into situations like this in the past, where the mgmt server was >> > either not fully up or rejecting agents for some reason. >> > >> > On Wed, Oct 1, 2014 at 7:01 AM, Wido den Hollander >> wrote: >> > >> > > >> > > >> > > On 09/30/2014 09:26 AM, Daan Hoogland wrote: >> > > > H all, >> > > > >> > > > As you might remember, we agreed on a test day for the master >> branch on >> > > > Wednesday the 1st October, during our last meeting in Schihol-Rijk >> with >> > > > some folks. Please feel invited to test master so that we can >> report to >> > > our >> > > > RM for 4.5 for the current state and he can have a short and quick >> > > journey >> > > > to releasing. >> > > > >> > > >> > > I didn't forget! Just tested by upgrading from 4.4.1 (RC) to 4.5.0 and >> > > that worked, but my KVM agent couldn't connect anymore afterwards: >> > > >> > > 2014-10-01 14:59:08,789 INFO [utils.nio.NioClient] >> > > (Agent-Selector:null) Connecting to cloudstack.:8250 >> > > 2014-10-01 14:59:08,809 ERROR [utils.nio.NioConnection] >> > > (Agent-Selector:null) Unable to initialize the threads. >> > > java.io.IOException: Connection closed with -1 on reading size. >> > > at com.cloud.utils.nio.Link.doHandshake(Link.java:509) >> > > at com.cloud.utils.nio.NioClient.init(NioClient.java:78) >> > > at >> com.cloud.utils.nio.NioConnection.run(NioConnection.java:111) >> > > at java.lang.Thread.run(Thread.java:744) >> > > >> > > Any ideas? When I try to telnet to 8250 the connection is closed >> > > immediately by the mgmt server. Nothing in
Re: test day reminder
Hi All, Using the following environment: - XenServer 6.2 - The RPM build that was created on October 1st 2015 4:51am http://jenkins.buildacloud.org/job/package-rhel63-master/3361/ - The system vm that was build on September 29th 2015 7:07am http://jenkins.buildacloud.org/job/build-systemvm64-master/425/ I brought up a basic zone using marvin to do all the configuration. If anybody wants re-create the exact same environment there is code over at https://github.com/imduffy15/cookbook_cloudstack_wrapper adjust chef_configuration.json as necessary to change the repo and systemvm and then do a vagrant up (if your on windows expect issues). Configuration was successful, my systemvms were successfully created: http://ianduffy.ie/cloudstack/testing45/version%2bsystemvms-up.png There was an issue with a table header on the system vms page: http://ianduffy.ie/cloudstack/testing45/strange-labeling-on-ui.png Another labelling issue was noted on the alerts section on the initial screen: http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2001.40.18.png The cluster configuration table under infrastructure had a white block as its header, on hovering text would appear: http://ianduffy.ie/cloudstack/testing45/cluster-table-renders-oddly.png The system vms complained about a file not being found: http://ianduffy.ie/cloudstack/testing45/system-vm-reports-script-not-found.png Rapidly clicking the search button resulted in duplicate entries: http://ianduffy.ie/cloudstack/testing45/clicking-the-search-button-multiple-times-results-in-duplicates.png Add instance UI had a random scroll bar for no reason: http://ianduffy.ie/cloudstack/testing45/add-instance-scroll-bar-for-no-reason.png I attempted to create an instance, it failed. I believe this is due to an issue with the version field populated for the virtual router logs available at https://gist.github.com/imduffy15/5879718ce38f8a67bebd After this error was created I got random prompt boxes on the UI: http://ianduffy.ie/cloudstack/testing45/Screen%20Shot%202014-10-02%20at%2001.40.18.png I stopped my testing at this stage. Thanks, Ian On 1 October 2014 17:26, Daan Hoogland wrote: > I have been looking at using my collegues integration work for the master > branch. So far the packaging part is holding my back as it uses 'SNAPSHOT' > in the build and does not allow for patch levels (in package.sh) I am > looking at a solution. > > what I am thinking of is making rpms like > > > cloudstack.el6_64.rpm > > this seems quite verbose but it gives us space to do continuous integration > on the artifact. I am sure a scheme like this can be deviced for .deb > packages as well. > > thoughts? > > The actual testing, for as little far as I got to do, did not yield issues > yet. > > Daan > > On Wed, Oct 1, 2014 at 5:28 PM, Marcus wrote: > > > I'd be curious to know if it works by re-adding the host. I remember > > running into situations like this in the past, where the mgmt server was > > either not fully up or rejecting agents for some reason. > > > > On Wed, Oct 1, 2014 at 7:01 AM, Wido den Hollander > wrote: > > > > > > > > > > > On 09/30/2014 09:26 AM, Daan Hoogland wrote: > > > > H all, > > > > > > > > As you might remember, we agreed on a test day for the master branch > on > > > > Wednesday the 1st October, during our last meeting in Schihol-Rijk > with > > > > some folks. Please feel invited to test master so that we can report > to > > > our > > > > RM for 4.5 for the current state and he can have a short and quick > > > journey > > > > to releasing. > > > > > > > > > > I didn't forget! Just tested by upgrading from 4.4.1 (RC) to 4.5.0 and > > > that worked, but my KVM agent couldn't connect anymore afterwards: > > > > > > 2014-10-01 14:59:08,789 INFO [utils.nio.NioClient] > > > (Agent-Selector:null) Connecting to cloudstack.:8250 > > > 2014-10-01 14:59:08,809 ERROR [utils.nio.NioConnection] > > > (Agent-Selector:null) Unable to initialize the threads. > > > java.io.IOException: Connection closed with -1 on reading size. > > > at com.cloud.utils.nio.Link.doHandshake(Link.java:509) > > > at com.cloud.utils.nio.NioClient.init(NioClient.java:78) > > > at > com.cloud.utils.nio.NioConnection.run(NioConnection.java:111) > > > at java.lang.Thread.run(Thread.java:744) > > > > > > Any ideas? When I try to telnet to 8250 the connection is closed > > > immediately by the mgmt server. Nothing in the logs. > > > > > > So this is currently preventing me from testing the KVM agents. > > > > > > Wido > > > > > > > > > > optimistically yours, > > > > > > > > > > > > > -- > Daan >
Re: test day reminder
I have been looking at using my collegues integration work for the master branch. So far the packaging part is holding my back as it uses 'SNAPSHOT' in the build and does not allow for patch levels (in package.sh) I am looking at a solution. what I am thinking of is making rpms like cloudstack.el6_64.rpm this seems quite verbose but it gives us space to do continuous integration on the artifact. I am sure a scheme like this can be deviced for .deb packages as well. thoughts? The actual testing, for as little far as I got to do, did not yield issues yet. Daan On Wed, Oct 1, 2014 at 5:28 PM, Marcus wrote: > I'd be curious to know if it works by re-adding the host. I remember > running into situations like this in the past, where the mgmt server was > either not fully up or rejecting agents for some reason. > > On Wed, Oct 1, 2014 at 7:01 AM, Wido den Hollander wrote: > > > > > > > On 09/30/2014 09:26 AM, Daan Hoogland wrote: > > > H all, > > > > > > As you might remember, we agreed on a test day for the master branch on > > > Wednesday the 1st October, during our last meeting in Schihol-Rijk with > > > some folks. Please feel invited to test master so that we can report to > > our > > > RM for 4.5 for the current state and he can have a short and quick > > journey > > > to releasing. > > > > > > > I didn't forget! Just tested by upgrading from 4.4.1 (RC) to 4.5.0 and > > that worked, but my KVM agent couldn't connect anymore afterwards: > > > > 2014-10-01 14:59:08,789 INFO [utils.nio.NioClient] > > (Agent-Selector:null) Connecting to cloudstack.:8250 > > 2014-10-01 14:59:08,809 ERROR [utils.nio.NioConnection] > > (Agent-Selector:null) Unable to initialize the threads. > > java.io.IOException: Connection closed with -1 on reading size. > > at com.cloud.utils.nio.Link.doHandshake(Link.java:509) > > at com.cloud.utils.nio.NioClient.init(NioClient.java:78) > > at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111) > > at java.lang.Thread.run(Thread.java:744) > > > > Any ideas? When I try to telnet to 8250 the connection is closed > > immediately by the mgmt server. Nothing in the logs. > > > > So this is currently preventing me from testing the KVM agents. > > > > Wido > > > > > > > optimistically yours, > > > > > > -- Daan
Re: test day reminder
I'd be curious to know if it works by re-adding the host. I remember running into situations like this in the past, where the mgmt server was either not fully up or rejecting agents for some reason. On Wed, Oct 1, 2014 at 7:01 AM, Wido den Hollander wrote: > > > On 09/30/2014 09:26 AM, Daan Hoogland wrote: > > H all, > > > > As you might remember, we agreed on a test day for the master branch on > > Wednesday the 1st October, during our last meeting in Schihol-Rijk with > > some folks. Please feel invited to test master so that we can report to > our > > RM for 4.5 for the current state and he can have a short and quick > journey > > to releasing. > > > > I didn't forget! Just tested by upgrading from 4.4.1 (RC) to 4.5.0 and > that worked, but my KVM agent couldn't connect anymore afterwards: > > 2014-10-01 14:59:08,789 INFO [utils.nio.NioClient] > (Agent-Selector:null) Connecting to cloudstack.:8250 > 2014-10-01 14:59:08,809 ERROR [utils.nio.NioConnection] > (Agent-Selector:null) Unable to initialize the threads. > java.io.IOException: Connection closed with -1 on reading size. > at com.cloud.utils.nio.Link.doHandshake(Link.java:509) > at com.cloud.utils.nio.NioClient.init(NioClient.java:78) > at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111) > at java.lang.Thread.run(Thread.java:744) > > Any ideas? When I try to telnet to 8250 the connection is closed > immediately by the mgmt server. Nothing in the logs. > > So this is currently preventing me from testing the KVM agents. > > Wido > > > > optimistically yours, > > >
Re: test day reminder
On 09/30/2014 09:26 AM, Daan Hoogland wrote: > H all, > > As you might remember, we agreed on a test day for the master branch on > Wednesday the 1st October, during our last meeting in Schihol-Rijk with > some folks. Please feel invited to test master so that we can report to our > RM for 4.5 for the current state and he can have a short and quick journey > to releasing. > I didn't forget! Just tested by upgrading from 4.4.1 (RC) to 4.5.0 and that worked, but my KVM agent couldn't connect anymore afterwards: 2014-10-01 14:59:08,789 INFO [utils.nio.NioClient] (Agent-Selector:null) Connecting to cloudstack.:8250 2014-10-01 14:59:08,809 ERROR [utils.nio.NioConnection] (Agent-Selector:null) Unable to initialize the threads. java.io.IOException: Connection closed with -1 on reading size. at com.cloud.utils.nio.Link.doHandshake(Link.java:509) at com.cloud.utils.nio.NioClient.init(NioClient.java:78) at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111) at java.lang.Thread.run(Thread.java:744) Any ideas? When I try to telnet to 8250 the connection is closed immediately by the mgmt server. Nothing in the logs. So this is currently preventing me from testing the KVM agents. Wido > optimistically yours, >
test day reminder
H all, As you might remember, we agreed on a test day for the master branch on Wednesday the 1st October, during our last meeting in Schihol-Rijk with some folks. Please feel invited to test master so that we can report to our RM for 4.5 for the current state and he can have a short and quick journey to releasing. optimistically yours, -- (almost former RM) Daan
