From mburns at redhat.com Tue May 1 12:08:38 2012 From: mburns at redhat.com (Mike Burns) Date: Tue, 01 May 2012 08:08:38 -0400 (EDT) Subject: [node-devel] Cancelled: oVirt Node weekly meeting Message-ID: <0e8ff474-fe90-416d-8d80-7a962361dca5@zmail17.collab.prod.int.phx2.redhat.com> A single instance of the following meeting has been cancelled: Subject: oVirt Node weekly meeting Organizer: "Mike Burns" Location: #ovirt on irc.oftc.net Time: Tuesday, May 1, 2012, 9:00:00 AM - 9:30:00 AM GMT -05:00 US/Canada Eastern Invitees: node-devel at ovirt.org; aliguori at linux.vnet.ibm.com; anthony at codemonkey.ws; whenry at redhat.com *~*~*~*~*~*~*~*~*~* -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 2629 bytes Desc: not available URL: From mvanhorssen at vluchtelingenwerk.nl Mon May 7 14:34:26 2012 From: mvanhorssen at vluchtelingenwerk.nl (Michel van Horssen) Date: Mon, 07 May 2012 16:34:26 +0200 (CEST) Subject: [node-devel] Still not abel to migrate to node Message-ID: <7a3eec88-0a5e-4297-acad-2e9025f248e8@mailstore1.vluchtelingenwerk.nl> Hi, I've re-installed my system with a separate DNS just for my test. Time on the servers are correct. Still migrating a VM from the VDSM on my engine towards a node gives me problems. The vdsm.log on the engine says: --- Thread-203040::ERROR::2012-05-07 15:51:36,794::vm::170::vm.Vm::(_recover) vmId=`95fac60f-49f5-4dcb-8c2d-2dfd926c781b`::operation failed: Failed to connect to remote libvirt URI qemu+tls://192.168.10.79/system Thread-203041::DEBUG::2012-05-07 15:51:36,795::libvirtvm::329::vm.Vm::(run) vmId=`95fac60f-49f5-4dcb-8c2d-2dfd926c781b`::migration downtime thread exiting Thread-203040::ERROR::2012-05-07 15:51:37,045::vm::234::vm.Vm::(run) vmId=`95fac60f-49f5-4dcb-8c2d-2dfd926c781b`::Traceback (most recent call last): File "/usr/share/vdsm/vm.py", line 217, in run self._startUnderlyingMigration() File "/usr/share/vdsm/libvirtvm.py", line 443, in _startUnderlyingMigration None, maxBandwidth) File "/usr/share/vdsm/libvirtvm.py", line 483, in f ret = attr(*args, **kwargs) File "/usr/share/vdsm/libvirtconnection.py", line 79, in wrapper ret = f(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 971, in migrateToURI2 if ret == -1: raise libvirtError ('virDomainMigrateToURI2() failed', dom=self) libvirtError: operation failed: Failed to connect to remote libvirt URI qemu+tls://192.168.10.79/system --- Can someone give me a pointer where to look? Regards, Michel From mvanhorssen at vluchtelingenwerk.nl Mon May 7 15:07:40 2012 From: mvanhorssen at vluchtelingenwerk.nl (Michel van Horssen) Date: Mon, 07 May 2012 17:07:40 +0200 (CEST) Subject: [node-devel] Still not abel to migrate to node In-Reply-To: <7a3eec88-0a5e-4297-acad-2e9025f248e8@mailstore1.vluchtelingenwerk.nl> Message-ID: <438760c0-425c-4a8f-8dfd-5840edd99617@mailstore1.vluchtelingenwerk.nl> Some extra info: If I go into virsh on the engine/vdsm and type connect qemu+tls://192.168.10.79/system I get: error: unable to connect to server at '192.168.10.79:16514': Connection refused (192.168.10.79 is the nodes IP address) If I open virsh on the node and type qemu+tls://192.168.10.31/system there no error and I have a connection (192.168.10.31 is the engine/vdsm's IP address) This explains why I can migrate towards the engine/vdsm but not towards the node. Not sure but it seems a certificate thing. Any pointers where to start looking? Michel ----- Oorspronkelijk bericht ----- > Van: "Michel van Horssen" > Aan: node-devel at ovirt.org > Verzonden: Maandag 7 mei 2012 16:34:26 > Onderwerp: [node-devel] Still not abel to migrate to node > > Hi, > > I've re-installed my system with a separate DNS just for my test. > Time on the servers are correct. > Still migrating a VM from the VDSM on my engine towards a node gives > me problems. > > The vdsm.log on the engine says: > > --- > Thread-203040::ERROR::2012-05-07 > 15:51:36,794::vm::170::vm.Vm::(_recover) > vmId=`95fac60f-49f5-4dcb-8c2d-2dfd926c781b`::operation failed: > Failed to connect to remote libvirt URI > qemu+tls://192.168.10.79/system > Thread-203041::DEBUG::2012-05-07 > 15:51:36,795::libvirtvm::329::vm.Vm::(run) > vmId=`95fac60f-49f5-4dcb-8c2d-2dfd926c781b`::migration downtime > thread exiting > Thread-203040::ERROR::2012-05-07 15:51:37,045::vm::234::vm.Vm::(run) > vmId=`95fac60f-49f5-4dcb-8c2d-2dfd926c781b`::Traceback (most recent > call last): > File "/usr/share/vdsm/vm.py", line 217, in run > self._startUnderlyingMigration() > File "/usr/share/vdsm/libvirtvm.py", line 443, in > _startUnderlyingMigration > None, maxBandwidth) > File "/usr/share/vdsm/libvirtvm.py", line 483, in f > ret = attr(*args, **kwargs) > File "/usr/share/vdsm/libvirtconnection.py", line 79, in wrapper > ret = f(*args, **kwargs) > File "/usr/lib64/python2.7/site-packages/libvirt.py", line 971, in > migrateToURI2 > if ret == -1: raise libvirtError ('virDomainMigrateToURI2() > failed', dom=self) > libvirtError: operation failed: Failed to connect to remote libvirt > URI qemu+tls://192.168.10.79/system > --- > > Can someone give me a pointer where to look? > > Regards, > Michel > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel > From mburns at redhat.com Tue May 8 13:31:43 2012 From: mburns at redhat.com (Mike Burns) Date: Tue, 08 May 2012 09:31:43 -0400 Subject: [node-devel] oVirt Node Weekly Meeting Minutes -- 2012-05-08 Message-ID: <1336483903.27284.10.camel@beelzebub.mburnsfire.net> Minutes: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-08-13.03.html Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-08-13.03.txt Log: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-08-13.03.log.html ============================== #ovirt: ovirt node weekly sync ============================== Meeting started by mburns at 13:03:02 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-08-13.03.log.html . Meeting summary --------------- * agenda and roll call (mburns, 13:03:20) * action item review (mburns, 13:05:47) * LINK: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-04-24-13.01.html (mburns, 13:05:50) * a bunch of bzs moved out of 2.4.0 (mburns, 13:06:33) * ACTION: mburns to review stateless status and wiki page (mburns, 13:08:19) * ACTION: fabiand to work on network manager feature page (mburns, 13:09:20) * release status (mburns, 13:10:32) * oVirt Project delayed their release from May 31 to end of June (27th iirc) (mburns, 13:10:57) * ACTION: mburns to review 2.4.0 bug list and defer RFEs that won't make it (mburns, 13:16:01) * patch reviews (mburns, 13:16:36) * ~50-60 patches need review (mburns, 13:17:38) * other topics? (mburns, 13:20:14) Meeting ended at 13:21:50 UTC. Action Items ------------ * mburns to review stateless status and wiki page * fabiand to work on network manager feature page * mburns to review 2.4.0 bug list and defer RFEs that won't make it Action Items, by person ----------------------- * fabiand * fabiand to work on network manager feature page * mburns * mburns to review stateless status and wiki page * mburns to review 2.4.0 bug list and defer RFEs that won't make it * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mburns (48) * fabiand (6) * jboggs (2) * ovirtbot (2) * pmyers (1) * Elad (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From fabiand at redhat.com Tue May 8 16:42:34 2012 From: fabiand at redhat.com (Fabian Deutsch) Date: Tue, 08 May 2012 18:42:34 +0200 Subject: [node-devel] [RFC] Test Automation (cont.) Message-ID: <1336495354.2221.46.camel@fdeutsch-laptop.local> Moin, I've written about the automation of testing about a month ago [1]. Now continuing those thoughts this time it's about how we can establish a system to do some automated installation and run-time Node testing. The automated testing of the installation and run-time functionality of the Node is a big deal, because it's getting more more annoying to do all the testing manually. Oh - and it shall also help to prevent regressions and catch bugs in complex setups. A flexible system is needed which can - test several testcases (many cases are condensed into one testsuite) - on different hardware - with different setups (e.g. once with 4 individual disks, then with a VG spanning all 4 of them, or two VG's each spanning two, and this once on Fedora and then again on CentOS, etc.) - such a system should self provision the required hardware and prepare the required setup The intended workflow and terms are explained in more detail here [2]. I singled out the following milestones on the path to reach the point where an automated test is triggered by jenkins: - A Node is able to fetch and run a given testsuite - A controller can do the provisioning of real or virtual hosts - The controller is extended so it can provision and run a testsuite on a Host - Jenkins triggers the controller and the controller reports back I'd like to discuss if I got all requirements right or missed some cases, thus if there are cases which can not be covered by the outlined system and if the ordering is to invasive or not. Maybe you've also got some other thoughts and ideas you would like to share your 2ct on this topic. Thanks, fabian -- [1] http://lists.ovirt.org/pipermail/node-devel/2012-April/000204.html [2] http://ovirt.org/wiki/Node_Testing#Workflow -------------- 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 Wed May 9 11:57:12 2012 From: mburns at redhat.com (Mike Burns) Date: Wed, 09 May 2012 07:57:12 -0400 Subject: [node-devel] Still not abel to migrate to node In-Reply-To: <438760c0-425c-4a8f-8dfd-5840edd99617@mailstore1.vluchtelingenwerk.nl> References: <438760c0-425c-4a8f-8dfd-5840edd99617@mailstore1.vluchtelingenwerk.nl> Message-ID: <1336564632.3397.8.camel@beelzebub.mburnsfire.net> On Mon, 2012-05-07 at 17:07 +0200, Michel van Horssen wrote: > Some extra info: > > If I go into virsh on the engine/vdsm and type connect qemu+tls://192.168.10.79/system I get: > > error: unable to connect to server at '192.168.10.79:16514': Connection refused > > (192.168.10.79 is the nodes IP address) > > If I open virsh on the node and type qemu+tls://192.168.10.31/system there no error and I have a connection > > (192.168.10.31 is the engine/vdsm's IP address) > > This explains why I can migrate towards the engine/vdsm but not towards the node. > > Not sure but it seems a certificate thing. > > Any pointers where to start looking? > > Michel This strikes me as more of a vdsm problem than ovirt-node directly. Once node is registered to engine, we hand over all control of libvirt and networking (among other things) to the engine to manage. If migration is failing due to some setting on the node, then vdsm should probably be changing that setting when it comes online. I'm adding the vdsm-devel list to get them to look at this issue. Mike > > > ----- Oorspronkelijk bericht ----- > > Van: "Michel van Horssen" > > Aan: node-devel at ovirt.org > > Verzonden: Maandag 7 mei 2012 16:34:26 > > Onderwerp: [node-devel] Still not abel to migrate to node > > > > Hi, > > > > I've re-installed my system with a separate DNS just for my test. > > Time on the servers are correct. > > Still migrating a VM from the VDSM on my engine towards a node gives > > me problems. > > > > The vdsm.log on the engine says: > > > > --- > > Thread-203040::ERROR::2012-05-07 > > 15:51:36,794::vm::170::vm.Vm::(_recover) > > vmId=`95fac60f-49f5-4dcb-8c2d-2dfd926c781b`::operation failed: > > Failed to connect to remote libvirt URI > > qemu+tls://192.168.10.79/system > > Thread-203041::DEBUG::2012-05-07 > > 15:51:36,795::libvirtvm::329::vm.Vm::(run) > > vmId=`95fac60f-49f5-4dcb-8c2d-2dfd926c781b`::migration downtime > > thread exiting > > Thread-203040::ERROR::2012-05-07 15:51:37,045::vm::234::vm.Vm::(run) > > vmId=`95fac60f-49f5-4dcb-8c2d-2dfd926c781b`::Traceback (most recent > > call last): > > File "/usr/share/vdsm/vm.py", line 217, in run > > self._startUnderlyingMigration() > > File "/usr/share/vdsm/libvirtvm.py", line 443, in > > _startUnderlyingMigration > > None, maxBandwidth) > > File "/usr/share/vdsm/libvirtvm.py", line 483, in f > > ret = attr(*args, **kwargs) > > File "/usr/share/vdsm/libvirtconnection.py", line 79, in wrapper > > ret = f(*args, **kwargs) > > File "/usr/lib64/python2.7/site-packages/libvirt.py", line 971, in > > migrateToURI2 > > if ret == -1: raise libvirtError ('virDomainMigrateToURI2() > > failed', dom=self) > > libvirtError: operation failed: Failed to connect to remote libvirt > > URI qemu+tls://192.168.10.79/system > > --- > > > > Can someone give me a pointer where to look? > > > > Regards, > > Michel > > _______________________________________________ > > 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 mvanhorssen at vluchtelingenwerk.nl Wed May 9 12:14:51 2012 From: mvanhorssen at vluchtelingenwerk.nl (Michel van Horssen) Date: Wed, 09 May 2012 14:14:51 +0200 (CEST) Subject: [node-devel] Still not abel to migrate to node In-Reply-To: <1336564632.3397.8.camel@beelzebub.mburnsfire.net> Message-ID: Hi Mike, > This strikes me as more of a vdsm problem than ovirt-node directly. > Once node is registered to engine, we hand over all control of > libvirt > and networking (among other things) to the engine to manage. If > migration is failing due to some setting on the node, then vdsm > should > probably be changing that setting when it comes online. > > I'm adding the vdsm-devel list to get them to look at this issue. Thnx Mike hope to get it solved soon. From mvanhorssen at vluchtelingenwerk.nl Fri May 11 10:02:25 2012 From: mvanhorssen at vluchtelingenwerk.nl (Michel van Horssen) Date: Fri, 11 May 2012 12:02:25 +0200 (CEST) Subject: [node-devel] Still not abel to migrate to node In-Reply-To: Message-ID: <90c9428f-adba-4462-aabb-2cfd983eb6a0@mailstore1.vluchtelingenwerk.nl> Hi Mike, > This strikes me as more of a vdsm problem than ovirt-node directly. > Once node is registered to engine, we hand over all control of > libvirt and networking (among other things) to the engine to manage. I just tried migrating between 2 nodes but that also fails. Doing a connect between the 2 nodes from a virsh I get the same connection refused I get when trying to connect the node from the vdsm on the engine server. So they can't do qemu+tls:/ipaddress/system to each other. Stranger still I just tried the qemu+tls connect to the vdsm which worked before, now it's also a connection refused I get back. > If migration is failing due to some setting on the node, then vdsm > should probably be changing that setting when it comes online. I'll attache a grep from the vdsm.log while the migration was started from nodes. Maybe someone can take a look and hopefully find something. Time difference between the servers is about 40 seconds. > Mike Michel -------------- next part -------------- A non-text attachment was scrubbed... Name: node-migrations.tar.gz Type: application/x-compressed-tar Size: 10536 bytes Desc: not available URL: From mvanhorssen at vluchtelingenwerk.nl Fri May 11 09:56:00 2012 From: mvanhorssen at vluchtelingenwerk.nl (Michel van Horssen) Date: Fri, 11 May 2012 11:56:00 +0200 (CEST) Subject: [node-devel] Still not abel to migrate to node In-Reply-To: <1336564632.3397.8.camel@beelzebub.mburnsfire.net> Message-ID: Hi Mike, > This strikes me as more of a vdsm problem than ovirt-node directly. > Once node is registered to engine, we hand over all control of > libvirt and networking (among other things) to the engine to manage. I just tried migrating between 2 nodes but that also fails. Doing a connect between the 2 nodes from a virsh I get the same connection refused I get when trying to connect the node from the vdsm on the engine server. So they can't do qemu+tls:/ipaddress/system to each other. Stranger still I just tried the qemu+tls connect to the vdsm which worked before, now it's also a connection refused I get back. > If migration is failing due to some setting on the node, then vdsm > should probably be changing that setting when it comes online. I'll attache a grep from the vdsm.log while the migration was started from nodes. Maybe someone can take a look and hopefully find something. Time difference between the servers is about 40 seconds. > Mike Michel -------------- next part -------------- A non-text attachment was scrubbed... Name: node-migrating-away-from.log Type: text/x-log Size: 18547 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: node-migrating-towards-to.log Type: text/x-log Size: 58354 bytes Desc: not available URL: From mvanhorssen at vluchtelingenwerk.nl Fri May 11 10:54:09 2012 From: mvanhorssen at vluchtelingenwerk.nl (Michel van Horssen) Date: Fri, 11 May 2012 12:54:09 +0200 (CEST) Subject: [node-devel] Still not abel to migrate to node In-Reply-To: Message-ID: sorry for the double postings :) From minqf at sina.com Fri May 18 08:07:42 2012 From: minqf at sina.com (QingFeng.Min) Date: Fri, 18 May 2012 16:07:42 +0800 Subject: [node-devel] ovirt-node create iso failed Message-ID: <003001cd34cd$4cd267d0$e6773770$@sina.com> $ make iso publish rm -f *.ks Node Creator script is: ~/git/ovirt-node/recipe/node-creator cp ~/git/ovirt-node/recipe/*.ks . rm -f version.ks ( \ echo "PRODUCT='"oVirt Node Hypervisor"'" ;\ echo "PRODUCT_SHORT='"oVirt Node Hypervisor"'" ;\ echo "PACKAGE=ovirt-node-iso" ;\ echo "VERSION=2.3.0" ;\ echo "RELEASE=999.3.fc16" ;\ ) > version.ks ksflatten -c ovirt-node-image.ks -o ovirt-node-iso.ks ~/git/ovirt-node/recipe/node-creator ovirt-node-iso.ks [sudo] password for minqf: warning: libgcc-4.6.3-2.fc16.x86_64: Header V3 RSA/SHA256 Signature, key ID a82ba4b7: NOKEY Installing: libgcc ##################### [ 1/502] Installing: setup ##################### [ 2/502] Installing: filesystem ##################### [ 3/502] Installing: bind-license ##################### [ 4/502] Installing: fedora-release ##################### [ 5/502] Installing: basesystem ##################### [ 6/502] Installing: ncurses-base ##################### [ 7/502] Installing: vgabios ##################### [ 8/502] Installing: xen-licenses ##################### [ 9/502] Installing: gpxe-roms-qemu ##################### [ 10/502] Installing: cim-schema ##################### [ 11/502] Installing: poppler-data ##################### [ 12/502] Installing: mailcap ##################### [ 13/502] Installing: libX11-common ##################### [ 14/502] Installing: ca-certificates ##################### [ 15/502] Installing: tzdata ##################### [ 16/502] Installing: nss-softokn-freebl ##################### [ 17/502] Installing: glibc-common ##################### [ 18/502] Installing: glibc ##################### [ 19/502] Installing: ncurses-libs ##################### [ 20/502] Installing: bash ##################### [ 21/502] Installing: libsepol ##################### [ 22/502] Installing: libselinux ##################### [ 23/502] Installing: libattr ##################### [ 24/502] Installing: libcap ##################### [ 25/502] Installing: zlib ##################### [ 26/502] Installing: libstdc++ ##################### [ 27/502] Installing: libxml2 ##################### [ 28/502] Installing: info ##################### [ 29/502] Installing: libuuid ##################### [ 30/502] Installing: libcom_err ##################### [ 31/502] Installing: audit-libs ##################### [ 32/502] Installing: bzip2-libs ##################### [ 33/502] Installing: readline ##################### [ 34/502] Installing: popt ##################### [ 35/502] Installing: chkconfig ##################### [ 36/502] Installing: nspr ##################### [ 37/502] Installing: dbus-libs ##################### [ 38/502] Installing: libacl ##################### [ 39/502] Installing: libgpg-error ##################### [ 40/502] Installing: libgcrypt ##################### [ 41/502] Installing: nss-util ##################### [ 42/502] Installing: sed ##################### [ 43/502] install-info: No such file or directory for /usr/share/info/sed.info.gz Installing: libblkid ##################### [ 44/502] Installing: tcp_wrappers-libs ##################### [ 45/502] Installing: xz-libs ##################### [ 46/502] Installing: db4 ##################### [ 47/502] Installing: libudev ##################### [ 48/502] Installing: expat ##################### [ 49/502] Installing: elfutils-libelf ##################### [ 50/502] Installing: gawk ##################### [ 51/502] Installing: libcap-ng ##################### [ 52/502] Installing: sqlite ##################### [ 53/502] Installing: e2fsprogs-libs ##################### [ 54/502] Installing: pcre ##################### [ 55/502] Installing: grep ##################### [ 56/502] install-info: No such file or directory for /usr/share/info/grep.info.gz Installing: boost-program-options ##################### [ 57/502] Installing: keyutils-libs ##################### [ 58/502] Installing: krb5-libs ##################### [ 59/502] Installing: libaio ##################### [ 60/502] Installing: libjpeg-turbo ##################### [ 61/502] Installing: cpio ##################### [ 62/502] Installing: libidn ##################### [ 63/502] install-info: No such file or directory for /usr/share/info/libidn.info.gz Installing: file-libs ##################### [ 64/502] Installing: libnl ##################### [ 65/502] Installing: sigar ##################### [ 66/502] Installing: xen-libs ##################### [ 67/502] Installing: xz ##################### [ 68/502] Installing: lua ##################### [ 69/502] Installing: bzip2 ##################### [ 70/502] Installing: findutils ##################### [ 71/502] Installing: augeas-libs ##################### [ 72/502] Installing: libpng ##################### [ 73/502] Installing: freetype ##################### [ 74/502] Installing: libpcap ##################### [ 75/502] Installing: libICE ##################### [ 76/502] Installing: libogg ##################### [ 77/502] Installing: gdbm ##################### [ 78/502] Installing: perl-Pod-Escapes ##################### [ 79/502] Installing: perl-Socket ##################### [ 80/502] Installing: perl-Scalar-List-Utils ##################### [ 81/502] Installing: perl-macros ##################### [ 82/502] Installing: perl-threads ##################### [ 83/502] Installing: perl-threads-shared ##################### [ 84/502] Installing: perl-Module-Pluggable ##################### [ 85/502] Installing: perl-PathTools ##################### [ 86/502] Installing: perl-libs ##################### [ 87/502] Installing: perl-Pod-Simple ##################### [ 88/502] Installing: perl ##################### [ 89/502] Installing: numactl ##################### [ 90/502] Installing: perl-LWP-MediaTypes ##################### [ 91/502] Installing: perl-Compress-Raw-Zlib ##################### [ 92/502] Installing: perl-URI ##################### [ 93/502] Installing: libSM ##################### [ 94/502] Installing: libtiff ##################### [ 95/502] Installing: libmount ##################### [ 96/502] Installing: vim-minimal ##################### [ 97/502] Installing: tar ##################### [ 98/502] Installing: libss ##################### [ 99/502] Installing: e2fsprogs ##################### [100/502] Installing: which ##################### [101/502] install-info: No such file or directory for /usr/share/info/which.info.gz Installing: boost-system ##################### [102/502] Installing: boost-filesystem ##################### [103/502] Installing: psmisc ##################### [104/502] Installing: libedit ##################### [105/502] Installing: ncurses ##################### [106/502] Installing: fuse-libs ##################### [107/502] Installing: yajl ##################### [108/502] Installing: dmidecode ##################### [109/502] Installing: libffi ##################### [110/502] Installing: gamin ##################### [111/502] Installing: pkgconfig ##################### [112/502] Installing: glib2 ##################### [113/502] Installing: shared-mime-info ##################### [114/502] Installing: dbus-glib ##################### [115/502] Installing: libtasn1 ##################### [116/502] Installing: lm_sensors-libs ##################### [117/502] Installing: bridge-utils ##################### [118/502] Installing: p11-kit ##################### [119/502] Installing: gnutls ##################### [120/502] Installing: slang ##################### [121/502] Installing: newt ##################### [122/502] Installing: libcroco ##################### [123/502] Installing: perl-Encode-Locale ##################### [124/502] Installing: file ##################### [125/502] Installing: jasper-libs ##################### [126/502] Installing: libgssglue ##################### [127/502] Installing: libtirpc ##################### [128/502] Installing: less ##################### [129/502] Installing: setools-libs ##################### [130/502] Installing: nss-softokn ##################### [131/502] Installing: db4-utils ##################### [132/502] Installing: nss-myhostname ##################### [133/502] Installing: avahi-libs ##################### [134/502] Installing: libunistring ##################### [135/502] Installing: diffutils ##################### [136/502] install-info: No such file or directory for /usr/share/info/diffutils.info Installing: libicu ##################### [137/502] Installing: boost-regex ##################### [138/502] Installing: boost-date-time ##################### [139/502] Installing: boost-thread ##################### [140/502] Installing: gmp ##################### [141/502] Installing: coreutils-libs ##################### [142/502] Installing: gzip ##################### [143/502] Installing: cracklib ##################### [144/502] Installing: cracklib-dicts ##################### [145/502] Installing: coreutils ##################### [146/502] Installing: pam ##################### [147/502] Installing: openssl ##################### [148/502] Installing: python-libs ##################### [149/502] Installing: python ##################### [150/502] Installing: module-init-tools ##################### [151/502] Installing: hwdata ##################### [152/502] Installing: libssh2 ##################### [153/502] Installing: net-snmp-libs ##################### [154/502] Installing: libpciaccess ##################### [155/502] Installing: dbus-python ##################### [156/502] Installing: libxml2-python ##################### [157/502] Installing: python-IPy ##################### [158/502] Installing: libselinux-python ##################### [159/502] Installing: fontconfig ##################### [160/502] Installing: python-qpid ##################### [161/502] Installing: newt-python ##################### [162/502] Installing: bind-libs-lite ##################### [163/502] Installing: binutils ##################### [164/502] Installing: logrotate ##################### [165/502] Installing: libconfig ##################### [166/502] Installing: libfontenc ##################### [167/502] Installing: libselinux-utils ##################### [168/502] Installing: checkpolicy ##################### [169/502] Installing: procps ##################### [170/502] /var/tmp/rpm-tmp.VB5oQJ: line 1: groupadd: command not found Installing: matahari-core #################### [171/502]warning: group qpidd does not exist - using root Installing: matahari-core ##################### [171/502] Installing: lzo ##################### [172/502] Installing: lzop ##################### [173/502] Installing: pciutils-libs ##################### [174/502] Installing: dosfstools ##################### [175/502] Installing: ntfs-3g ##################### [176/502] Installing: linux-atm-libs ##################### [177/502] Installing: ethtool ##################### [178/502] Installing: libdb ##################### [179/502] Installing: cyrus-sasl-lib ##################### [180/502] Installing: ustr ##################### [181/502] Installing: libsemanage ##################### [182/502] Installing: shadow-utils ##################### [183/502] Installing: libutempter ##################### [184/502] Installing: util-linux ##################### [185/502] Installing: libusb1 ##################### [186/502] Installing: usbredir ##################### [187/502] Installing: febootstrap-supermin-helper ##################### [188/502] Installing: libsemanage-python ##################### [189/502] Installing: cyrus-sasl-gssapi ##################### [190/502] Installing: cyrus-sasl-md5 ##################### [191/502] Installing: ntfsprogs ##################### [192/502] Installing: libXfont ##################### [193/502] Installing: xorg-x11-font-utils ##################### [194/502] Installing: ghostscript-fonts ##################### [195/502] Installing: authconfig ##################### [196/502] Installing: urw-fonts ##################### [197/502] Installing: sos ##################### [198/502] Installing: net-snmp-utils ##################### [199/502] Installing: pygobject2 ##################### [200/502] Installing: PyPAM ##################### [201/502] Installing: python-newt_syrup ##################### [202/502] Installing: setools-libs-python ##################### [203/502] Installing: pyxf86config ##################### [204/502] Installing: pexpect ##################### [205/502] Installing: python-suds ##################### [206/502] Installing: pyOpenSSL ##################### [207/502] Installing: audit-libs-python ##################### [208/502] Installing: cracklib-python ##################### [209/502] Installing: python-ethtool ##################### [210/502] Installing: boost-python ##################### [211/502] Installing: libevent ##################### [212/502] Installing: perl-Net-SSLeay ##################### [213/502] Installing: wget ##################### [214/502] install-info: No such file or directory for /usr/share/info/wget.info.gz Installing: openslp ##################### [215/502] Installing: tog-pegasus-libs ##################### [216/502] Installing: hfsplus-tools ##################### [217/502] Installing: fipscheck-lib ##################### [218/502] Installing: fipscheck ##################### [219/502] Installing: mysql-libs ##################### [220/502] Installing: bind-libs ##################### [221/502] Installing: bind-utils ##################### [222/502] Installing: krb5-workstation ##################### [223/502] install-info: No such file or directory for /usr/share/info/krb5-user.info Installing: alsa-lib ##################### [224/502] Installing: genisoimage ##################### [225/502] Installing: groff ##################### [226/502] install-info: No such file or directory for /usr/share/info/groff.info Installing: nss ##################### [227/502] Installing: nss-sysinit ##################### [228/502] Installing: openldap ##################### [229/502] Installing: libcurl ##################### [230/502] Installing: matahari-lib ##################### [231/502] Installing: libwsman1 ##################### [232/502] Installing: libuser ##################### [233/502] Installing: libuser-python ##################### [234/502] Installing: python-pycurl ##################### [235/502] Installing: dhcp-libs ##################### [236/502] Installing: dhcp-common ##################### [237/502] Installing: python-urlgrabber ##################### [238/502] Installing: passwd ##################### [239/502] Installing: usermode ##################### [240/502] Installing: curl ##################### [241/502] Installing: rpm-libs ##################### [242/502] Installing: rpm ##################### [243/502] Installing: net-snmp-agent-libs ##################### [244/502] Installing: libnfsidmap ##################### [245/502] Installing: sudo ##################### [246/502] Installing: hmaccalc ##################### [247/502] Installing: generic-logos ##################### [248/502] Installing: boost-wave ##################### [249/502] Installing: boost-graph ##################### [250/502] Installing: gettext-libs ##################### [251/502] Installing: cups-libs ##################### [252/502] Installing: gnutls-utils ##################### [253/502] Installing: nbd ##################### [254/502] Installing: libgudev1 ##################### [255/502] Installing: python-gudev ##################### [256/502] Installing: perl-WWW-RobotRules ##################### [257/502] Installing: perl-Net-Telnet ##################### [258/502] Installing: perl-HTML-Tagset ##################### [259/502] Installing: perl-HTML-Parser ##################### [260/502] Installing: perl-TimeDate ##################### [261/502] Installing: perl-HTTP-Date ##################### [262/502] Installing: perl-File-Listing ##################### [263/502] Installing: perl-hivex ##################### [264/502] Installing: hivex ##################### [265/502] Installing: perl-Compress-Raw-Bzip2 ##################### [266/502] Installing: perl-IO-Compress ##################### [267/502] Installing: perl-HTTP-Message ##################### [268/502] Installing: perl-HTTP-Negotiate ##################### [269/502] Installing: perl-HTTP-Cookies ##################### [270/502] Installing: perl-HTTP-Daemon ##################### [271/502] Installing: perl-Net-LibIDN ##################### [272/502] Installing: perl-IO-Socket-SSL ##################### [273/502] Installing: perl-Net-HTTP ##################### [274/502] Installing: perl-libwww-perl ##################### [275/502] Installing: icoutils ##################### [276/502] Installing: celt051 ##################### [277/502] Installing: libvorbis ##################### [278/502] Installing: flac ##################### [279/502] Installing: libsndfile ##################### [280/502] Installing: augeas ##################### [281/502] Installing: device-mapper-multipath-libs ##################### [282/502] Installing: kstart ##################### [283/502] Installing: zerofree ##################### [284/502] Installing: btrfs-progs ##################### [285/502] Installing: elfutils-libs ##################### [286/502] Installing: grubby ##################### [287/502] Installing: xfsprogs ##################### [288/502] Installing: libxslt ##################### [289/502] Installing: netcf-libs ##################### [290/502] Installing: libassuan ##################### [291/502] Installing: acl ##################### [292/502] Installing: pinentry ##################### [293/502] Installing: boost-iostreams ##################### [294/502] Installing: unzip ##################### [295/502] Installing: nilfs-utils ##################### [296/502] Installing: jfsutils ##################### [297/502] Installing: libgomp ##################### [298/502] Installing: gettext ##################### [299/502] install-info: No such file or directory for /usr/share/info/gettext.info.gz Installing: make ##################### [300/502] Installing: mtools ##################### [301/502] Installing: m4 ##################### [302/502] Installing: libcmpiutil ##################### [303/502] Installing: cryptopp ##################### [304/502] Installing: boost-chrono ##################### [305/502] Installing: boost-test ##################### [306/502] Installing: boost-random ##################### [307/502] Installing: boost-signals ##################### [308/502] Installing: boost-serialization ##################### [309/502] Installing: boost ##################### [310/502] Installing: attr ##################### [311/502] Installing: lsof ##################### [312/502] Installing: libpipeline ##################### [313/502] Installing: strace ##################### [314/502] Installing: dash ##################### [315/502] Installing: telnet ##################### [316/502] Installing: hexedit ##################### [317/502] Installing: tree ##################### [318/502] Installing: libunwind ##################### [319/502] Installing: gperftools-libs ##################### [320/502] Installing: pixman ##################### [321/502] Installing: spice-server ##################### [322/502] Installing: scrub ##################### [323/502] Installing: libsysfs ##################### [324/502] Installing: plymouth-core-libs ##################### [325/502] Installing: sg3_utils-libs ##################### [326/502] Installing: sg3_utils ##################### [327/502] Installing: libasyncns ##################### [328/502] Installing: sysvinit-tools ##################### [329/502] Installing: libbsd ##################### [330/502] Installing: nc ##################### [331/502] Installing: libdaemon ##################### [332/502] Installing: libXau ##################### [333/502] Installing: libxcb ##################### [334/502] Installing: libX11 ##################### [335/502] Installing: libXext ##################### [336/502] Installing: libXi ##################### [337/502] Installing: libXtst ##################### [338/502] Installing: pulseaudio-libs ##################### [339/502] Installing: libXt ##################### [340/502] Installing: ghostscript ##################### [341/502] Installing: SDL ##################### [342/502] Installing: libibverbs ##################### [343/502] Installing: mingetty ##################### [344/502] Installing: traceroute ##################### [345/502] Installing: reiserfs-utils ##################### [346/502] Installing: pth ##################### [347/502] Installing: gnupg2 ##################### [348/502] install-info: No such file or directory for /usr/share/info/gnupg.info Installing: rpm-build-libs ##################### [349/502] Installing: sgpio ##################### [350/502] Installing: hostname ##################### [351/502] Installing: device-mapper ##################### [352/502] Installing: device-mapper-libs ##################### [353/502] Installing: cryptsetup-luks-libs ##################### [354/502] Installing: iproute ##################### [355/502] Installing: udev ##################### [356/502] Installing: initscripts ##################### [357/502] Installing: systemd ##################### [358/502] Installing: systemd-units ##################### [359/502] Installing: systemd-sysv ##################### [360/502] Installing: iptables ##################### [361/502] Installing: dbus ##################### [362/502] Installing: net-tools ##################### [363/502] Installing: iputils ##################### [364/502] Installing: qpid-cpp-client ##################### [365/502] Installing: qpid-qmf ##################### [366/502] Installing: device-mapper-event-libs ##################### [367/502] Installing: iscsi-initiator-utils ##################### [368/502] Installing: policycoreutils ##################### [369/502] Installing: cyrus-sasl ##################### [370/502] Installing: libvirt-client ##################### [371/502] chkconfig version 1.3.59 - Copyright (C) 1997-2000 Red Hat, Inc. This may be freely redistributed under the terms of the GNU Public License. usage: chkconfig [--list] [--type ] [name] chkconfig --add chkconfig --del chkconfig --override chkconfig [--level ] [--type ] Installing: libvirt-python ##################### [372/502] Installing: ceph ##################### [373/502] Installing: qemu-img ##################### [374/502] Installing: qpid-cpp-server ##################### [375/502] Installing: device-mapper-event ##################### [376/502] Installing: qpid-cpp-client-ssl ##################### [377/502] Installing: rpcbind ##################### [378/502] Installing: nfs-utils ##################### [379/502] Installing: openssh ##################### [380/502] Installing: libcgroup ##################### [381/502] Installing: kpartx ##################### [382/502] Installing: parted ##################### [383/502] Installing: dmraid ##################### [384/502] Installing: dmraid-events ##################### [385/502] Installing: device-mapper-multipath ##################### [386/502] Installing: policycoreutils-python ##################### [387/502] Installing: openssh-clients ##################### [388/502] Installing: qpid-cpp-server-ssl ##################### [389/502] Installing: lvm2-libs ##################### [390/502] Installing: lvm2 ##################### [391/502] Installing: qemu-common ##################### [392/502] ln -s '/lib/systemd/system/ksm.service' '/etc/systemd/system/multi-user.target.wants/ksm.service' ln -s '/lib/systemd/system/ksmtuned.service' '/etc/systemd/system/multi-user.target.wants/ksmtuned.service' warning: %post(qemu-common-2:0.15.1-4.fc16.x86_64) scriptlet failed, exit status 1 Installing: python-virtinst ##################### [393/502] Installing: virt-manager-common ##################### [394/502] Installing: selinux-policy ##################### [395/502] Installing: selinux-policy-targeted ##################### [396/502] Installing: python-qpid-qmf ##################### [397/502] Installing: qpid-tools ##################### [398/502] Installing: ConsoleKit-libs ##################### [399/502] Installing: polkit ##################### [400/502] Installing: ConsoleKit ##################### [401/502] Installing: matahari-agent-lib ##################### [402/502] Installing: collectd ##################### [403/502] Installing: net-snmp ##################### [404/502] Installing: tog-pegasus ##################### [405/502] Installing: mdadm ##################### [406/502] Installing: rsyslog ##################### [407/502] Installing: cronie-anacron ##################### [408/502] Installing: cronie ##################### [409/502] Installing: crontabs ##################### [410/502] Installing: man-db ##################### [411/502] Installing: ipmitool ##################### [412/502] Installing: fence-agents ##################### [413/502] Installing: dnsmasq ##################### [414/502] Installing: ntpdate ##################### [415/502] Installing: ntp ##################### [416/502] Installing: dhclient ##################### [417/502] Installing: gfs2-utils ##################### [418/502] Installing: tuned ##################### [419/502] Installing: ebtables ##################### [420/502] Installing: glusterfs ##################### [421/502] Installing: glusterfs-fuse ##################### [422/502] Installing: radvd ##################### [423/502] Installing: libvirt ##################### [424/502] Installing: anyterm ##################### [425/502] Installing: os-prober ##################### [426/502] Installing: netxen-firmware ##################### [427/502] Installing: linux-firmware ##################### [428/502] Installing: cryptsetup-luks ##################### [429/502] Installing: netpbm ##################### [430/502] Installing: netpbm-progs ##################### [431/502] Installing: busybox ##################### [432/502] Installing: seabios-bin ##################### [433/502] Installing: qemu-system-x86 ##################### [434/502] Installing: qemu-kvm ##################### [435/502] Installing: kbd-misc ##################### [436/502] Installing: kbd ##################### [437/502] Installing: plymouth-scripts ##################### [438/502] Installing: dracut ##################### [439/502] Installing: kernel ##################### [440/502] Installing: libdrm ##################### [441/502] Installing: plymouth ##################### [442/502] Installing: vdsm ##################### [443/502] Installing: fuse ##################### [444/502] Installing: zfs-fuse ##################### [445/502] Installing: libguestfs ##################### [446/502] Installing: grub2 ##################### [447/502] install-info: No such file or directory for /usr/share/info/grub2.info.gz install-info: No such file or directory for /usr/share/info/grub2-dev.info.gz Installing: ovirt-node ##################### [448/502] Installing: python-libguestfs ##################### [449/502] Installing: libguestfs-tools-c ##################### [450/502] Installing: vdsm-reg ##################### [451/502] Installing: systemtap-runtime ##################### [452/502] Installing: dracut-network ##################### [453/502] Installing: kexec-tools ##################### [454/502] error reading information on service kdump: No such file or directory Installing: dracut-fips ##################### [455/502] Installing: libvirt-cim ##################### [456/502] Installing: matahari-host ##################### [457/502] Running in chroot, ignoring request. Redirecting to /bin/systemctl condrestart matahari-host.service Running in chroot, ignoring request. Installing: sysstat ##################### [458/502] Installing: collectd-virt ##################### [459/502] Installing: libvirt-qmf ##################### [460/502] Installing: matahari-network ##################### [461/502] Running in chroot, ignoring request. Redirecting to /bin/systemctl condrestart matahari-network.service Running in chroot, ignoring request. Installing: matahari-broker ##################### [462/502] Running in chroot, ignoring request. Redirecting to /bin/systemctl condrestart matahari-broker.service Running in chroot, ignoring request. Installing: virt-manager-tui ##################### [463/502] Installing: openssh-server ##################### [464/502] Installing: vhostmd ##################### [465/502] Installing: system-config-firewall-base ##################### [466/502] Installing: audit ##################### [467/502] Installing: acpid ##################### [468/502] Installing: sblim-sfcb ##################### [469/502] Installing: irqbalance ##################### [470/502] Installing: bfa-firmware ##################### [471/502] Installing: aic94xx-firmware ##################### [472/502] Installing: rpm-python ##################### [473/502] Installing: libmlx4 ##################### [474/502] Installing: sysfsutils ##################### [475/502] Installing: syslinux ##################### [476/502] Installing: python-hivex ##################### [477/502] Installing: system-config-keyboard-base ##################### [478/502] Installing: usbutils ##################### [479/502] Installing: tcpdump ##################### [480/502] Installing: pciutils ##################### [481/502] Installing: efibootmgr ##################### [482/502] Installing: qemu-kvm-tools ##################### [483/502] Installing: python-setuptools ##################### [484/502] Installing: grub-efi ##################### [485/502] Installing: gdb ##################### [486/502] Installing: setools-console ##################### [487/502] Installing: ltrace ##################### [488/502] Installing: isomd5sum ##################### [489/502] Installing: bc ##################### [490/502] Installing: patch ##################### [491/502] Installing: vdsm-cli ##################### [492/502] Installing: hdparm ##################### [493/502] Installing: eject ##################### [494/502] Installing: lsscsi ##################### [495/502] Installing: vconfig ##################### [496/502] Installing: ql2200-firmware ##################### [497/502] Installing: ql2500-firmware ##################### [498/502] Installing: ql2400-firmware ##################### [499/502] Installing: ql23xx-firmware ##################### [500/502] Installing: rootfiles ##################### [501/502] Installing: ql2100-firmware ##################### [502/502] 1426 blocks Removing password for user root. passwd: Success Note: Forwarding request to 'systemctl enable auditd.service'. Note: Forwarding request to 'systemctl enable ntpd.service'. ln -s '/lib/systemd/system/ntpd.service' '/etc/systemd/system/multi-user.target.wants/ntpd.service' Note: Forwarding request to 'systemctl enable ntpdate.service'. ln -s '/lib/systemd/system/ntpdate.service' '/etc/systemd/system/multi-user.target.wants/ntpdate.service' Note: Forwarding request to 'systemctl enable iptables.service'. Note: Forwarding request to 'systemctl enable rsyslog.service'. Note: Forwarding request to 'systemctl enable multipathd.service'. Note: Forwarding request to 'systemctl enable snmpd.service'. ln -s '/lib/systemd/system/snmpd.service' '/etc/systemd/system/multi-user.target.wants/snmpd.service' Note: Forwarding request to 'systemctl enable ovirt-early.service'. ln -s '/lib/systemd/system/ovirt-early.service' '/etc/systemd/system/multi-user.target.wants/ovirt-early.service' Note: Forwarding request to 'systemctl enable ovirt.service'. ln -s '/lib/systemd/system/ovirt.service' '/etc/systemd/system/multi-user.target.wants/ovirt.service' Note: Forwarding request to 'systemctl enable ovirt-post.service'. ln -s '/lib/systemd/system/ovirt-post.service' '/etc/systemd/system/multi-user.target.wants/ovirt-post.service' Note: Forwarding request to 'systemctl enable ovirt-cim.service'. ln -s '/lib/systemd/system/ovirt-cim.service' '/etc/systemd/system/multi-user.target.wants/ovirt-cim.service' Note: Forwarding request to 'systemctl enable collectd.service'. ln -s '/lib/systemd/system/collectd.service' '/etc/systemd/system/multi-user.target.wants/collectd.service' Note: Forwarding request to 'systemctl enable libvirt-qmf.service'. ln -s '/lib/systemd/system/libvirt-qmf.service' '/etc/systemd/system/multi-user.target.wants/libvirt-qmf.service' Note: Forwarding request to 'systemctl enable matahari-host.service'. ln -s '/lib/systemd/system/matahari-host.service' '/etc/systemd/system/multi-user.target.wants/matahari-host.service' Note: Forwarding request to 'systemctl enable libvirtd.service'. ln -s '/lib/systemd/system/libvirtd.service' '/etc/systemd/system/multi-user.target.wants/libvirtd.service' error reading information on service cgconfig: No such file or directory loop: can't delete device /dev/loop1: Device or resource busy cp: writing `/tmp/lorax.imgutils.y5Im6N/EFI/BOOT/BOOTx64.efi': No space left on device cp: failed to extend `/tmp/lorax.imgutils.y5Im6N/EFI/BOOT/BOOTx64.efi': No space left on device loop: can't delete device /dev/loop2: Device or resource busy Traceback (most recent call last): File "/usr/sbin/mkefiboot", line 105, in mkmacboot(opt.bootdir, opt.outfile, opt.label, opt.icon) File "/usr/sbin/mkefiboot", line 35, in mkmacboot mkhfsimg(None, outfile, label=label, graft=graft) File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line 292, in mkhfsimg mkfsargs=["-v", label], graft=graft) File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line 275, in mkfsimage do_grafts(graft, mnt, preserve) File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line 133, in do_grafts copytree(filename, join(dest, imgpath), preserve) File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line 118, in copytree check_call(cp + [".", os.path.abspath(dest)], preexec_fn=chdir) File "/usr/lib64/python2.7/subprocess.py", line 511, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['cp', '-a', '.', '/tmp/lorax.imgutils.y5Im6N/EFI/BOOT']' returned non-zero exit status 1 Starting Kickstart Post Creating shadow files Lock root account Locking password for user root. passwd: Success Saved 1 file(s) Saved 1 file(s) Saved 1 file(s) patching file sosreport.py patching file plugins/general.py Listing /usr/lib/python2.7/site-packages/sos ... Listing /usr/lib/python2.7/site-packages/sos/plugins ... Compiling /usr/lib/python2.7/site-packages/sos/plugins/general.py ... Compiling /usr/lib/python2.7/site-packages/sos/sosreport.py ... Saved 1 file(s) Saved 1 file(s) Configuring IPTables Listing /usr/share/virt-manager ... Listing /usr/share/virt-manager/virtManager ... Listing /usr/share/virt-manager/virtManagerTui ... Listing /usr/share/virt-manager/virtManagerTui/importblacklist ... Configuring SELinux Compiling targeted ovirt module /usr/bin/checkmodule: loading policy configuration from tmp/ovirt.tmp /usr/bin/checkmodule: policy configuration loaded /usr/bin/checkmodule: writing binary representation (version 14) to tmp/ovirt.mod Creating targeted ovirt.pp policy package rm tmp/ovirt.mod tmp/ovirt.mod.fc Attempting to install module 'ovirt.pp': Ok: return value of 0. Committing changes: Ok: transaction number 0. Fixing boot menu /sbin/ldconfig: relative path `0' used to build cache warning: %postun(dmraid-1.0.0.rc16-15.fc15.x86_64) scriptlet failed, exit status 1 /usr/share/info/dir: could not read (No such file or directory) and could not create (No such file or directory) Removing python source files Creating manifest....done /etc/selinux/targeted/contexts/files/file_contexts: line 3776 has invalid context system_u:object_r:ovirt_exec_t:s0 /etc/selinux/targeted/contexts/files/file_contexts: line 4000 has invalid context system_u:object_r:ovirt_exec_t:s0 *************** Error creating Live CD : fsck after resize returned an error (1)! umount: /home/minqf/ovirt-cache/node-creator-x86_64-tmp/imgcreate-G2OjOu/install_roo t/sys/fs/selinux/load: not found [sudo] password for minqf: ERROR: ISO build failed. make: *** [iso] Error 1 How can I fix it? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: create_iso.log Type: application/octet-stream Size: 46622 bytes Desc: not available URL: From fabiand at redhat.com Mon May 21 07:50:26 2012 From: fabiand at redhat.com (Fabian Deutsch) Date: Mon, 21 May 2012 09:50:26 +0200 Subject: [node-devel] Using yum in Node Message-ID: <1337586626.2575.3.camel@fdeutsch-laptop.local> Hey, yum landed in node quite recently - not in the official build, but in gerrit [0]. It's somewhat tricky to get it working, I added a small section to the Node troubleshooting wiki page [1] to give other a better start. Greetings fabian [0] http://gerrit.ovirt.org/#change,4522 [1] http://ovirt.org/wiki/Node_Troubleshooting#Using_yum -------------- 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 Mon May 21 12:56:27 2012 From: mburns at redhat.com (Mike Burns) Date: Mon, 21 May 2012 08:56:27 -0400 Subject: [node-devel] Using yum in Node In-Reply-To: <1337586626.2575.3.camel@fdeutsch-laptop.local> References: <1337586626.2575.3.camel@fdeutsch-laptop.local> Message-ID: <1337604987.24864.7.camel@beelzebub.mburnsfire.net> On Mon, 2012-05-21 at 09:50 +0200, Fabian Deutsch wrote: > Hey, > > yum landed in node quite recently - not in the official build, but in > gerrit [0]. > It's somewhat tricky to get it working, I added a small section to the > Node troubleshooting wiki page [1] to give other a better start. Just for clarity, this is being done to support plugins. It will only be supported offline when using the edit-node functionality. Mike > > Greetings > fabian > > [0] http://gerrit.ovirt.org/#change,4522 > [1] http://ovirt.org/wiki/Node_Troubleshooting#Using_yum > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From acathrow at redhat.com Mon May 21 13:06:45 2012 From: acathrow at redhat.com (Andrew Cathrow) Date: Mon, 21 May 2012 09:06:45 -0400 (EDT) Subject: [node-devel] Using yum in Node In-Reply-To: <1337604987.24864.7.camel@beelzebub.mburnsfire.net> Message-ID: ----- Original Message ----- > From: "Mike Burns" > To: "Fabian Deutsch" > Cc: node-devel at ovirt.org > Sent: Monday, May 21, 2012 8:56:27 AM > Subject: Re: [node-devel] Using yum in Node > > On Mon, 2012-05-21 at 09:50 +0200, Fabian Deutsch wrote: > > Hey, > > > > yum landed in node quite recently - not in the official build, but > > in > > gerrit [0]. > > It's somewhat tricky to get it working, I added a small section to > > the > > Node troubleshooting wiki page [1] to give other a better start. > > Just for clarity, this is being done to support plugins. It will > only > be supported offline when using the edit-node functionality. > Obviously the reason for this is not for users to have yum available for use on the node when it's deployed but it's going to cause confusion with users that they have utilities like yum and rpm and can't use them, or if they try to things fail in strange ways. If we don't want or support runtime use of rpm and yum then having them in the node and available to be called is asking for trouble. Having docs that explain why it failed and why they shouldn't be doing it isn't enough. > Mike > > > > > Greetings > > fabian > > > > [0] http://gerrit.ovirt.org/#change,4522 > > [1] http://ovirt.org/wiki/Node_Troubleshooting#Using_yum > > _______________________________________________ > > 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 Mon May 21 13:26:38 2012 From: mburns at redhat.com (Mike Burns) Date: Mon, 21 May 2012 09:26:38 -0400 Subject: [node-devel] Using yum in Node In-Reply-To: References: Message-ID: <1337606798.24864.12.camel@beelzebub.mburnsfire.net> On Mon, 2012-05-21 at 09:06 -0400, Andrew Cathrow wrote: > > ----- Original Message ----- > > From: "Mike Burns" > > To: "Fabian Deutsch" > > Cc: node-devel at ovirt.org > > Sent: Monday, May 21, 2012 8:56:27 AM > > Subject: Re: [node-devel] Using yum in Node > > > > On Mon, 2012-05-21 at 09:50 +0200, Fabian Deutsch wrote: > > > Hey, > > > > > > yum landed in node quite recently - not in the official build, but > > > in > > > gerrit [0]. > > > It's somewhat tricky to get it working, I added a small section to > > > the > > > Node troubleshooting wiki page [1] to give other a better start. > > > > Just for clarity, this is being done to support plugins. It will > > only > > be supported offline when using the edit-node functionality. > > > > Obviously the reason for this is not for users to have yum available for use on the node when it's deployed but it's going to cause confusion with users that they have utilities like yum and rpm and can't use them, or if they try to things fail in strange ways. > > If we don't want or support runtime use of rpm and yum then having them in the node and available to be called is asking for trouble. > Having docs that explain why it failed and why they shouldn't be doing it isn't enough. The plan to mitigate this issue is that the yum binary will be relocated to either a non-standard place that isn't in the path (/usr/libexec) or renamed to something else non-standard (ovirt-yum or something). The /usr/bin/yum executable will instead print a message/warning to the user that says the running yum in unsupported on a running host. The offline edit-node process will call the renamed or relocated yum script correctly. The only other options we have are to go down a path where we end up having to handle all the dependency solving ourselves rather than leverage something that already exists or have people provide fully functional and already resolved packages for installation. I don't see either of those as good options. Mike > > > > Mike > > > > > > > > Greetings > > > fabian > > > > > > [0] http://gerrit.ovirt.org/#change,4522 > > > [1] http://ovirt.org/wiki/Node_Troubleshooting#Using_yum > > > _______________________________________________ > > > 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 acathrow at redhat.com Mon May 21 13:30:37 2012 From: acathrow at redhat.com (Andrew Cathrow) Date: Mon, 21 May 2012 09:30:37 -0400 (EDT) Subject: [node-devel] Using yum in Node In-Reply-To: <1337606798.24864.12.camel@beelzebub.mburnsfire.net> Message-ID: <8edde00b-bb63-4a54-ab1f-3c96f6478cd9@zmail07.collab.prod.int.phx2.redhat.com> ----- Original Message ----- > From: "Mike Burns" > To: "Andrew Cathrow" > Cc: node-devel at ovirt.org > Sent: Monday, May 21, 2012 9:26:38 AM > Subject: Re: [node-devel] Using yum in Node > > On Mon, 2012-05-21 at 09:06 -0400, Andrew Cathrow wrote: > > > > ----- Original Message ----- > > > From: "Mike Burns" > > > To: "Fabian Deutsch" > > > Cc: node-devel at ovirt.org > > > Sent: Monday, May 21, 2012 8:56:27 AM > > > Subject: Re: [node-devel] Using yum in Node > > > > > > On Mon, 2012-05-21 at 09:50 +0200, Fabian Deutsch wrote: > > > > Hey, > > > > > > > > yum landed in node quite recently - not in the official build, > > > > but > > > > in > > > > gerrit [0]. > > > > It's somewhat tricky to get it working, I added a small section > > > > to > > > > the > > > > Node troubleshooting wiki page [1] to give other a better > > > > start. > > > > > > Just for clarity, this is being done to support plugins. It will > > > only > > > be supported offline when using the edit-node functionality. > > > > > > > Obviously the reason for this is not for users to have yum > > available for use on the node when it's deployed but it's going to > > cause confusion with users that they have utilities like yum and > > rpm and can't use them, or if they try to things fail in strange > > ways. > > > > If we don't want or support runtime use of rpm and yum then having > > them in the node and available to be called is asking for trouble. > > Having docs that explain why it failed and why they shouldn't be > > doing it isn't enough. > > The plan to mitigate this issue is that the yum binary will be > relocated > to either a non-standard place that isn't in the path (/usr/libexec) > or > renamed to something else non-standard (ovirt-yum or something). > The /usr/bin/yum executable will instead print a message/warning to > the > user that says the running yum in unsupported on a running host. The > offline edit-node process will call the renamed or relocated yum > script > correctly. Great. > > The only other options we have are to go down a path where we end up > having to handle all the dependency solving ourselves rather than > leverage something that already exists or have people provide fully > functional and already resolved packages for installation. I don't > see > either of those as good options. > > Mike > > > > > > > > Mike > > > > > > > > > > > Greetings > > > > fabian > > > > > > > > [0] http://gerrit.ovirt.org/#change,4522 > > > > [1] http://ovirt.org/wiki/Node_Troubleshooting#Using_yum > > > > _______________________________________________ > > > > 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 pmyers at redhat.com Mon May 21 14:29:37 2012 From: pmyers at redhat.com (Perry Myers) Date: Mon, 21 May 2012 10:29:37 -0400 Subject: [node-devel] Using yum in Node In-Reply-To: <8edde00b-bb63-4a54-ab1f-3c96f6478cd9@zmail07.collab.prod.int.phx2.redhat.com> References: <8edde00b-bb63-4a54-ab1f-3c96f6478cd9@zmail07.collab.prod.int.phx2.redhat.com> Message-ID: <4FBA5151.5060802@redhat.com> On 05/21/2012 09:30 AM, Andrew Cathrow wrote: > > > ----- Original Message ----- >> From: "Mike Burns" >> To: "Andrew Cathrow" >> Cc: node-devel at ovirt.org >> Sent: Monday, May 21, 2012 9:26:38 AM >> Subject: Re: [node-devel] Using yum in Node >> >> On Mon, 2012-05-21 at 09:06 -0400, Andrew Cathrow wrote: >>> >>> ----- Original Message ----- >>>> From: "Mike Burns" >>>> To: "Fabian Deutsch" >>>> Cc: node-devel at ovirt.org >>>> Sent: Monday, May 21, 2012 8:56:27 AM >>>> Subject: Re: [node-devel] Using yum in Node >>>> >>>> On Mon, 2012-05-21 at 09:50 +0200, Fabian Deutsch wrote: >>>>> Hey, >>>>> >>>>> yum landed in node quite recently - not in the official build, >>>>> but >>>>> in >>>>> gerrit [0]. >>>>> It's somewhat tricky to get it working, I added a small section >>>>> to >>>>> the >>>>> Node troubleshooting wiki page [1] to give other a better >>>>> start. >>>> >>>> Just for clarity, this is being done to support plugins. It will >>>> only >>>> be supported offline when using the edit-node functionality. >>>> >>> >>> Obviously the reason for this is not for users to have yum >>> available for use on the node when it's deployed but it's going to >>> cause confusion with users that they have utilities like yum and >>> rpm and can't use them, or if they try to things fail in strange >>> ways. >>> >>> If we don't want or support runtime use of rpm and yum then having >>> them in the node and available to be called is asking for trouble. >>> Having docs that explain why it failed and why they shouldn't be >>> doing it isn't enough. >> >> The plan to mitigate this issue is that the yum binary will be >> relocated >> to either a non-standard place that isn't in the path (/usr/libexec) >> or >> renamed to something else non-standard (ovirt-yum or something). >> The /usr/bin/yum executable will instead print a message/warning to >> the >> user that says the running yum in unsupported on a running host. The >> offline edit-node process will call the renamed or relocated yum >> script >> correctly. > > Great. We could also solve this (and many other issues around folks trying to do things in oVirt Node that should not be done) by making it harder to get a shell. Doing things like disabling root ssh access completely (which is presently only blocked by vdsm needing to use root ssh for registration) and making the admin shell harder to enter would further enforce the firmware like nature of oVirt Node Perry From mburns at redhat.com Mon May 21 14:43:37 2012 From: mburns at redhat.com (Mike Burns) Date: Mon, 21 May 2012 10:43:37 -0400 Subject: [node-devel] Using yum in Node In-Reply-To: <4FBA5151.5060802@redhat.com> References: <8edde00b-bb63-4a54-ab1f-3c96f6478cd9@zmail07.collab.prod.int.phx2.redhat.com> <4FBA5151.5060802@redhat.com> Message-ID: <1337611417.23619.0.camel@beelzebub.mburnsfire.net> On Mon, 2012-05-21 at 10:29 -0400, Perry Myers wrote: > On 05/21/2012 09:30 AM, Andrew Cathrow wrote: > > > > > > ----- Original Message ----- > >> From: "Mike Burns" > >> To: "Andrew Cathrow" > >> Cc: node-devel at ovirt.org > >> Sent: Monday, May 21, 2012 9:26:38 AM > >> Subject: Re: [node-devel] Using yum in Node > >> > >> On Mon, 2012-05-21 at 09:06 -0400, Andrew Cathrow wrote: > >>> > >>> ----- Original Message ----- > >>>> From: "Mike Burns" > >>>> To: "Fabian Deutsch" > >>>> Cc: node-devel at ovirt.org > >>>> Sent: Monday, May 21, 2012 8:56:27 AM > >>>> Subject: Re: [node-devel] Using yum in Node > >>>> > >>>> On Mon, 2012-05-21 at 09:50 +0200, Fabian Deutsch wrote: > >>>>> Hey, > >>>>> > >>>>> yum landed in node quite recently - not in the official build, > >>>>> but > >>>>> in > >>>>> gerrit [0]. > >>>>> It's somewhat tricky to get it working, I added a small section > >>>>> to > >>>>> the > >>>>> Node troubleshooting wiki page [1] to give other a better > >>>>> start. > >>>> > >>>> Just for clarity, this is being done to support plugins. It will > >>>> only > >>>> be supported offline when using the edit-node functionality. > >>>> > >>> > >>> Obviously the reason for this is not for users to have yum > >>> available for use on the node when it's deployed but it's going to > >>> cause confusion with users that they have utilities like yum and > >>> rpm and can't use them, or if they try to things fail in strange > >>> ways. > >>> > >>> If we don't want or support runtime use of rpm and yum then having > >>> them in the node and available to be called is asking for trouble. > >>> Having docs that explain why it failed and why they shouldn't be > >>> doing it isn't enough. > >> > >> The plan to mitigate this issue is that the yum binary will be > >> relocated > >> to either a non-standard place that isn't in the path (/usr/libexec) > >> or > >> renamed to something else non-standard (ovirt-yum or something). > >> The /usr/bin/yum executable will instead print a message/warning to > >> the > >> user that says the running yum in unsupported on a running host. The > >> offline edit-node process will call the renamed or relocated yum > >> script > >> correctly. > > > > Great. > > We could also solve this (and many other issues around folks trying to > do things in oVirt Node that should not be done) by making it harder to > get a shell. > > Doing things like disabling root ssh access completely (which is > presently only blocked by vdsm needing to use root ssh for registration) > and making the admin shell harder to enter would further enforce the > firmware like nature of oVirt Node Balancing this with the ability to debug issues when they come up is a tricky thing though. Perhaps a debug flag to enable/disable the ability to drop to a shell. Mike > > Perry > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From pmyers at redhat.com Mon May 21 15:01:08 2012 From: pmyers at redhat.com (Perry Myers) Date: Mon, 21 May 2012 11:01:08 -0400 Subject: [node-devel] Using yum in Node In-Reply-To: <1337611417.23619.0.camel@beelzebub.mburnsfire.net> References: <8edde00b-bb63-4a54-ab1f-3c96f6478cd9@zmail07.collab.prod.int.phx2.redhat.com> <4FBA5151.5060802@redhat.com> <1337611417.23619.0.camel@beelzebub.mburnsfire.net> Message-ID: <4FBA58B4.8080102@redhat.com> On 05/21/2012 10:43 AM, Mike Burns wrote: > On Mon, 2012-05-21 at 10:29 -0400, Perry Myers wrote: >> On 05/21/2012 09:30 AM, Andrew Cathrow wrote: >>> >>> >>> ----- Original Message ----- >>>> From: "Mike Burns" >>>> To: "Andrew Cathrow" >>>> Cc: node-devel at ovirt.org >>>> Sent: Monday, May 21, 2012 9:26:38 AM >>>> Subject: Re: [node-devel] Using yum in Node >>>> >>>> On Mon, 2012-05-21 at 09:06 -0400, Andrew Cathrow wrote: >>>>> >>>>> ----- Original Message ----- >>>>>> From: "Mike Burns" >>>>>> To: "Fabian Deutsch" >>>>>> Cc: node-devel at ovirt.org >>>>>> Sent: Monday, May 21, 2012 8:56:27 AM >>>>>> Subject: Re: [node-devel] Using yum in Node >>>>>> >>>>>> On Mon, 2012-05-21 at 09:50 +0200, Fabian Deutsch wrote: >>>>>>> Hey, >>>>>>> >>>>>>> yum landed in node quite recently - not in the official build, >>>>>>> but >>>>>>> in >>>>>>> gerrit [0]. >>>>>>> It's somewhat tricky to get it working, I added a small section >>>>>>> to >>>>>>> the >>>>>>> Node troubleshooting wiki page [1] to give other a better >>>>>>> start. >>>>>> >>>>>> Just for clarity, this is being done to support plugins. It will >>>>>> only >>>>>> be supported offline when using the edit-node functionality. >>>>>> >>>>> >>>>> Obviously the reason for this is not for users to have yum >>>>> available for use on the node when it's deployed but it's going to >>>>> cause confusion with users that they have utilities like yum and >>>>> rpm and can't use them, or if they try to things fail in strange >>>>> ways. >>>>> >>>>> If we don't want or support runtime use of rpm and yum then having >>>>> them in the node and available to be called is asking for trouble. >>>>> Having docs that explain why it failed and why they shouldn't be >>>>> doing it isn't enough. >>>> >>>> The plan to mitigate this issue is that the yum binary will be >>>> relocated >>>> to either a non-standard place that isn't in the path (/usr/libexec) >>>> or >>>> renamed to something else non-standard (ovirt-yum or something). >>>> The /usr/bin/yum executable will instead print a message/warning to >>>> the >>>> user that says the running yum in unsupported on a running host. The >>>> offline edit-node process will call the renamed or relocated yum >>>> script >>>> correctly. >>> >>> Great. >> >> We could also solve this (and many other issues around folks trying to >> do things in oVirt Node that should not be done) by making it harder to >> get a shell. >> >> Doing things like disabling root ssh access completely (which is >> presently only blocked by vdsm needing to use root ssh for registration) >> and making the admin shell harder to enter would further enforce the >> firmware like nature of oVirt Node > > Balancing this with the ability to debug issues when they come up is a > tricky thing though. Perhaps a debug flag to enable/disable the ability > to drop to a shell I was thinking more along the lines of drop to shell from Admin TUI user account drops to 'admin' user vs. 'root' user. And then we could have very selected subset of commands that will work via tightly controlled sudoers configuration vs. giving root access. From mburns at redhat.com Mon May 21 15:08:47 2012 From: mburns at redhat.com (Mike Burns) Date: Mon, 21 May 2012 11:08:47 -0400 Subject: [node-devel] Using yum in Node In-Reply-To: <4FBA58B4.8080102@redhat.com> References: <8edde00b-bb63-4a54-ab1f-3c96f6478cd9@zmail07.collab.prod.int.phx2.redhat.com> <4FBA5151.5060802@redhat.com> <1337611417.23619.0.camel@beelzebub.mburnsfire.net> <4FBA58B4.8080102@redhat.com> Message-ID: <1337612927.23619.5.camel@beelzebub.mburnsfire.net> On Mon, 2012-05-21 at 11:01 -0400, Perry Myers wrote: > On 05/21/2012 10:43 AM, Mike Burns wrote: > > On Mon, 2012-05-21 at 10:29 -0400, Perry Myers wrote: > >> On 05/21/2012 09:30 AM, Andrew Cathrow wrote: > >>> > >>> > >>> ----- Original Message ----- > >>>> From: "Mike Burns" > >>>> To: "Andrew Cathrow" > >>>> Cc: node-devel at ovirt.org > >>>> Sent: Monday, May 21, 2012 9:26:38 AM > >>>> Subject: Re: [node-devel] Using yum in Node > >>>> > >>>> On Mon, 2012-05-21 at 09:06 -0400, Andrew Cathrow wrote: > >>>>> > >>>>> ----- Original Message ----- > >>>>>> From: "Mike Burns" > >>>>>> To: "Fabian Deutsch" > >>>>>> Cc: node-devel at ovirt.org > >>>>>> Sent: Monday, May 21, 2012 8:56:27 AM > >>>>>> Subject: Re: [node-devel] Using yum in Node > >>>>>> > >>>>>> On Mon, 2012-05-21 at 09:50 +0200, Fabian Deutsch wrote: > >>>>>>> Hey, > >>>>>>> > >>>>>>> yum landed in node quite recently - not in the official build, > >>>>>>> but > >>>>>>> in > >>>>>>> gerrit [0]. > >>>>>>> It's somewhat tricky to get it working, I added a small section > >>>>>>> to > >>>>>>> the > >>>>>>> Node troubleshooting wiki page [1] to give other a better > >>>>>>> start. > >>>>>> > >>>>>> Just for clarity, this is being done to support plugins. It will > >>>>>> only > >>>>>> be supported offline when using the edit-node functionality. > >>>>>> > >>>>> > >>>>> Obviously the reason for this is not for users to have yum > >>>>> available for use on the node when it's deployed but it's going to > >>>>> cause confusion with users that they have utilities like yum and > >>>>> rpm and can't use them, or if they try to things fail in strange > >>>>> ways. > >>>>> > >>>>> If we don't want or support runtime use of rpm and yum then having > >>>>> them in the node and available to be called is asking for trouble. > >>>>> Having docs that explain why it failed and why they shouldn't be > >>>>> doing it isn't enough. > >>>> > >>>> The plan to mitigate this issue is that the yum binary will be > >>>> relocated > >>>> to either a non-standard place that isn't in the path (/usr/libexec) > >>>> or > >>>> renamed to something else non-standard (ovirt-yum or something). > >>>> The /usr/bin/yum executable will instead print a message/warning to > >>>> the > >>>> user that says the running yum in unsupported on a running host. The > >>>> offline edit-node process will call the renamed or relocated yum > >>>> script > >>>> correctly. > >>> > >>> Great. > >> > >> We could also solve this (and many other issues around folks trying to > >> do things in oVirt Node that should not be done) by making it harder to > >> get a shell. > >> > >> Doing things like disabling root ssh access completely (which is > >> presently only blocked by vdsm needing to use root ssh for registration) > >> and making the admin shell harder to enter would further enforce the > >> firmware like nature of oVirt Node > > > > Balancing this with the ability to debug issues when they come up is a > > tricky thing though. Perhaps a debug flag to enable/disable the ability > > to drop to a shell > > I was thinking more along the lines of drop to shell from Admin TUI user > account drops to 'admin' user vs. 'root' user. And then we could have > very selected subset of commands that will work via tightly controlled > sudoers configuration vs. giving root access. We'd probably want to get the TUI itself to run as admin then. It runs as root currently. I guess we could keep the TUI running as root, but spawn a shell as admin. Not something that will be done in the short term regardless, though. renaming/moving will have to suffice for now. Mike From mburns at redhat.com Tue May 22 13:40:47 2012 From: mburns at redhat.com (Mike Burns) Date: Tue, 22 May 2012 09:40:47 -0400 Subject: [node-devel] oVirt Node Weekly Sync Meeting Minutes -- 2012-05-22 Message-ID: <1337694047.23619.40.camel@beelzebub.mburnsfire.net> Minutes: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-22-13.01.html Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-22-13.01.txt Log: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-22-13.01.log.html ============================== #ovirt: ovirt node weekly sync ============================== Meeting started by mburns at 13:01:21 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-22-13.01.log.html . Meeting summary --------------- * agenda and roll call (mburns, 13:01:33) * Action Item Review (mburns, 13:03:22) * LINK: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-08-13.03.html (mburns, 13:03:24) * LINK: http://ovirt.org/wiki/Features/NetworkManager_Support (fabiand, 13:03:59) * LINK: http://ovirt.org/wiki/Features/NetworkManager_Support (mburns, 13:04:09) * ACTION: mburns and jboggs to review network manager feature page (mburns, 13:04:52) * mburns still hasn't reviewed/updated stateless feature page (mburns, 13:05:36) * ACTION: mburns to update stateless page by May 29 meeting (mburns, 13:05:55) * mburns review 2.4.0 bug list and removed things that definitely won't make it (mburns, 13:06:46) * Release Status (mburns, 13:07:13) * 2.4.0 scheduled for release 31-May (mburns, 13:07:27) * 8 bugs still in New/Assigned (mburns, 13:08:32) * ~25 patches still pending (mburns, 13:09:18) * ACTION: mburns jboggs fabiand to review pending patches (mburns, 13:10:22) * oVirt Project release scheduled for 2012-06-27 (mburns, 13:14:06) * oVirt Beta scheduled for 2012-05-31 (mburns, 13:14:20) * addtional ovirt-node builds needed during beta and for oVirt Project GA will be 2.4.x (mburns, 13:14:50) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=822705 (mburns, 13:16:47) * other topics (mburns, 13:19:55) Meeting ended at 13:27:04 UTC. Action Items ------------ * mburns and jboggs to review network manager feature page * mburns to update stateless page by May 29 meeting * mburns jboggs fabiand to review pending patches Action Items, by person ----------------------- * fabiand * mburns jboggs fabiand to review pending patches * jboggs * mburns and jboggs to review network manager feature page * mburns jboggs fabiand to review pending patches * mburns * mburns and jboggs to review network manager feature page * mburns to update stateless page by May 29 meeting * mburns jboggs fabiand to review pending patches * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mburns (65) * fabiand (32) * ovirtbot (6) * jboggs (4) * pmyers (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From mvanhorssen at vluchtelingenwerk.nl Thu May 24 15:15:14 2012 From: mvanhorssen at vluchtelingenwerk.nl (Michel van Horssen) Date: Thu, 24 May 2012 17:15:14 +0200 (CEST) Subject: [node-devel] Still not abel to migrate to node In-Reply-To: <1336564632.3397.8.camel@beelzebub.mburnsfire.net> Message-ID: <1cd33a18-07ea-41d7-83ea-a5f35bf7da3a@mailstore1.vluchtelingenwerk.nl> Mike I just found a bug that look a lot like my problem. So I'm going to give my input there and hope it get's solved. Glad to see I'm not the only one with this problem. Bug is => https://bugzilla.redhat.com/show_bug.cgi?id=810272 From mvanhorssen at vluchtelingenwerk.nl Fri May 25 12:44:19 2012 From: mvanhorssen at vluchtelingenwerk.nl (Michel van Horssen) Date: Fri, 25 May 2012 14:44:19 +0200 (CEST) Subject: [node-devel] Solution Re: Still not abel to migrate to node In-Reply-To: <1cd33a18-07ea-41d7-83ea-a5f35bf7da3a@mailstore1.vluchtelingenwerk.nl> Message-ID: Okay, Jacob Wyatt gave the solution. Make sure that in /etc/libvirt/libvirtd.conf the line with "listen_tls = 0" So listen_tls = 0 becomes # listen_tls = 0 Do this also in /config/etc/libvirt/libvirtd.conf this way you can safely reboot. Tested this and my 2 nodes happily migrated a VM between them. Michel From mvanhorssen at vluchtelingenwerk.nl Fri May 25 14:25:37 2012 From: mvanhorssen at vluchtelingenwerk.nl (Michel van Horssen) Date: Fri, 25 May 2012 16:25:37 +0200 (CEST) Subject: [node-devel] Seting the timezone on the node In-Reply-To: Message-ID: <7c75a3a8-773c-4391-9896-9007f25d6c0a@mailstore1.vluchtelingenwerk.nl> I'm really stomped on this one. The nodes only know about UTC timezone. My node points towards a time server in my network. Because the timezone is UTC the node is 2 hours behind the engine which is running with the CEST timezone. The bios/hardware time is correct, so the node time is 2 hours behind that as well. Question is how can I get the node in CEST mode? It's probably stupidly simple but please take my hand and guide me towards a better Ovirt-node future :) I'm so close now my migration problem is resolved :) Thnx, Michel From mburns at redhat.com Fri May 25 14:41:07 2012 From: mburns at redhat.com (Mike Burns) Date: Fri, 25 May 2012 10:41:07 -0400 Subject: [node-devel] Seting the timezone on the node In-Reply-To: <7c75a3a8-773c-4391-9896-9007f25d6c0a@mailstore1.vluchtelingenwerk.nl> References: <7c75a3a8-773c-4391-9896-9007f25d6c0a@mailstore1.vluchtelingenwerk.nl> Message-ID: <1337956867.3606.55.camel@beelzebub.mburnsfire.net> On Fri, 2012-05-25 at 16:25 +0200, Michel van Horssen wrote: > I'm really stomped on this one. > > The nodes only know about UTC timezone. My node points towards a time server in my network. > Because the timezone is UTC the node is 2 hours behind the engine which is running with the CEST timezone. > > The bios/hardware time is correct, so the node time is 2 hours behind that as well. > > Question is how can I get the node in CEST mode? > > It's probably stupidly simple but please take my hand and guide me towards a better Ovirt-node future :) > > I'm so close now my migration problem is resolved :) > At this time, ovirt-node doesn't have any way to set different time zones. IMO, this isn't a bug with ovirt-node though. IMO, migration *should* normalize the time to a consistent time zone regardless. If migration is breaking due to there being different time zones on engine and node, then that's a bug with engine/vdsm. Mike > Thnx, > > Michel > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From mvanhorssen at vluchtelingenwerk.nl Fri May 25 14:57:59 2012 From: mvanhorssen at vluchtelingenwerk.nl (Michel van Horssen) Date: Fri, 25 May 2012 16:57:59 +0200 (CEST) Subject: [node-devel] Seting the timezone on the node In-Reply-To: <1337956867.3606.55.camel@beelzebub.mburnsfire.net> Message-ID: <03fe60ba-8706-4e96-8df0-2e0bf2dd2f22@mailstore1.vluchtelingenwerk.nl> Hi Mike, > At this time, ovirt-node doesn't have any way to set different time > zones. IMO, this isn't a bug with ovirt-node though. IMO, migration > *should* normalize the time to a consistent time zone regardless. If > migration is breaking due to there being different time zones on > engine > and node, then that's a bug with engine/vdsm. Hmm, strange. You're correct, I did some test migrations earlier and when I migrated to one of the nodes the status was "?" The moment I changed to the correct time on the node the green triangle appeared in the web inteface. Now doing some migrations between nodes (with different times) all went well. Funny. My time paranoia is partly because of the other migration problem I had (tls related). It was suggested to look at time differences on the nodes and the VDSM. Now I found the real problem I thought I would tackle the time thing. But that doesn't seem to be a problem so I'll leave at that. > Mike Thnx Mike Michel From berrange at redhat.com Fri May 25 15:02:16 2012 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 25 May 2012 16:02:16 +0100 Subject: [node-devel] Seting the timezone on the node In-Reply-To: <03fe60ba-8706-4e96-8df0-2e0bf2dd2f22@mailstore1.vluchtelingenwerk.nl> References: <1337956867.3606.55.camel@beelzebub.mburnsfire.net> <03fe60ba-8706-4e96-8df0-2e0bf2dd2f22@mailstore1.vluchtelingenwerk.nl> Message-ID: <20120525150215.GK11895@redhat.com> On Fri, May 25, 2012 at 04:57:59PM +0200, Michel van Horssen wrote: > My time paranoia is partly because of the other migration problem > I had (tls related). It was suggested to look at time differences > on the nodes and the VDSM. Anything time related with migration, and/or TLS should be operating against UTC, regardless of what the OS timezone is set to. Basically the only thing timezone ought to affect is timestamps written into logfiles. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| From danken at redhat.com Sun May 27 20:03:35 2012 From: danken at redhat.com (Dan Kenigsberg) Date: Sun, 27 May 2012 23:03:35 +0300 Subject: [node-devel] [vdsm] Solution Re: Still not abel to migrate to node In-Reply-To: References: <1cd33a18-07ea-41d7-83ea-a5f35bf7da3a@mailstore1.vluchtelingenwerk.nl> Message-ID: <20120527200335.GA15729@redhat.com> On Fri, May 25, 2012 at 02:44:19PM +0200, Michel van Horssen wrote: > Okay, > > Jacob Wyatt gave the solution. Make sure that in /etc/libvirt/libvirtd.conf the line with "listen_tls = 0" > > So > > listen_tls = 0 > > becomes > > # listen_tls = 0 > > Do this also in /config/etc/libvirt/libvirtd.conf this way you can safely reboot. > > Tested this and my 2 nodes happily migrated a VM between them. > > Michel Michel, Thanks for your report and for following it to completion. The art of configuring another daemon is a fine one. Vdsm tries to touch libvirtd.conf as little as possible, so it does not set listen_tls=1, as this is the libvirt default. It assumes that if someone/something else changes the default, it knows what it is doing. Apparently this was not the case this time. I believe that Vdsm's minimalistic approach is the Right Thing to do, and about to close the Vdsm part of this bug. Regards, Dan. From mburns at redhat.com Wed May 30 14:49:21 2012 From: mburns at redhat.com (Mike Burns) Date: Wed, 30 May 2012 10:49:21 -0400 Subject: [node-devel] oVirt Node Weekly Meeting Minutes -- 2012-05-29 Message-ID: <1338389361.3802.5.camel@mburns-laptop.usersys.redhat.com> Minutes: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-29-13.00.html Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-29-13.00.txt Log: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-29-13.00.log.html ============================== #ovirt: oVirt Node Weekly Sync ============================== Meeting started by mburns at 13:00:17 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-29-13.00.log.html . Meeting summary --------------- * roll call (mburns, 13:01:20) * Action Item Review (mburns, 13:02:06) * LINK: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-22-13.01.html (mburns, 13:02:13) * ~25 patches outstanding (mburns, 13:04:29) * includes many patches that are new (mburns, 13:04:41) * ACTION: mburns fabiand jboggs to review patches (again) (mburns, 13:05:11) * ACTION: mburns and jboggs to review network manager feature page (mburns, 13:06:33) * LINK: http://ovirt.org/wiki/Features/NetworkManager_Support (mburns, 13:06:42) * LINK: http://ovirt.org/wiki/Node_Stateless (mburns, 13:07:22) * ACTION: mburns to file bugs for remaining stateless pieces targetted at 2.5.0 (mburns, 13:08:53) * ACTION: fabiand to add link to network manager bridge support on network manager feature page (mburns, 13:10:18) * Release Status (mburns, 13:10:42) * oVirt Feature freeze delays 1 week to June 7 (mburns, 13:10:59) * oVirt Node 2.4.0 will delay until then as well (mburns, 13:11:18) * 14 bugs still open, 5 new, 2 assigned, rest in POST or MODIFIED (mburns, 13:12:08) * LINK: http://goo.gl/i8G14 (mburns, 13:12:30) * ACTION: mburns to review 2.5.0 bug list, set target date to mid-july, defer things to 2.6.0 that aren't going to make it in. (mburns, 13:16:44) * AGREED: target 2.5.0 release for mid-July (mburns, 13:19:40) * other topics (mburns, 13:19:57) * mburns will be at LinuxCon Japan next week, so may or may not be on these meetings (mburns, 13:20:20) * -- seeing some errors from anaconda with installation (mburns, 13:22:42) * corrupt initscripts package (mburns, 13:22:49) * LINK: https://admin.fedoraproject.org/updates/FEDORA-2012-8440/util-linux-2.21.2-1.fc17 (mburns, 13:25:03) Meeting ended at 13:26:23 UTC. Action Items ------------ * mburns fabiand jboggs to review patches (again) * mburns and jboggs to review network manager feature page * mburns to file bugs for remaining stateless pieces targetted at 2.5.0 * fabiand to add link to network manager bridge support on network manager feature page * mburns to review 2.5.0 bug list, set target date to mid-july, defer things to 2.6.0 that aren't going to make it in. Action Items, by person ----------------------- * fabiand * mburns fabiand jboggs to review patches (again) * fabiand to add link to network manager bridge support on network manager feature page * jboggs * mburns fabiand jboggs to review patches (again) * mburns and jboggs to review network manager feature page * mburns * mburns fabiand jboggs to review patches (again) * mburns and jboggs to review network manager feature page * mburns to file bugs for remaining stateless pieces targetted at 2.5.0 * mburns to review 2.5.0 bug list, set target date to mid-july, defer things to 2.6.0 that aren't going to make it in. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mburns (72) * jboggs (8) * fabiand (6) * ovirtbot (4) * ewoud (1) * yzaslavs (1) * pmyers (1) * abaron (1) * ecohen (1) * bazulay (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot