Iteration over ansible device for disk_utilisation maas check include sr0 device

Bug #1416880 reported by Bjoern
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Invalid
Medium
Unassigned
Juno
Invalid
Medium
Unassigned

Bug Description

The new iteration over all SCSI devices does include now sr0 for disk_utilisation maas check and that check fails since we have no media mounted on this device. SR0 need to be excluded from this device list, otherwise the alarms will fail.

no longer affects: openstack-ansible/next
Revision history for this message
Bernardo Salinas (bernardo-salinas55) wrote :

Hey @Bjoern Teipel what branch did you see this on? what version of the rpc-maas plugins were you using? Any more information you can provide on this would be great for beginning to troubleshoot.

Revision history for this message
Bjoern (bjoern-t) wrote :

The disk_utilisation (please US-ify in the name (z not s)) was run with 9.0.5. Later we switched to 10.1.2 but did not reinstall those checks, only the openstack ones

no longer affects: openstack-ansible/trunk
Revision history for this message
Kevin Carter (kevin-carter) wrote :

moving to rpc-extras as it pertains to rackspace monitoring as a service.

Changed in openstack-ansible:
status: New → Incomplete
status: Incomplete → Invalid
Revision history for this message
Bjoern (bjoern-t) wrote :

Moved to rpcextras issues #39

Changed in openstack-ansible:
milestone: next → none
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.