Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Libvirt should reject domain name starting with '.', because file name starting with '.' is invisible in linux, the domain will disappear after restarting libvirtd.
Version-Release number of selected component:
libvirt-1.3.4-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
0.
# /usr/bin/virsh define /tmp/aaa.xml
Domain .aaa defined from /tmp/aaa.xml
1.
# /usr/bin/virsh list --all
Id Name State
----------------------------------------------------
- .aaa shut off
2.
# ls /etc/libvirt/qemu/.aaa.xml
/etc/libvirt/qemu/.aaa.xml
3.
# systemctl restart libvirtd
# /usr/bin/virsh list --all
Id Name State
----------------------------------------------------
Actual results:
As step3, domain disappeared after restarting libvirtd
Expected results:
Libvirt reject object name starting with '.'.
Additional info:
The issue also exists with network/pool name
Pushed upstream as:
commit 5217fe3db439e3dd66e2d657d2c0bebe0443ed22
Author: Ján Tomko <jtomko>
CommitDate: 2016-06-23 21:58:38 +0200
Allow configs to start with a dot
This fixes the disappearance of domains and networks starting with a
dot.
https://bugzilla.redhat.com/show_bug.cgi?id=1333248
git describe: v1.3.5-413-g5217fe3
I can reproduce this.
verify with build:
libvirt-2.0.0-1.el7.x86_64
step:
1. define a guest which name staring with a dot
# virsh define q35.xml
Domain .q35 defined from q35.xml
# virsh list --all
Id Name State
----------------------------------------------------
3 rhel7 running
- .q35 shut off
# systemctl restart libvirtd
[root@intel-e5530-8-1 ~]# virsh list --all
Id Name State
----------------------------------------------------
3 rhel7 running
- .q35 shut off
test pool:
#virsh pool-define pool.xml
Pool .test defined from pool.xml
# systemctl restart libvirtd
# virsh pool-list --all
Name State Autostart
-------------------------------------------
.test active no
default active yes
test network:
# virsh net-define net.xml
Network ..test defined from net.xml
# virsh net-list --all
Name State Autostart Persistent
----------------------------------------------------------
..test inactive no yes
default active yes yes
# systemctl restart libvirtd
# virsh net-list --all
Name State Autostart Persistent
----------------------------------------------------------
..test inactive no yes
default active yes yes
worked as expect, move to verified.
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://rhn.redhat.com/errata/RHSA-2016-2577.html