Bug 1614302
Summary: | qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Yanan Fu <yfu> |
Component: | qemu-kvm-rhev | Assignee: | Marc-Andre Lureau <marcandre.lureau> |
Status: | CLOSED ERRATA | QA Contact: | Yanan Fu <yfu> |
Severity: | low | Docs Contact: | |
Priority: | high | ||
Version: | 7.6 | CC: | chayang, jinzhao, juzhang, virt-maint, yfu |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-rhev-2.12.0-20.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-22 09:18:48 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1649160, 1651787 |
Description
Yanan Fu
2018-08-09 10:57:11 UTC
This issue doesn't exist on RHEL7.5. Test version: qemu: qemu-kvm-rhev-2.10.0-21.el7.x86_64 kernel: kernel-3.10.0-862.el7.x86_64 So, add keywords "Regression". Fix included in qemu-kvm-rhev-2.12.0-20.el7 ============Reproduce========== qemu-kvm: qemu-kvm-rhev-2.12.0-19.el7.x86_64 # /usr/libexec/qemu-kvm # tailf /var/log/messages .... Mar 5 22:11:19 hp-dl388g9-02 kvm: 1 guest now active Mar 5 22:11:19 hp-dl388g9-02 qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory ============ verification ========== qemu-kvm: qemu-kvm-rhev-2.12.0-24.el7 same step, no error in /var/log/message. # /usr/libexec/qemu-kvm # tailf /var/log/messages Mar 5 22:20:07 hp-dl388g9-02 kvm: 1 guest now active Mar 5 22:20:08 hp-dl388g9-02 kvm: 0 guests now active Mar 5 22:20:09 hp-dl388g9-02 kvm: 1 guest now active Mar 5 22:20:10 hp-dl388g9-02 kvm: 0 guests now active Move to VERIFIED accordingly. 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/RHSA-2019:2553 |