Loopback devices do not persist

Bug #1929605 reported by Nicolas Bock
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Cinder Charm
In Progress

Bug Description

The loopback devices used for local files does not persist on the Cinder units. This leads to a failure in cinder-volume which is not noticed by the charm. After rebooting a cinder unit the following entries are logged in cinder-volume.log:

2021-05-25 18:32:35.329 2107 ERROR cinder.service [-] Manager for service cinder-volume juju-b7da65-dxc-15@LVM is reporting problems, not sending heartbeat. Service will appear "down".

Changed in charm-cinder:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-cinder (master)

Change abandoned by "James Page <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/charm-cinder/+/793056
Reason: This review is > 12 weeks without comment, and failed testing the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.