Skip to content
Snippets Groups Projects
  1. Jun 24, 2019
  2. May 21, 2019
  3. Nov 04, 2018
  4. Nov 02, 2018
  5. Oct 30, 2018
  6. Oct 29, 2018
  7. Oct 23, 2018
  8. Oct 22, 2018
  9. Oct 19, 2018
  10. Oct 18, 2018
  11. Oct 17, 2018
  12. Oct 15, 2018
  13. Oct 12, 2018
    • Peter Krempa's avatar
      util: storage: Properly parse URIs with missing trailing slash · 6e7e965d
      Peter Krempa authored
      
      The URI parser used by libvirt does not populate uri->path if the
      trailing slash is missing. The code virStorageSourceParseBackingURI
      would then not populate src->path.
      
      As only NBD network disks are allowed to have the 'name' field in the
      XML defining the disk source omitted we'd generate an invalid XML which
      we'd not parse again.
      
      Fix it by populating src->path with an empty string if the uri is
      lacking slash.
      
      As pointed out above NBD is special in this case since we actually allow
      it being NULL. The URI path is used as export name. Since an empty
      export does not make sense the new approach clears the src->path if the
      trailing slash is present but nothing else.
      
      Add test cases now to cover all the various cases for NBD and non-NBD
      uris as there was to time only 1 test abusing the quirk witout slash for
      NBD and all other URIs contained the slash or in case of NBD also the
      export name.
      
      Signed-off-by: default avatarPeter Krempa <pkrempa@redhat.com>
      6e7e965d
    • Peter Krempa's avatar
      util: storage: Rename '@path' argument of virStorageSourceParseBackingURI · 4471f770
      Peter Krempa authored
      
      The name is misleading. Change it to 'uristr' so that 'path' can be
      reused in the proper context later.
      
      Signed-off-by: default avatarPeter Krempa <pkrempa@redhat.com>
      4471f770
    • Eric Blake's avatar
      virsh: Fix regression with duplicated error messages · 35966308
      Eric Blake authored
      Commit 4f4c3b13 (v3.3) fixed an issue where performing cleanup of
      libvirt objects could sometimes lose error messages, by adding code
      to copy the libvirt error into last_error prior to cleanup paths.
      However, it caused a regression: on other paths, some errors are now
      printed twice, if libvirt still remembers in its thread-local
      storage that an error was set even after virsh cleared last_error.
      For example:
      
      $ virsh -c test:///default
      
       snapshot-delete test blah
      error: Domain snapshot not found: no domain snapshot with matching name 'blah'
      error: Domain snapshot not found: no domain snapshot with matching name 'blah'
      
      Fix things by telling libvirt to discard any thread-local errors at
      the same time virsh prints an error message (whether or not the libvirt
      error is the same as what is stored in last_error).
      
      Update the virsh-undefine testsuite (partially reverting portions of
      commit b620bdee, by removing -q, to more easily pinpoint which commands
      are causing which messages), now that there is only one error message
      instead of two.
      
      Signed-off-by: Eric Blake's avatarEric Blake <eblake@redhat.com>
      Reviewed-by: default avatarMichal Privoznik <mprivozn@redhat.com>
      35966308
    • Olaf Hering's avatar
      rpc: reproducible genprotocol output · 297ed93a
      Olaf Hering authored and Michal Privoznik's avatar Michal Privoznik committed
      
      If the same source gets built twice ('build same source on different
      hosts at different times') the resulting files may differ.
      Fix this by sorting the hash keys before usage.
      
      Signed-off-by: default avatarOlaf Hering <olaf@aepfle.de>
      297ed93a
  14. Oct 11, 2018
  15. Oct 10, 2018
    • Michal Privoznik's avatar
      virfile: Rework virFileIsSharedFixFUSE · 1dbf6222
      Michal Privoznik authored
      
      There are couple of things wrong with the current implementation.
      The first one is that in the first loop the code tries to build a
      list of fuse.glusterfs mount points. Well, since the strings are
      allocated in a temporary buffer and are not duplicated this
      results in wrong decision made later in the code.
      
      The second problem is that the code does not take into account
      subtree mounts. For instance, if there's a fuse.gluster mounted
      at /some/path and another FS mounted at /some/path/subdir the
      code would not recognize this subdir mount.
      
      Reported-by: default avatarHan Han <hhan@redhat.com>
      Signed-off-by: default avatarMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: default avatarJiri Denemark <jdenemar@redhat.com>
      1dbf6222
Loading