Bug 1566818
Summary: | Cannot trigger ValueError(_("cpuset can only contain numeric, ',', '^', or '-' characters")) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Xiaodai Wang <xiaodwan> |
Component: | virt-manager | Assignee: | Pavel Hrdina <phrdina> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.5 | CC: | juzhou, mxie, mzhan, tzheng |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | virt-manager-1.5.0-2.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-06 13:07:59 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Xiaodai Wang
2018-04-13 03:51:49 UTC
Upstream commit: commit 5b2774b27aa84850de7c1328fb6d9d3682db7003 Author: Pavel Hrdina <phrdina> Date: Tue May 22 13:56:23 2018 +0200 numatune: fix validate_cpuset regexp There is a better fix in upstream that removes the validation completely as it is also done by libvirt: commit 39a7cbbad750656a7d89694c3b0341a5ae98d346 Author: Cole Robinson <crobinso> Date: Mon Jun 4 14:30:26 2018 -0400 domain.numatune: Drop cpuset validation I can reproduce this issue with package: virt-manager-1.4.3-3.el7.noarch Then try to verify this bug with new build: virt-manager-1.5.0-3.el7.noarch virt-install-1.5.0-3.el7.noarch libvirt-4.5.0-16.el7.x86_64 qemu-kvm-rhev-2.12.0-27.el7.x86_64 libvirt-python-4.5.0-1.el7.x86_64 Steps: 1.Check that the correct error report can be triggered: 1.1 virt-install --name test1 --memory 1024 --disk /var/lib/libvirt/images/aaa.qcow2 --import --vcpus vcpus=1,cpuset="1@2" ERROR invalid argument: Failed to parse bitmap '1@2' Result:The correct error report has been triggered successfully. I move this bug from ON_QA to VERIFIED based on above testing. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2232 |