libvirt tries to read /etc/sasl/libvirt.conf not /etc/sasl2/libvirt.conf despite docs
Bug #546745 reported by
Craig Ringer
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Debian) |
New
|
Unknown
|
|||
libvirt (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Description: Ubuntu 9.10
Release: 9.10
Codename: karmic
libvirtd (libvirt) 0.7.0
/etc/libvirt/
# - sasl: use SASL infrastructure. The actual auth scheme is then
# controlled from /etc/sasl2/
# socket only GSSAPI & DIGEST-MD5 mechanisms will be used.
# For non-TCP or TLS sockets, any scheme is allowed.
#
yet strace'ing libvirtd startup reveals that it's actually looking for /etc/sasl/
Once /etc/sasl2 is symlinked to /etc/sasl, it still fails, but that's another bug.
Changed in libvirt (Ubuntu): | |
importance: | Undecided → Low |
Changed in libvirt (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | added: patch |
Changed in libvirt (Debian): | |
status: | Unknown → New |
Changed in libvirt (Ubuntu): | |
assignee: | Jamie Strandboge (jdstrand) → nobody |
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Lucid Lynx. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http:// www.ubuntu. com/testing/ . Thanks again and we appreciate your help.