|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [libvirt test] 97688: regressions - FAIL
flight 97688 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/97688/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-libvirt 6 xen-boot fail REGR. vs. 97638 Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-xsm 14 guest-saverestore fail never pass test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-armhf-armhf-libvirt-qcow2 11 migrate-support-check fail never pass test-armhf-armhf-libvirt-qcow2 13 guest-saverestore fail never pass test-armhf-armhf-libvirt-raw 13 guest-saverestore fail never pass test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass version targeted for testing: libvirt 8ee6a99e7c2b31e7f3cdeabf59e211854da26f5d baseline version: libvirt c62e9d4199afb0e6cff1b6818330b115417addc1 Last test of basis 97638 2016-07-19 04:22:58 Z 1 days Testing same since 97688 2016-07-20 04:21:45 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Cédric Bosdonnat <cbosdonnat@xxxxxxxx> Erik Skultety <eskultet@xxxxxxxxxx> John Ferlan <jferlan@xxxxxxxxxx> Julio Faracco <jcfaracco@xxxxxxxxx> jobs: build-amd64-xsm pass build-armhf-xsm pass build-i386-xsm pass build-amd64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-libvirt-xsm pass test-armhf-armhf-libvirt-xsm fail test-amd64-i386-libvirt-xsm pass test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt fail test-amd64-i386-libvirt pass test-amd64-amd64-libvirt-pair pass test-amd64-i386-libvirt-pair pass test-armhf-armhf-libvirt-qcow2 fail test-armhf-armhf-libvirt-raw fail test-amd64-amd64-libvirt-vhd pass ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit 8ee6a99e7c2b31e7f3cdeabf59e211854da26f5d Author: Cédric Bosdonnat <cbosdonnat@xxxxxxxx> Date: Tue Jul 19 16:23:25 2016 +0200 lxc: errors after the handshake won't be reported Any error happening after the hand shake in the lxc controller will not result in a failure as errors are checked during the handshake. Move the handshake after the last possible error. commit cedd2ab28262db62976b351dbf2a0f8d9f88ca9e Author: Cédric Bosdonnat <cbosdonnat@xxxxxxxx> Date: Mon Jan 18 11:22:32 2016 +0100 virt-aa-helper: better write denials handling Better fix replacing c726af2d: introducing an 'R' permission to add read rule, but no explicit deny write rule. commit da86c6c22674ccc147224afa2740e33d8cbdbf22 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Thu Jun 2 16:28:28 2016 -0400 qemu: Add luks support for domain disk Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1301021 Generate the luks command line using the AES secret key to encrypt the luks secret. A luks secret object will be in addition to a an AES secret. For hotplug, check if the encinfo exists and if so, add the AES secret for the passphrase for the secret object used to decrypt the device. Modify/augment the fakeSecret* in qemuxml2argvtest in order to handle find a uuid or a volume usage with a specific path prefix in the XML (corresponds to the already generated XML tests). Add error message when the 'usageID' is not 'mycluster_myname'. Commit id '1d632c39' altered the error message generation to rely on the errors from the secret_driver (or it's faked replacement). Add the .args output for adding the LUKS disk to the domain Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit b7b3a51e8ab7c95b7ffab6b8d727338d71c37c55 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Fri Jun 24 15:31:57 2016 -0400 qemu: Alter the qemuDomainGetSecretAESAlias to add new arg Soon we will be adding luks encryption support. Since a volume could require both a luks secret and a secret to give to the server to use of the device, alter the alias generation to create a slightly different alias so that we don't have two objects with the same alias. Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit fceeeda2115bcb86b992c4add38704a886c099c8 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Wed Jun 22 07:07:49 2016 -0400 qemu: Add secinfo for hotplug virtio disk Commit id 'a1344f70a' added AES secret processing for RBD when starting up a guest. As such, when the hotplug code calls qemuDomainSecretDiskPrepare an AES secret could be added to the disk about to be hotplugged. If an AES secret was added, then the hotplug code would need to generate the secret object because qemuBuildDriveStr would add the "password-secret=" to the returned 'driveStr' rather than the base64 encoded password. Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit 5e46d7d6b693c1e3c9197c182302ac7125a856d9 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Thu Jun 2 11:33:47 2016 -0400 storage: Add support to create a luks volume Partially resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1301021 If the volume xml was looking to create a luks volume take the necessary steps in order to make that happen. The processing will be: 1. create a temporary file (virStorageBackendCreateQemuImgSecretPath) 1a. use the storage driver state dir path that uses the pool and volume name as a base. 2. create a secret object (virStorageBackendCreateQemuImgSecretObject) 2a. use an alias combinding the volume name and "_luks0" 2b. add the file to the object 3. create/add luks options to the commandline (virQEMUBuildLuksOpts) 3a. at the very least a "key-secret=%s" using the secret object alias 3b. if found in the XML the various "cipher" and "ivgen" options Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit bd93ba64fdb899c2d581ab7506542f9663d21ffb Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Mon Jul 18 14:37:38 2016 -0400 vsh: Properly initialize res The 'res' variable was only being initialized to NULL in the if (!state) path; however, that path never used res and evenutally res is assigned one of two results based on a pair of if then else if conditions. If for some reason neither of those paths was taken and the (!state) path wasn't taken, then 'res' would be indeterminate. Found by Coverity, probably a false positive based on code paths, but better safe than sorry for the future. Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit 7ca6cd7def2fbbd4308842cf4222fde7891d2987 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Mon Jul 18 14:30:59 2016 -0400 conf: Need to check for glisten before accessing When formatting the graphics data for TYPE_SPICE, check if the glisten is NULL before blindly referencing Found by Coverity Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit 5ddaa7ef2d8fd78b95f4d6595f972c6462eaafd3 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Mon Jul 18 14:25:43 2016 -0400 tests: Need to check return of virGetLastError Cannot assume virGetLastError returns non-NULL value - modify the code to fetch err and check if err && err->code Found by Coverity Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit dfb18b0afbb040a496ddce1f224176a97f8a5667 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Mon Jul 18 14:07:42 2016 -0400 tools: Fix comparison in virLoginShellGetShellArgv Commit id '740e4d70' altered the logic to fetch the sysconf values and added a new virConfGetValueStringList which returns -1 on failure, 0 if missing, and 1 if the value was present. However, the caller only checked !shargv which caught Coverity's attention since the following VIR_ALLOC_N(*shargv, 2) would be a NULL ptr deref Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit fee696b6e8f932c7160bc09c8c1d23383b87138a Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Mon Jul 18 13:58:52 2016 -0400 util: Fix incorrect VIR_FREE in virConfGetValueStringList Since we VIR_ALLOC_N to *values, the VIR_FREE should be done likewise Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit a8962f705d5b7973e322b81c38e46eb542cb1ad4 Author: Erik Skultety <eskultet@xxxxxxxxxx> Date: Mon Jul 18 10:45:17 2016 +0200 virt-admin: Output srv-threadpool-info data as unsigned int rather than signed Internally, all the data are represented as unsigned int, it is also documented in the header file that users should use our exported constants that also indicate that the data should be unsigned int. However, when polling for the current server threadpool's configuration, virt-admin uses an incorrect formatting parameter '%d' for printf. Instead, virt-admin should use formatting parameter '%u'. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1356769 Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx> commit 8215aab0036e65da47a2646f85749e9f5ea5d252 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Fri Jul 15 07:02:05 2016 -0400 qemu: Move and rename qemuBufferEscapeComma Move to virqemu and rename to virQEMUBuildBufferEscapeComma. This can then be shared by the storage driver when it builds the command line for qemuimg commit 99026fd0ad4fb962cc1c95c9a310ee7af79788ae Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Fri Jul 15 07:27:48 2016 -0400 qemu: Alter error path cleanup for qemuDomainAttachMemory A recent adjustment to qemuDomainAttachRNGDevice to properly cleanup the props object after a qemuMonitorAddObject also would affect this code. Alter the cleanup to be similar to RNG changes. commit 47208776be883ae8e55ea95a7673b47fe112c51f Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Thu Jul 14 18:13:50 2016 -0400 qemu: Alter error path cleanup for qemuDomainAttachRNGDevice Based on recent review comment - rather than have a spate of goto failxxxx, change to a boolean based model. Ensures that the original error can be preserved and cleanup is a bit more orderly if more objects are added. commit 05bc30d2bba8e7074e5bd1888c082edb567e07d0 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Thu Jul 14 17:55:05 2016 -0400 qemu: Alter error path cleanup for qemuDomainAttachChrDevice Based on recent review comment - rather than have a spate of goto failxxxx, change to a boolean based model. Ensures that the original error can be preserved and cleanup is a bit more orderly if more objects are added. commit c3b5f22dec05389a8a164761976d4aa64d4c399f Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Thu Jul 14 17:47:13 2016 -0400 qemu: Alter error path cleanup for qemuDomainAttachSCSIDisk Based on recent review comment - rather than have a spate of goto failxxxx, change to a boolean based model. Ensures that the original error can be preserved and cleanup is a bit more orderly if more objects are added. commit a7f84cb1ee037c2ea6c803450eb692d8030b4227 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Thu Jul 14 17:28:53 2016 -0400 qemu: Alter error path cleanup for qemuDomainAttachVirtioDiskDevice Based on recent review comment - rather than have a spate of goto failxxxx, change to a boolean based model. Ensures that the original error can be preserved and cleanup is a bit more orderly if more objects are added. commit 6fe2eb2458b5e4b84f5aede6d3fdf3ae47c0cd02 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Thu Jul 14 17:15:10 2016 -0400 qemu: Alter error path cleanup for qemuDomainAttachHostSCSIDevice Based on recent review comment - rather than have a spate of goto failxxxx, change to a boolean based model. Ensures that the original error can be preserved and cleanup is a bit more orderly if more objects are added. commit 28e191a96cf18dc241f4c3a4224bdf1f20aa1bdf Author: Erik Skultety <eskultet@xxxxxxxxxx> Date: Tue Jul 19 09:27:32 2016 +0200 fs: Fix '<' comparison of value produced by logical not '!' Commit da665fbd introduced the following condition to virLXCProcessEnsureRootFS and openvzReadFSConf: if (!(<some_var> = virDomainFSDefNew()) < 0) which broke the build on fedora with GCC 5.3.1: "logical not is only applied to the left hand side of comparison". Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx> commit fc624d86eab0018c1b4c7a80236a86301ebda9e1 Author: Julio Faracco <jcfaracco@xxxxxxxxx> Date: Mon Jul 18 22:09:20 2016 -0300 security: compilation error due to wrong parameter for vah_add_path(). The commit da665fbd introduced virStorageSourcePtr inside the structure _virDomainFSDef. This is causing an error when libvirt is being compiled. make[3]: Entering directory `/media/julio/8d65c59c-6ade-4740-9cdc-38016a4cb8ae /home/julio/Desktop/virt/libvirt/src' CC security/virt_aa_helper-virt-aa-helper.o security/virt-aa-helper.c: In function 'get_files': security/virt-aa-helper.c:1087:13: error: passing argument 2 of 'vah_add_path' from incompatible pointer type [-Werror] if (vah_add_path(&buf, fs->src, "rw", true) != 0) ^ security/virt-aa-helper.c:732:1: note: expected 'const char *' but argument is of type 'virStorageSourcePtr' vah_add_path(virBufferPtr buf, const char *path, const char *perms, bool recursive) ^ cc1: all warnings being treated as errors Adding the attribute "path" from virStorageSourcePtr fixes this issue. Signed-off-by: Julio Faracco <jcfaracco@xxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |