VNX: volume cannot attach with os-brick failing connecting device

Bug #1882541 reported by Ryan Liang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
In Progress
Undecided
Ryan Liang

Bug Description

Below logs are repeating in the nova compute log.
    Searching for a device in session 2 and hctl ('4', '0', '0', 101) yield: None

This causes nova node cannot connect the volume as a block device, the VM cannot boot up because the volume cannot be attached to nova node and other related issues.

No error logs in the cinder volume log, but you can see this messages:
    Mar 23 02:13:32 vnxvm1 cinder-volume[27333]: INFO storops.vnx.resource.sg [None req-9f5f1115-5f0c-4f69-afab-f03c1e76a76c tempest-VolumeRetypeWithMigrationTest-934831485 None] ALU(alu=29) is already attached, found in the cache

Tags: dellemc vnx
Revision history for this message
Ryan Liang (ryan-liang) wrote :

The root cause is described in the storops issue: https://github.com/emc-openstack/storops/issues/305

Changed in cinder:
assignee: nobody → Ryan Liang (ryan-liang)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.opendev.org/734093

Changed in cinder:
status: New → In Progress
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.