From: pevogam <plamen@pevogam.com>
To: qemu-devel@nongnu.org
Subject: [Bug 1859989] [NEW] qemu-img has broken output with large snapshot names
Date: Thu, 16 Jan 2020 13:59:26 -0000 [thread overview]
Message-ID: <157918316689.4864.12553262908100217782.malonedeb@wampee.canonical.com> (raw)
Public bug reported:
On Qemu 4.1.1 the output of snalshots breaks if the chosen state name is
too long:
```
# qemu-img snapshot -l /mnt/local/some_image.qcow2
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK
1 online_provider_with_dhcp747 MiB 2020-01-15 12:05:01 00:00:45.873
```
Prior to 4.1.1 this used to work with extra tabs for the VM SIZE values.
The collision is also disabling us from using a regex on top of this
input to detect the snapshot.
** Affects: qemu
Importance: Undecided
Status: New
** Summary changed:
- qemu-img has broken input on large snapshot name
+ qemu-img has broken output on large snapshot name
** Summary changed:
- qemu-img has broken output on large snapshot name
+ qemu-img has broken output with large snapshot names
** Description changed:
- On Qemu 4.1.1 the output of snalshots breaks if the chosen state name is
+ On Qemu 4.1.1 the output of snapshots breaks if the chosen state name is
too long:
# qemu-img snapshot -l /mnt/local/some_image.qcow2
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK
1 online_provider_with_dhcp747 MiB 2020-01-15 12:05:01 00:00:45.873
Prior to 4.1.1 this used to work with extra tabs for the VM SIZE values.
The collision is also disabling us from using a regex on top of this
input to detect the snapshot.
** Description changed:
On Qemu 4.1.1 the output of snapshots breaks if the chosen state name is
too long:
# qemu-img snapshot -l /mnt/local/some_image.qcow2
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK
1 online_provider_with_dhcp747 MiB 2020-01-15 12:05:01 00:00:45.873
- Prior to 4.1.1 this used to work with extra tabs for the VM SIZE values.
- The collision is also disabling us from using a regex on top of this
- input to detect the snapshot.
+ Prior to 4.1.1, this used to work with extra tabs for the VM SIZE
+ values. The collision is also disabling us from using a regex on top of
+ this input to detect the snapshot unless we forbid numbers in the
+ snapshot name.
** Description changed:
- On Qemu 4.1.1 the output of snapshots breaks if the chosen state name is
+ On Qemu 4.1.1 the output of snalshots breaks if the chosen state name is
too long:
+ ```
# qemu-img snapshot -l /mnt/local/some_image.qcow2
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK
1 online_provider_with_dhcp747 MiB 2020-01-15 12:05:01 00:00:45.873
+ ```
- Prior to 4.1.1, this used to work with extra tabs for the VM SIZE
- values. The collision is also disabling us from using a regex on top of
- this input to detect the snapshot unless we forbid numbers in the
- snapshot name.
+ Prior to 4.1.1 this used to work with extra tabs for the VM SIZE values.
+ The collision is also disabling us from using a regex on top of this
+ input to detect the snapshot.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1859989
Title:
qemu-img has broken output with large snapshot names
Status in QEMU:
New
Bug description:
On Qemu 4.1.1 the output of snalshots breaks if the chosen state name
is too long:
```
# qemu-img snapshot -l /mnt/local/some_image.qcow2
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK
1 online_provider_with_dhcp747 MiB 2020-01-15 12:05:01 00:00:45.873
```
Prior to 4.1.1 this used to work with extra tabs for the VM SIZE
values. The collision is also disabling us from using a regex on top
of this input to detect the snapshot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1859989/+subscriptions
next reply other threads:[~2020-01-16 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 13:59 pevogam [this message]
2020-01-16 18:49 ` [Bug 1859989] Re: qemu-img has broken output with large snapshot names pevogam
2020-01-17 9:54 ` Max Reitz
2020-01-17 10:13 ` Max Reitz
2020-01-17 10:42 ` pevogam
2020-01-17 11:08 ` Max Reitz
2020-03-10 9:12 ` Laurent Vivier
2020-04-30 13:42 ` Laurent Vivier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=157918316689.4864.12553262908100217782.malonedeb@wampee.canonical.com \
--to=plamen@pevogam.com \
--cc=1859989@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.