From fabiand at redhat.com Fri Jun 8 15:10:02 2012 From: fabiand at redhat.com (Fabian Deutsch) Date: Fri, 08 Jun 2012 17:10:02 +0200 Subject: [node-devel] Fedora 17 status update Message-ID: <1339168202.2510.19.camel@fdeutsch-laptop.local> Hey, during the last couple of days I tried to get a working Fedora 17 based Node build running, which was blocked by some bugs summarized here [1]. The current status is that - after some segfaults, selinux and dracut problems - Node can be installed and we can login again. Currently the usage and further testing is semi-blocked by a problem with the TUI because you currently can't configure any NIC. The interested reader can find most of the for 2.4.0 here [2]. Feature freeze was yesterday, that's fine, but there is still a bit to do to get a stable F17 based Node for the overall beta. I'm optimistic that we can nail down most the bugs during the next days. And the plan is that the Fedora 17 based builds will be the first ones with some basic automated continuous testing [3]. Greetings for now fabian -- [1] https://bugzilla.redhat.com/show_bug.cgi?id=824420 [2] http://gerrit.ovirt.org/#/q/status:open+project:ovirt-node,n,z [3] http://ovirt.org/wiki/Node_Testing -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From fabiand at redhat.com Mon Jun 11 08:39:15 2012 From: fabiand at redhat.com (Fabian Deutsch) Date: Mon, 11 Jun 2012 10:39:15 +0200 Subject: [node-devel] Continous Testing of Node Message-ID: <1339403955.2289.21.camel@fdeutsch-laptop.local> Hey, I've already talked about integrating some testing mechanism in our current build chain [1, 2]. I looked at two existing solutions autotest (used by e.g. KVM folks) [3] and beaker (used by e.g. Fedora) [4]. Both provide a framework to run tests on some hardware but didn't match our needs that well, thus easy integration into jenkins and able to be nicely integrated with node and be able to be run an real hardware and VMs (with varying configurations). Finally I invested some time into a peace of glue (igor), which ties our current tools together (cobbler, libvirt and livecd-tools) to provide a lightweight service to do the automated testing and respecting all our constraints. igor can be found at [5], it's a small wsgi script awaiting orders via some RESTless like API. There is also an example script provided to illustrate how it can be triggered from jenkins. The patch [6] is needed to add the necessary service to a Node build. I plan to get the basic integration into our jenkins during the week, which will be able to do some basic installation tests for now. - fabian -- [1] http://lists.ovirt.org/pipermail/node-devel/2012-April/000204.html [2] http://lists.ovirt.org/pipermail/node-devel/2012-May/000221.html [3] http://autotest.github.com/ [4] https://fedorahosted.org/beaker/ [5] https://gitorious.org/ovirt/igord [6] http://gerrit.ovirt.org/#/c/4306/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From fabiand at redhat.com Mon Jun 11 09:08:21 2012 From: fabiand at redhat.com (Fabian Deutsch) Date: Mon, 11 Jun 2012 11:08:21 +0200 Subject: [node-devel] Continous Testing of Node In-Reply-To: <1339403955.2289.21.camel@fdeutsch-laptop.local> References: <1339403955.2289.21.camel@fdeutsch-laptop.local> Message-ID: <1339405701.2289.28.camel@fdeutsch-laptop.local> Am Montag, den 11.06.2012, 10:39 +0200 schrieb Fabian Deutsch: > igor can be found at [5], it's a small wsgi script awaiting orders via > some RESTless like API. There is also an example script provided to > illustrate how it can be triggered from jenkins. The patch [6] is needed > to add the necessary service to a Node build. Just a few more details on different parts: - VMs are currently created by virt-install (which is already quite flexible), this can be extended to take any domain definition so we can create arbitrary guests. - Testcases are intended to be python or bash scripts, but can actually be any kind of on-the-node-runnable blob. [1] is showing some examples. - Testcases are summarized in a Testset which are the distilled into a testsuite. And specified in files with a .suite and .set suffix. [1] gives some examples - Testsets (Testcases) can be reused in different Testsuites (Testsets). - The idea to do the TUI testing is to use uinput (via python-uninput) for input and /dev/vcs or whatever to check the results Testcases are welcome, and it's planned to have a separate repository for them. fabian -- [1] https://gitorious.org/ovirt/igord/trees/master/testcases -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From fabiand at redhat.com Tue Jun 12 09:12:56 2012 From: fabiand at redhat.com (Fabian Deutsch) Date: Tue, 12 Jun 2012 11:12:56 +0200 Subject: [node-devel] Automated testing client Message-ID: <1339492376.2252.19.camel@fdeutsch-laptop.local> Hey, up to now the testing client which needs to be part of Node builds resided as a patch for ovirt-node in gerrit. I've extracted that part which now forms it's own rpm [1] (ovirt-autotesting), this way it's better to control when it get's into a build. My question: And what point should/could we include this rpm? I suppose this would be a good case for a Node plugin. [2] Greetings fabian --- [1] https://gitorious.org/ovirt/ovirt-igor-client [2] http://ovirt.org/wiki/Node_plugins -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From mburns at redhat.com Tue Jun 12 09:28:49 2012 From: mburns at redhat.com (Mike Burns) Date: Tue, 12 Jun 2012 05:28:49 -0400 Subject: [node-devel] Automated testing client In-Reply-To: <1339492376.2252.19.camel@fdeutsch-laptop.local> References: <1339492376.2252.19.camel@fdeutsch-laptop.local> Message-ID: <1339493329.827.5.camel@beelzebub.mburnsfire.net> On Tue, 2012-06-12 at 11:12 +0200, Fabian Deutsch wrote: > Hey, > > up to now the testing client which needs to be part of Node builds > resided as a patch for ovirt-node in gerrit. > I've extracted that part which now forms it's own rpm [1] > (ovirt-autotesting), this way it's better to control when it get's into > a build. > > My question: And what point should/could we include this rpm? > I suppose this would be a good case for a Node plugin. [2] My thoughts exactly. Have a new job in jenkins after the iso build that runs the node-plugin script to add it in. Joey, Do we have patches yet that can do at least this part? Thanks Mike > > Greetings > fabian > > --- > [1] https://gitorious.org/ovirt/ovirt-igor-client > [2] http://ovirt.org/wiki/Node_plugins > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From mburns at redhat.com Tue Jun 12 09:37:38 2012 From: mburns at redhat.com (Mike Burns) Date: Tue, 12 Jun 2012 05:37:38 -0400 Subject: [node-devel] Automated testing client In-Reply-To: <1339493329.827.5.camel@beelzebub.mburnsfire.net> References: <1339492376.2252.19.camel@fdeutsch-laptop.local> <1339493329.827.5.camel@beelzebub.mburnsfire.net> Message-ID: <1339493858.827.8.camel@beelzebub.mburnsfire.net> On Tue, 2012-06-12 at 05:28 -0400, Mike Burns wrote: > On Tue, 2012-06-12 at 11:12 +0200, Fabian Deutsch wrote: > > Hey, > > > > up to now the testing client which needs to be part of Node builds > > resided as a patch for ovirt-node in gerrit. > > I've extracted that part which now forms it's own rpm [1] > > (ovirt-autotesting), this way it's better to control when it get's into > > a build. > > > > My question: And what point should/could we include this rpm? > > I suppose this would be a good case for a Node plugin. [2] > > My thoughts exactly. Have a new job in jenkins after the iso build that > runs the node-plugin script to add it in. > > Joey, Do we have patches yet that can do at least this part? Helps if I add the person I'm asking... > > Thanks > > Mike > > > > > Greetings > > fabian > > > > --- > > [1] https://gitorious.org/ovirt/ovirt-igor-client > > [2] http://ovirt.org/wiki/Node_plugins > > _______________________________________________ > > node-devel mailing list > > node-devel at ovirt.org > > http://lists.ovirt.org/mailman/listinfo/node-devel > > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From mburns at redhat.com Tue Jun 12 13:15:31 2012 From: mburns at redhat.com (Mike Burns) Date: Tue, 12 Jun 2012 09:15:31 -0400 Subject: [node-devel] oVirt Node Weekly Meeting Minutes -- 2012-06-12 Message-ID: <1339506931.827.22.camel@beelzebub.mburnsfire.net> Minutes: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-12-13.02.html Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-12-13.02.txt Log: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-12-13.02.log.html ============================== #ovirt: ovirt node weekly sync ============================== Meeting started by mburns at 13:02:32 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-12-13.02.log.html . Meeting summary --------------- * roll call and agenda (mburns, 13:02:40) * action item review (mburns, 13:03:59) * LINK: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-05-13.01.html (mburns, 13:04:08) * still lots of patches, but good job by fabiand getting things reviewed (mburns, 13:04:45) * mburns still catching up after linuxcon last week (mburns, 13:04:55) * ACTION: mburns jboggs fabiand get 2.4.0 out the door (mburns, 13:05:40) * ACTION: mburns jboggs review network manager feature page (mburns, 13:05:50) * ACTION: mburns to file bzs for stateless (mburns, 13:06:05) * ACTION: mburns to add 2.6.0 release and re-target bugs (mburns, 13:06:15) * jboggs acks network manager feature page (mburns, 13:06:28) * release status (mburns, 13:07:08) * patches in f17 topic branch gets it to almost working (mburns, 13:10:15) * 1 outstanding issue -- network page not working right (mburns, 13:10:24) * ACTION: jboggs looking at network page today (mburns, 13:10:32) * other topics (mburns, 13:12:01) Meeting ended at 13:14:42 UTC. Action Items ------------ * mburns jboggs fabiand get 2.4.0 out the door * mburns jboggs review network manager feature page * mburns to file bzs for stateless * mburns to add 2.6.0 release and re-target bugs * jboggs looking at network page today Action Items, by person ----------------------- * fabiand * mburns jboggs fabiand get 2.4.0 out the door * jboggs * mburns jboggs fabiand get 2.4.0 out the door * mburns jboggs review network manager feature page * jboggs looking at network page today * mburns * mburns jboggs fabiand get 2.4.0 out the door * mburns jboggs review network manager feature page * mburns to file bzs for stateless * mburns to add 2.6.0 release and re-target bugs * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mburns (37) * fabiand (6) * jboggs (5) * ovirtbot (3) * pmyers (0) * READ10 (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From fabiand at redhat.com Thu Jun 14 10:31:54 2012 From: fabiand at redhat.com (Fabian Deutsch) Date: Thu, 14 Jun 2012 12:31:54 +0200 Subject: [node-devel] Fedora 17 status update In-Reply-To: <1339168202.2510.19.camel@fdeutsch-laptop.local> References: <1339168202.2510.19.camel@fdeutsch-laptop.local> Message-ID: <1339669914.2277.6.camel@fdeutsch-laptop.local> Hey, we nailed down most of the bugs and it seems as if we can provide a fresh F!/ based build within the next hours, so it get's some love from early testers. Greetings fabian Am Freitag, den 08.06.2012, 17:10 +0200 schrieb Fabian Deutsch: > Hey, > > during the last couple of days I tried to get a working Fedora 17 based > Node build running, which was blocked by some bugs summarized here [1]. > > The current status is that - after some segfaults, selinux and dracut > problems - Node can be installed and we can login again. > Currently the usage and further testing is semi-blocked by a problem > with the TUI because you currently can't configure any NIC. > The interested reader can find most of the for 2.4.0 here [2]. > > Feature freeze was yesterday, that's fine, but there is still a bit to > do to get a stable F17 based Node for the overall beta. > I'm optimistic that we can nail down most the bugs during the next days. > > And the plan is that the Fedora 17 based builds will be the first ones > with some basic automated continuous testing [3]. > > Greetings for now > fabian > > -- > [1] https://bugzilla.redhat.com/show_bug.cgi?id=824420 > [2] http://gerrit.ovirt.org/#/q/status:open+project:ovirt-node,n,z > [3] http://ovirt.org/wiki/Node_Testing > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From mburns at redhat.com Thu Jun 14 13:25:20 2012 From: mburns at redhat.com (Mike Burns) Date: Thu, 14 Jun 2012 09:25:20 -0400 Subject: [node-devel] oVirt Node 2.4.0 Posted Message-ID: <1339680320.2175.4.camel@mburns-laptop.usersys.redhat.com> The image is posted to the beta area on ovirt.org[1]. There will likely be a 2.4.1 release in the next couple weeks as we clean up some other issues. Mike [1] http://ovirt.org/releases/beta/ From dennisml at conversis.de Thu Jun 14 16:50:50 2012 From: dennisml at conversis.de (Dennis Jacobfeuerborn) Date: Thu, 14 Jun 2012 18:50:50 +0200 Subject: [node-devel] oVirt Node 2.4.0 Posted In-Reply-To: <1339680320.2175.4.camel@mburns-laptop.usersys.redhat.com> References: <1339680320.2175.4.camel@mburns-laptop.usersys.redhat.com> Message-ID: <4FDA166A.2090703@conversis.de> On 06/14/2012 03:25 PM, Mike Burns wrote: > The image is posted to the beta area on ovirt.org[1]. There will likely > be a 2.4.1 release in the next couple weeks as we clean up some other > issues. I just did a test install and this is the result so far: When booting the iso itself and the installed node later I get the following output: rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" the boot process continues though. I can't seem to configure the network. When I move to "eth0" and hit enter I see a blue screen for about 20 seconds and then I get back to the grey background with header and footer but nothing in the content area. Hitting a cursor key the menu appears but in the top left corner instead of where it's supposed to be. Selecting anything doesn't change the content are though. When I hit f12 the gui apparently resets and everything looks alright again. Looking at the logs I see ovirtfunctions - unable to determine ip/netmask from: ovirtfunctions - unable to determine ip/netmask from: Device "breth0" does not exist. Is there a manual way to configure the networking so I can test the engine connection? Regards, Dennis From mburns at redhat.com Thu Jun 14 17:10:31 2012 From: mburns at redhat.com (Mike Burns) Date: Thu, 14 Jun 2012 13:10:31 -0400 Subject: [node-devel] oVirt Node 2.4.0 Posted In-Reply-To: <4FDA166A.2090703@conversis.de> References: <1339680320.2175.4.camel@mburns-laptop.usersys.redhat.com> <4FDA166A.2090703@conversis.de> Message-ID: <1339693831.2175.11.camel@mburns-laptop.usersys.redhat.com> On Thu, 2012-06-14 at 18:50 +0200, Dennis Jacobfeuerborn wrote: > On 06/14/2012 03:25 PM, Mike Burns wrote: > > The image is posted to the beta area on ovirt.org[1]. There will likely > > be a 2.4.1 release in the next couple weeks as we clean up some other > > issues. > > I just did a test install and this is the result so far: > > When booting the iso itself and the installed node later I get the > following output: > rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" > the boot process continues though. > > I can't seem to configure the network. When I move to "eth0" and hit enter > I see a blue screen for about 20 seconds and then I get back to the grey > background with header and footer but nothing in the content area. Hitting > a cursor key the menu appears but in the top left corner instead of where > it's supposed to be. Selecting anything doesn't change the content are > though. When I hit f12 the gui apparently resets and everything looks > alright again. > Argh, we were seeing this in builds just before the official one. There was a patch that fixed it that was apparently missed int the build. I'm respinning a new 2.4.0 build now (2.4.0-1 actually). Mike > Looking at the logs I see > ovirtfunctions - unable to determine ip/netmask from: > ovirtfunctions - unable to determine ip/netmask from: Device "breth0" does > not exist. > > Is there a manual way to configure the networking so I can test the engine > connection? > > Regards, > Dennis > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From mburns at redhat.com Thu Jun 14 17:58:01 2012 From: mburns at redhat.com (Mike Burns) Date: Thu, 14 Jun 2012 13:58:01 -0400 Subject: [node-devel] oVirt Node 2.4.0-1 Posted In-Reply-To: <1339693831.2175.11.camel@mburns-laptop.usersys.redhat.com> References: <1339680320.2175.4.camel@mburns-laptop.usersys.redhat.com> <4FDA166A.2090703@conversis.de> <1339693831.2175.11.camel@mburns-laptop.usersys.redhat.com> Message-ID: <1339696681.2175.14.camel@mburns-laptop.usersys.redhat.com> 2.4.0-1 is now posted in the same place as 2.4.0. It includes a fix for the network screen not working correctly (patch was merged, but was missing from my repo when I built). Mike On Thu, 2012-06-14 at 13:10 -0400, Mike Burns wrote: > On Thu, 2012-06-14 at 18:50 +0200, Dennis Jacobfeuerborn wrote: > > On 06/14/2012 03:25 PM, Mike Burns wrote: > > > The image is posted to the beta area on ovirt.org[1]. There will likely > > > be a 2.4.1 release in the next couple weeks as we clean up some other > > > issues. > > > > I just did a test install and this is the result so far: > > > > When booting the iso itself and the installed node later I get the > > following output: > > rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" > > the boot process continues though. > > > > I can't seem to configure the network. When I move to "eth0" and hit enter > > I see a blue screen for about 20 seconds and then I get back to the grey > > background with header and footer but nothing in the content area. Hitting > > a cursor key the menu appears but in the top left corner instead of where > > it's supposed to be. Selecting anything doesn't change the content are > > though. When I hit f12 the gui apparently resets and everything looks > > alright again. > > > > Argh, we were seeing this in builds just before the official one. > There was a patch that fixed it that was apparently missed int the > build. I'm respinning a new 2.4.0 build now (2.4.0-1 actually). > > Mike > > > > Looking at the logs I see > > ovirtfunctions - unable to determine ip/netmask from: > > ovirtfunctions - unable to determine ip/netmask from: Device "breth0" does > > not exist. > > > > Is there a manual way to configure the networking so I can test the engine > > connection? > > > > Regards, > > Dennis > > _______________________________________________ > > node-devel mailing list > > node-devel at ovirt.org > > http://lists.ovirt.org/mailman/listinfo/node-devel > > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From dennisml at conversis.de Thu Jun 14 21:32:44 2012 From: dennisml at conversis.de (Dennis Jacobfeuerborn) Date: Thu, 14 Jun 2012 23:32:44 +0200 Subject: [node-devel] oVirt Node 2.4.0-1 Posted In-Reply-To: <1339696681.2175.14.camel@mburns-laptop.usersys.redhat.com> References: <1339680320.2175.4.camel@mburns-laptop.usersys.redhat.com> <4FDA166A.2090703@conversis.de> <1339693831.2175.11.camel@mburns-laptop.usersys.redhat.com> <1339696681.2175.14.camel@mburns-laptop.usersys.redhat.com> Message-ID: <4FDA587C.6040901@conversis.de> Thanks! With the new iso I can successfully configure the network. When I try to register the node with the engine I get the same problem though. I select "oVirt Engine", enter the IP of the engine system and hit apply and get the same menu problem as with the Network option before. Regards, Dennis On 06/14/2012 07:58 PM, Mike Burns wrote: > 2.4.0-1 is now posted in the same place as 2.4.0. It includes a fix for > the network screen not working correctly (patch was merged, but was > missing from my repo when I built). > > Mike > > On Thu, 2012-06-14 at 13:10 -0400, Mike Burns wrote: >> On Thu, 2012-06-14 at 18:50 +0200, Dennis Jacobfeuerborn wrote: >>> On 06/14/2012 03:25 PM, Mike Burns wrote: >>>> The image is posted to the beta area on ovirt.org[1]. There will likely >>>> be a 2.4.1 release in the next couple weeks as we clean up some other >>>> issues. >>> >>> I just did a test install and this is the result so far: >>> >>> When booting the iso itself and the installed node later I get the >>> following output: >>> rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" >>> the boot process continues though. >>> >>> I can't seem to configure the network. When I move to "eth0" and hit enter >>> I see a blue screen for about 20 seconds and then I get back to the grey >>> background with header and footer but nothing in the content area. Hitting >>> a cursor key the menu appears but in the top left corner instead of where >>> it's supposed to be. Selecting anything doesn't change the content are >>> though. When I hit f12 the gui apparently resets and everything looks >>> alright again. >>> >> >> Argh, we were seeing this in builds just before the official one. >> There was a patch that fixed it that was apparently missed int the >> build. I'm respinning a new 2.4.0 build now (2.4.0-1 actually). >> >> Mike >> >> >>> Looking at the logs I see >>> ovirtfunctions - unable to determine ip/netmask from: >>> ovirtfunctions - unable to determine ip/netmask from: Device "breth0" does >>> not exist. >>> >>> Is there a manual way to configure the networking so I can test the engine >>> connection? >>> >>> Regards, >>> Dennis >>> _______________________________________________ >>> node-devel mailing list >>> node-devel at ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/node-devel >> >> >> _______________________________________________ >> node-devel mailing list >> node-devel at ovirt.org >> http://lists.ovirt.org/mailman/listinfo/node-devel > > From mburns at redhat.com Thu Jun 14 21:48:10 2012 From: mburns at redhat.com (Mike Burns) Date: Thu, 14 Jun 2012 17:48:10 -0400 Subject: [node-devel] oVirt Node 2.4.0-1 Posted In-Reply-To: <4FDA587C.6040901@conversis.de> References: <1339680320.2175.4.camel@mburns-laptop.usersys.redhat.com> <4FDA166A.2090703@conversis.de> <1339693831.2175.11.camel@mburns-laptop.usersys.redhat.com> <1339696681.2175.14.camel@mburns-laptop.usersys.redhat.com> <4FDA587C.6040901@conversis.de> Message-ID: <1339710490.31830.9.camel@mburns-laptop.usersys.redhat.com> On Thu, 2012-06-14 at 23:32 +0200, Dennis Jacobfeuerborn wrote: > Thanks! With the new iso I can successfully configure the network. > When I try to register the node with the engine I get the same problem > though. I select "oVirt Engine", enter the IP of the engine system and hit > apply and get the same menu problem as with the Network option before. > > Regards, > Dennis Hi Dennis, I've had another report of the same issue [1]. It's being investigated now. Mike [1] https://bugzilla.redhat.com/show_bug.cgi?id=832196 > > On 06/14/2012 07:58 PM, Mike Burns wrote: > > 2.4.0-1 is now posted in the same place as 2.4.0. It includes a fix for > > the network screen not working correctly (patch was merged, but was > > missing from my repo when I built). > > > > Mike > > > > On Thu, 2012-06-14 at 13:10 -0400, Mike Burns wrote: > >> On Thu, 2012-06-14 at 18:50 +0200, Dennis Jacobfeuerborn wrote: > >>> On 06/14/2012 03:25 PM, Mike Burns wrote: > >>>> The image is posted to the beta area on ovirt.org[1]. There will likely > >>>> be a 2.4.1 release in the next couple weeks as we clean up some other > >>>> issues. > >>> > >>> I just did a test install and this is the result so far: > >>> > >>> When booting the iso itself and the installed node later I get the > >>> following output: > >>> rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" > >>> the boot process continues though. > >>> > >>> I can't seem to configure the network. When I move to "eth0" and hit enter > >>> I see a blue screen for about 20 seconds and then I get back to the grey > >>> background with header and footer but nothing in the content area. Hitting > >>> a cursor key the menu appears but in the top left corner instead of where > >>> it's supposed to be. Selecting anything doesn't change the content are > >>> though. When I hit f12 the gui apparently resets and everything looks > >>> alright again. > >>> > >> > >> Argh, we were seeing this in builds just before the official one. > >> There was a patch that fixed it that was apparently missed int the > >> build. I'm respinning a new 2.4.0 build now (2.4.0-1 actually). > >> > >> Mike > >> > >> > >>> Looking at the logs I see > >>> ovirtfunctions - unable to determine ip/netmask from: > >>> ovirtfunctions - unable to determine ip/netmask from: Device "breth0" does > >>> not exist. > >>> > >>> Is there a manual way to configure the networking so I can test the engine > >>> connection? > >>> > >>> Regards, > >>> Dennis > >>> _______________________________________________ > >>> node-devel mailing list > >>> node-devel at ovirt.org > >>> http://lists.ovirt.org/mailman/listinfo/node-devel > >> > >> > >> _______________________________________________ > >> node-devel mailing list > >> node-devel at ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/node-devel > > > > > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From dennisml at conversis.de Thu Jun 14 22:45:20 2012 From: dennisml at conversis.de (Dennis Jacobfeuerborn) Date: Fri, 15 Jun 2012 00:45:20 +0200 Subject: [node-devel] oVirt Node 2.4.0-1 Posted In-Reply-To: <1339710490.31830.9.camel@mburns-laptop.usersys.redhat.com> References: <1339680320.2175.4.camel@mburns-laptop.usersys.redhat.com> <4FDA166A.2090703@conversis.de> <1339693831.2175.11.camel@mburns-laptop.usersys.redhat.com> <1339696681.2175.14.camel@mburns-laptop.usersys.redhat.com> <4FDA587C.6040901@conversis.de> <1339710490.31830.9.camel@mburns-laptop.usersys.redhat.com> Message-ID: <4FDA6980.3010601@conversis.de> On 06/14/2012 11:48 PM, Mike Burns wrote: > On Thu, 2012-06-14 at 23:32 +0200, Dennis Jacobfeuerborn wrote: >> Thanks! With the new iso I can successfully configure the network. >> When I try to register the node with the engine I get the same problem >> though. I select "oVirt Engine", enter the IP of the engine system and hit >> apply and get the same menu problem as with the Network option before. >> >> Regards, >> Dennis > > Hi Dennis, > > I've had another report of the same issue [1]. It's being investigated > now. > > Mike > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=832196 I added some information to that bug. Apparently setting the password for registration from the engine side works because after setting that I was able to make the node appear in the engine (by adding the node in the administration portal) but then the initialization fails. Regards, Dennis From mburns at redhat.com Fri Jun 15 10:13:21 2012 From: mburns at redhat.com (Mike Burns) Date: Fri, 15 Jun 2012 06:13:21 -0400 Subject: [node-devel] oVirt Node 2.4.0-1 Posted In-Reply-To: <4FDA6980.3010601@conversis.de> References: <1339680320.2175.4.camel@mburns-laptop.usersys.redhat.com> <4FDA166A.2090703@conversis.de> <1339693831.2175.11.camel@mburns-laptop.usersys.redhat.com> <1339696681.2175.14.camel@mburns-laptop.usersys.redhat.com> <4FDA587C.6040901@conversis.de> <1339710490.31830.9.camel@mburns-laptop.usersys.redhat.com> <4FDA6980.3010601@conversis.de> Message-ID: <1339755201.3734.6.camel@beelzebub.mburnsfire.net> On Fri, 2012-06-15 at 00:45 +0200, Dennis Jacobfeuerborn wrote: > On 06/14/2012 11:48 PM, Mike Burns wrote: > > On Thu, 2012-06-14 at 23:32 +0200, Dennis Jacobfeuerborn wrote: > >> Thanks! With the new iso I can successfully configure the network. > >> When I try to register the node with the engine I get the same problem > >> though. I select "oVirt Engine", enter the IP of the engine system and hit > >> apply and get the same menu problem as with the Network option before. > >> > >> Regards, > >> Dennis > > > > Hi Dennis, > > > > I've had another report of the same issue [1]. It's being investigated > > now. > > > > Mike > > > > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=832196 > > I added some information to that bug. Apparently setting the password for > registration from the engine side works because after setting that I was > able to make the node appear in the engine (by adding the node in the > administration portal) but then the initialization fails. > > Regards, > Dennis Thanks Dennis. It turns out that a bug in sanlock (832230) causes a problem in the build process of the iso where sanlock and vdsm packages don't get installed . I've patched the sanlock bug and sent the patch to the maintainer. In the meantime, I've built a temporary sanlock rpm and built the ISO using that RPM instead. I've confirmed that the ISO has vdsm and sanlock included and boots. It appears that there are additional bugs with registration though. Registering itself to engine fails completely while adding from engine side runs into different problems. The build is being pushed out because it's *better* than it was before and should be useful for debugging what's going on with registration. Mike > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From fabiand at redhat.com Tue Jun 19 10:44:02 2012 From: fabiand at redhat.com (Fabian Deutsch) Date: Tue, 19 Jun 2012 12:44:02 +0200 Subject: [node-devel] Continous Testing of Node Message-ID: <1340102642.2281.15.camel@fdeutsch-laptop.local> Hey, after some time oVirt Node builds are finally also running through Igor [1] - a tool to do some continuous testing on VMs and real hardware. Currently igor is doing a basic test, so testing if the automatic installation works and if the can reboot. This testing is done once each night and report is sent to the node-patches [2, 2a] mailing-list. Running the tests required some preparations to meet Node's requirements. Igor [1] can manage the lifetime of a test instance (or real server) and prepares cobbler to provision the instance. Afterwards it supervises the testing process and cleans everything when it reached it's EOL (by passing or failing the testcases). A client [3] is injected into the (build by Jenkins) ISO using jboggs plugin patches [4], which is executing all the necessary stuff on the Node. Now that the infrastructure is in place the next steps will be to add some testcases (structured into testsets and testsuites) to [5]. The testcases should cover automatic and TUI install, but further more we should even do unit tests on the underlying "libraries" (like ovirt-functions). This has to be done online, because most of the functions expect a running system. If you want to contribute testcases - or anything else - have a look at the examples in [1] and [2]. Greetings fabian -- [1] https://gitorious.org/ovirt/igord [2] http://lists.ovirt.org/pipermail/node-patches/ [2a] http://lists.ovirt.org/pipermail/node-patches/2012-June/001481.html [3] http://gerrit.ovirt.org/#/c/5460/ [4] https://gitorious.org/ovirt/ovirt-igor-client [5] https://gitorious.org/ovirt/ovirt-node-igor-testsuites -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From mburns at redhat.com Tue Jun 26 13:22:55 2012 From: mburns at redhat.com (Mike Burns) Date: Tue, 26 Jun 2012 09:22:55 -0400 Subject: [node-devel] oVirt Node Weekly Meeting Minutes -- 2012-06-26 Message-ID: <1340716975.3656.22.camel@beelzebub.mburnsfire.net> Minutes: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-26-13.00.html Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-26-13.00.txt Log: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-26-13.00.log.html ============================== #ovirt: ovirt-node weekly sync ============================== Meeting started by mburns at 13:00:33 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-26-13.00.log.html . Meeting summary --------------- * agenda and roll call (mburns, 13:00:38) * Action Item Review (mburns, 13:02:59) * LINK: (mburns, 13:03:02) * LINK: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-19-13.00.html (mburns, 13:03:03) * ACTION: mburns file stateless bzs (mburns, 13:03:49) * release status (mburns, 13:04:20) * oVirt Project Release pushed out to July 9 (mburns, 13:05:07) * LINK: (mburns, 13:05:57) * LINK: http://goo.gl/DqyqZ (mburns, 13:05:58) * LINK: http://goo.gl/DqyqZ (mburns, 13:06:50) * in good shape (mburns, 13:06:54) * ACTION: fabiand to review bugs for 2.4.1 and move to MODIFIED where appropriate (mburns, 13:15:40) * ACTION: jboggs to follow up on 832163 (mburns, 13:15:55) * ACTION: mburns to confirm vdsm version and post new build (mburns, 13:16:11) * Other Topics (mburns, 13:16:50) Meeting ended at 13:19:30 UTC. Action Items ------------ * mburns file stateless bzs * fabiand to review bugs for 2.4.1 and move to MODIFIED where appropriate * jboggs to follow up on 832163 * mburns to confirm vdsm version and post new build Action Items, by person ----------------------- * fabiand * fabiand to review bugs for 2.4.1 and move to MODIFIED where appropriate * jboggs * jboggs to follow up on 832163 * mburns * mburns file stateless bzs * mburns to confirm vdsm version and post new build * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mburns (51) * READ10 (3) * jboggs (3) * ovirtbot (3) * pmyers (0) * fabiand (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From taget at linux.vnet.ibm.com Wed Jun 27 02:32:47 2012 From: taget at linux.vnet.ibm.com (Eli Qiao) Date: Wed, 27 Jun 2012 10:32:47 +0800 Subject: [node-devel] 'No packages or groups specified' error when building node on F17 Message-ID: <4FEA70CF.7000709@linux.vnet.ibm.com> Hi all , I met a error when building the latest node on F17. The imgcreator says that:'No packages or groups specified' Can any one give a hand thanks? Here is the screen: /+ sudo /usr/sbin/setenforce Permissive + sudo livecd-creator -c /home/taget/ovirt-cache/node-creator-x86_64-tmp/ovirt-node-iso.ks -f ovirt-node-iso --tmpdir=/home/taget/ovirt-cache/node-creator-x86_64-tmp --cache=/home/taget/ovirt-cache/yum-x86_64 Traceback (most recent call last): File "/bin/livecd-creator", line 215, in sys.exit(main()) File "/bin/livecd-creator", line 178, in main title=title, product=product) File "/usr/lib/python2.7/site-packages/imgcreate/live.py", line 53, in __init__ useplugins=useplugins) File "/usr/lib/python2.7/site-packages/imgcreate/creator.py", line 792, in __init__ ImageCreator.__init__(self, ks, name, releasever=releasever, tmpdir=tmpdir, useplugins=useplugins) File "/usr/lib/python2.7/site-packages/imgcreate/creator.py", line 85, in __init__ self.__sanity_check() File "/usr/lib/python2.7/site-packages/imgcreate/creator.py", line 413, in __sanity_check raise CreatorError("No packages or groups specified") imgcreate.errors.CreatorError: No packages or groups specified + '[' Enforcing = Enforcing ']' + sudo /usr/sbin/setenforce Enforcing ERROR: ISO build failed./ -- Thanks. Best regards. --Eli Qiao -------------- next part -------------- An HTML attachment was scrubbed... URL: From jboggs at redhat.com Wed Jun 27 02:52:37 2012 From: jboggs at redhat.com (Joey Boggs) Date: Tue, 26 Jun 2012 22:52:37 -0400 Subject: [node-devel] 'No packages or groups specified' error when building node on F17 In-Reply-To: <4FEA70CF.7000709@linux.vnet.ibm.com> References: <4FEA70CF.7000709@linux.vnet.ibm.com> Message-ID: <4FEA7575.70301@redhat.com> On 06/26/2012 10:32 PM, Eli Qiao wrote: > Hi all , > > I met a error when building the latest node on F17. The imgcreator > says that:'No packages or groups specified' > > Can any one give a hand thanks? > > Here is the screen: > > / + sudo /usr/sbin/setenforce Permissive > + sudo livecd-creator -c > /home/taget/ovirt-cache/node-creator-x86_64-tmp/ovirt-node-iso.ks -f > ovirt-node-iso > --tmpdir=/home/taget/ovirt-cache/node-creator-x86_64-tmp > --cache=/home/taget/ovirt-cache/yum-x86_64 > Traceback (most recent call last): > File "/bin/livecd-creator", line 215, in > sys.exit(main()) > File "/bin/livecd-creator", line 178, in main > title=title, product=product) > File "/usr/lib/python2.7/site-packages/imgcreate/live.py", line 53, > in __init__ > useplugins=useplugins) > File "/usr/lib/python2.7/site-packages/imgcreate/creator.py", line > 792, in __init__ > ImageCreator.__init__(self, ks, name, releasever=releasever, > tmpdir=tmpdir, useplugins=useplugins) > File "/usr/lib/python2.7/site-packages/imgcreate/creator.py", line > 85, in __init__ > self.__sanity_check() > File "/usr/lib/python2.7/site-packages/imgcreate/creator.py", line > 413, in __sanity_check > raise CreatorError("No packages or groups specified") > imgcreate.errors.CreatorError: No packages or groups specified > + '[' Enforcing = Enforcing ']' > + sudo /usr/sbin/setenforce Enforcing > ERROR: ISO build failed./ > > -- > Thanks. Best regards. --Eli Qiao > > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel This is a bug, workaround right now is to install older pykickstart package until pykickstart-1.99.13 is available http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=37975 https://bugzilla.redhat.com/show_bug.cgi?id=819672 -------------- next part -------------- An HTML attachment was scrubbed... URL: From taget at linux.vnet.ibm.com Fri Jun 29 08:18:27 2012 From: taget at linux.vnet.ibm.com (Eli Qiao) Date: Fri, 29 Jun 2012 16:18:27 +0800 Subject: [node-devel] Failed build node on F16 and F15 Message-ID: <4FED64D3.4060401@linux.vnet.ibm.com> hi all I saw a special process in ovirt-node.spec.in : / %if %is_f16 # install libvirtd systemd service %{__install} -p -m0644 libvirtd.service %{buildroot}%{_unitdir} %endif/ %if %is_f16 %{_unitdir}/libvirtd.service %endif what about F17 ? doesn't F17 need them ? And also , I can't succeed to build node on F16 and F15 : 1 Linux ovirt 3.0.0-1.fc16.x86_64 : /+ /usr/bin/install -p -m0644 libvirtd.service /home/taget/rpmbuild/BUILDROOT/ovirt-node-2.4.0-999.20120629071917git872cb51.fc16.x86_64/lib/systemd/system /usr/bin/install: cannot create regular file `/home/taget/rpmbuild/BUILDROOT/ovirt-node-2.4.0-999.20120629071917git872cb51.fc16.x86_64/lib/systemd/system': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.pvxomU (%install)/ 2 Linux ovirt-node 2.6.38.6-26.rc1.fc15.i686 : /RPM build errors: File not found: /home/ovirt/rpmbuild/BUILDROOT/ovirt-node-2.4.0-999.20120629080506git872cb51.fc15.i386/lib/systemd/system/ovirt.service File not found: /home/ovirt/rpmbuild/BUILDROOT/ovirt-node-2.4.0-999.20120629080506git872cb51.fc15.i386/lib/systemd/system/ovirt-awake.service File not found: /home/ovirt/rpmbuild/BUILDROOT/ovirt-node-2.4.0-999.20120629080506git872cb51.fc15.i386/lib/systemd/system/ovirt-firstboot.service File not found: /home/ovirt/rpmbuild/BUILDROOT/ovirt-node-2.4.0-999.20120629080506git872cb51.fc15.i386/lib/systemd/system/ovirt-post.service File not found: /home/ovirt/rpmbuild/BUILDROOT/ovirt-node-2.4.0-999.20120629080506git872cb51.fc15.i386/lib/systemd/system/ovirt-early.service File not found: /home/ovirt/rpmbuild/BUILDROOT/ovirt-node-2.4.0-999.20120629080506git872cb51.fc15.i386/lib/systemd/system/ovirt-cim.service/ there's no lib dir in the rpmbuild dir. /[ovirt at ovirt-node ovirt-node-2.4.0-999.20120629080506git872cb51.fc15.i386]$ pwd /home/ovirt/rpmbuild/BUILDROOT/ovirt-node-2.4.0-999.20120629080506git872cb51.fc15.i386 [ovirt at ovirt-node ovirt-node-2.4.0-999.20120629080506git872cb51.fc15.i386]$ ls etc usr/ I think the {_unitdir} are difference between F17 and F16&F15 , so I give a ugly fix in ovirt-node.spec.in: /%define is_f17 %(test "0%{?fedora}" == "017" && echo 1 || echo 0) %if %is_f17 %else %define _unitdir /usr/lib/systemd/system %endif/ I can build it successfully , but I am not sure it is correct. -- Thanks. Best regards. --Eli Qiao -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabiand at redhat.com Fri Jun 29 08:42:18 2012 From: fabiand at redhat.com (Fabian Deutsch) Date: Fri, 29 Jun 2012 10:42:18 +0200 Subject: [node-devel] Failed build node on F16 and F15 In-Reply-To: <4FED64D3.4060401@linux.vnet.ibm.com> References: <4FED64D3.4060401@linux.vnet.ibm.com> Message-ID: <1340959338.2280.4.camel@fdeutsch-laptop.local> Hey, Am Freitag, den 29.06.2012, 16:18 +0800 schrieb Eli Qiao: > %if %is_f16 > # install libvirtd systemd service > %{__install} -p -m0644 libvirtd.service %{buildroot}%{_unitdir} > %endif > > %if %is_f16 > %{_unitdir}/libvirtd.service > %endif > > what about F17 ? doesn't F17 need them ? IIRC libvirt is providing it's own service file on F17. > I think the {_unitdir} are difference between F17 and F16&F15 , so I > give a ugly fix in ovirt-node.spec.in: > > %define is_f17 %(test "0%{?fedora}" == "017" && echo 1 || echo 0) > %if %is_f17 > %else > %define _unitdir /usr/lib/systemd/system > %endif > > I can build it successfully , but I am not sure it is correct. That sounds reasonable, I wonder why systemd-units (which AFAIK defines _unitdir) isn't providing a different path on F15/F16. Greetings fabian > -- > Thanks. Best regards. --Eli Qiao > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From apevec at gmail.com Fri Jun 29 09:57:08 2012 From: apevec at gmail.com (Alan Pevec) Date: Fri, 29 Jun 2012 11:57:08 +0200 Subject: [node-devel] Failed build node on F16 and F15 In-Reply-To: <1340959338.2280.4.camel@fdeutsch-laptop.local> References: <4FED64D3.4060401@linux.vnet.ibm.com> <1340959338.2280.4.camel@fdeutsch-laptop.local> Message-ID: On Fri, Jun 29, 2012 at 10:42 AM, Fabian Deutsch wrote: > Am Freitag, den 29.06.2012, 16:18 +0800 schrieb Eli Qiao: >> I think the {_unitdir} are difference between F17 and F16&F15 , so I >> give a ugly fix in ovirt-node.spec.in: >> >> %define is_f17 %(test "0%{?fedora}" == "017" && echo 1 || echo 0) >> %if %is_f17 >> %else >> %define _unitdir /usr/lib/systemd/system >> %endif >> >> I can build it successfully , but I am not sure it is correct. > > That sounds reasonable, I wonder why systemd-units (which AFAIK defines > _unitdir) isn't providing a different path on F15/F16. F17 has that /usr-move feature, where all moved under /usr, it is different on F16: $ rpm -qf /etc/rpm/macros.systemd systemd-units-37-25.fc16.x86_64 $ cat /etc/rpm/macros.systemd %_unitdir /lib/systemd/system The problem for F16 is in services/Makefile.am: systemunitdir=$(prefix)/lib/systemd/system so ovirt *.services end up in %{buildroot}/usr/lib/systemd/system/ on both F16 and F17. F16 systemd Makefile has: systemunitdir=$(rootdir)/lib/systemd/system so you'd need some conditional in ovirt makefile if you want to support building on both F16/17. Cheers, Alan