Bug 1533105
Summary: | provide non-recursive output replacement for query-named-block-nodes | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | Peter Krempa <pkrempa> | ||||
Component: | qemu-kvm | Assignee: | Virtualization Maintenance <virt-maint> | ||||
qemu-kvm sub component: | Storage | QA Contact: | leidwang <leidwang> | ||||
Status: | CLOSED CURRENTRELEASE | Docs Contact: | |||||
Severity: | medium | ||||||
Priority: | medium | CC: | chayang, coli, fjin, juzhang, kanderso, kchamart, knoel, mtessun, ngu, rbalakri, virt-maint | ||||
Version: | --- | Keywords: | FutureFeature, Triaged | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2021-02-15 07:34:31 UTC | Type: | Feature Request | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1793036 | ||||||
Attachments: |
|
Description
Peter Krempa
2018-01-10 13:20:38 UTC
Created attachment 1392702 [details]
To illustrate, for a disk image chain with depth 4, see the attached output of `query-named-block-nodes`
QEMU has been recently split into sub-components and as a one-time operation to avoid breakage of tools, we are setting the QEMU sub-component of this BZ to "General". Please review and change the sub-component if necessary the next time you review this BZ. Thanks It looks like (I haven't tested it yet) this is fixed by this commit from Peter Krempa: https://git.qemu.org/?p=qemu.git;a=commit;h=facda5443f — qapi: Allow getting flat output from 'query-named-block-nodes' After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. According to https://bugzilla.redhat.com/show_bug.cgi?id=1793036#c6,set this bz to CURRENTRELEASE.Thanks. |