Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1678768

Summary: Start request repeated too quickly for libvirtd.service
Product: Red Hat OpenStack Reporter: Joe H. Rahme <jhakimra>
Component: openstack-tripleoAssignee: Lee Yarwood <lyarwood>
Status: CLOSED WONTFIX QA Contact: Arik Chernetsky <achernet>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 9.0 (Mitaka)CC: afazekas, aschultz, jhakimra, kchamart, mbooth, mburns
Target Milestone: ---Keywords: Triaged, ZStream
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: 2019-05-20 11:22:51 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:
Attachments:
Description Flags
sosreport -p openstack on the undercloud
none
Infrared logs none

Description Joe H. Rahme 2019-02-19 14:49:26 UTC
Created attachment 1536360 [details]
sosreport -p openstack on the undercloud

Description of problem:

Deployment with the Infrared Customized job keeps failing for RHOS9 at the update_image step.

From the IR logs I found:

2019-02-18 15:03:21.399 | TASK [restart libvirt service] *************************************************
2019-02-18 15:03:21.402 | task path: /home/rhos-ci/jenkins/workspace/OSPD-Customized-Deployment-virt/infrared/plugins/tripleo-undercloud/tasks/images/repos.yml:19
2019-02-18 15:03:21.405 | fatal: [undercloud-0]: FAILED! => {
2019-02-18 15:03:21.407 |     "changed": false
2019-02-18 15:03:21.410 | }
2019-02-18 15:03:21.412 | 
2019-02-18 15:03:21.415 | MSG:
2019-02-18 15:03:21.418 | 
2019-02-18 15:03:21.420 | Unable to start service libvirtd: Job for libvirtd.service failed because the control process exited with error code. See "systemctl status libvirtd.service" and "journalctl -xe" for details.


Looking at the systemd service on the undercloud-0:


[stack@undercloud-0 ~]$ sudo systemctl status libvirtd
● libvirtd.service - Virtualization daemon
   Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since Mon 2019-02-18 10:03:22 EST; 23h ago
     Docs: man:libvirtd(8)
           https://libvirt.org
  Process: 12106 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=3)
 Main PID: 12106 (code=exited, status=3)
 
Feb 18 10:03:22 undercloud-0.redhat.local systemd[1]: Failed to start Virtualization daemon.
Feb 18 10:03:22 undercloud-0.redhat.local systemd[1]: Unit libvirtd.service entered failed state.
Feb 18 10:03:22 undercloud-0.redhat.local systemd[1]: libvirtd.service failed.
Feb 18 10:03:22 undercloud-0.redhat.local systemd[1]: libvirtd.service holdoff time over, scheduling restart.
Feb 18 10:03:22 undercloud-0.redhat.local systemd[1]: Stopped Virtualization daemon.
Feb 18 10:03:22 undercloud-0.redhat.local systemd[1]: start request repeated too quickly for libvirtd.service
Feb 18 10:03:22 undercloud-0.redhat.local systemd[1]: Failed to start Virtualization daemon.
Feb 18 10:03:22 undercloud-0.redhat.local systemd[1]: Unit libvirtd.service entered failed state.
Feb 18 10:03:22 undercloud-0.redhat.local systemd[1]: libvirtd.service failed.


Version-Release number of selected component (if applicable):

puddle 9.0-RHEL-7 "version": "2019-02-04.1"

How reproducible:

Every time.

Steps to Reproduce:
1. Deploy OSP9 with the Customized job, like in here https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/OSPD-Customized-Deployment-virt/8907/parameters/
2.
3.

Actual results:

Job failure.

Expected results:

Job success.

Additional info:

I've uploaded both the infrared and the sosreport logs

Comment 1 Joe H. Rahme 2019-02-19 14:54:15 UTC
Created attachment 1536362 [details]
Infrared logs

Comment 3 Attila Fazekas 2019-02-19 15:46:41 UTC
The issue the latest libvirt is compiled with >=ceph 2.0, but your librbd is from ceph-1.3 which is incompatible.
You can either downgrade libvirt 4.5.0-10.el7  (instead of something like 4.5.0-10.el7_6.4) or
upgrading the librbd (osp9 tripleo/puppet cannot deploy with ceph 2.0 ATM).

Comment 6 Red Hat Bugzilla 2023-09-14 05:24:01 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days