Displaying 6 results from an estimated 6 matches for "create_v2v_directori".
Did you mean:
create_v2v_directory
2023 Jun 29
1
[v2v PATCH v2 2/3] lib/utils: make "chown_for_libvirt_rhbz_1045069" fail hard
Currently "chown_for_libvirt_rhbz_1045069" is best effort; if it fails, we
suppress the exception (we log it in verbose mode only, even).
That's not proved helpful: it almost certainly leads to later errors, but
those errors are less clear than the original (suppressed) exception.
Namely, the user sees something like
> Failed to connect to '/tmp/v2v.sKlulY/in0':
2023 Jun 29
1
[v2v PATCH v2 2/3] lib/utils: make "chown_for_libvirt_rhbz_1045069" fail hard
On Thu, Jun 29, 2023 at 02:34:42PM +0200, Laszlo Ersek wrote:
> Currently "chown_for_libvirt_rhbz_1045069" is best effort; if it fails, we
> suppress the exception (we log it in verbose mode only, even).
>
> That's not proved helpful: it almost certainly leads to later errors, but
> those errors are less clear than the original (suppressed) exception.
> Namely, the
2023 Jun 29
1
[v2v PATCH v2 2/3] lib/utils: make "chown_for_libvirt_rhbz_1045069" fail hard
On 6/29/23 14:54, Richard W.M. Jones wrote:
> On Thu, Jun 29, 2023 at 02:34:42PM +0200, Laszlo Ersek wrote:
>> Currently "chown_for_libvirt_rhbz_1045069" is best effort; if it fails, we
>> suppress the exception (we log it in verbose mode only, even).
>>
>> That's not proved helpful: it almost certainly leads to later errors, but
>> those errors are
2023 Jun 29
1
[v2v PATCH v2 2/3] lib/utils: make "chown_for_libvirt_rhbz_1045069" fail hard
On Thu, Jun 29, 2023 at 05:39:34PM +0200, Laszlo Ersek wrote:
> On 6/29/23 14:54, Richard W.M. Jones wrote:
> > On Thu, Jun 29, 2023 at 02:34:42PM +0200, Laszlo Ersek wrote:
> >> Currently "chown_for_libvirt_rhbz_1045069" is best effort; if it fails, we
> >> suppress the exception (we log it in verbose mode only, even).
> >>
> >> That's
2023 Jun 29
1
[v2v PATCH v2 2/3] lib/utils: make "chown_for_libvirt_rhbz_1045069" fail hard
On 6/29/23 17:48, Richard W.M. Jones wrote:
> On Thu, Jun 29, 2023 at 05:39:34PM +0200, Laszlo Ersek wrote:
>> On 6/29/23 14:54, Richard W.M. Jones wrote:
>>> On Thu, Jun 29, 2023 at 02:34:42PM +0200, Laszlo Ersek wrote:
>>>> Currently "chown_for_libvirt_rhbz_1045069" is best effort; if it fails, we
>>>> suppress the exception (we log it in
2023 Jun 29
3
[v2v PATCH v2 0/3] improve UX when running as root and we can't chown
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2182024
v1 was here:
<https://listman.redhat.com/archives/libguestfs/2023-June/031910.html>.
Make any "chown_for_libvirt_rhbz_1045069" failure a hard one; that way
the user gets to see more direct and more uniform error messages (namely
that we couldn't connect to libvirt).
Document those connection problems, and a simple