When we fail to manage a volume, we use cinder list to view the volume list, or use cinder show to view the volume details, We can see that the volume state is error.
But when we filter the list of volumes by specifying the status as error,We found that there were no manage failed volumes in the screening results.
I think this will confuse the user,user may not care whether the state of the volume is error or error_managing,We only distinguish the error_managing state when deleting volumes and handling quotas. So i think error_managing should be included when querying volumes with an error status.
When we fail to manage a volume, we use cinder list to view the volume list, or use cinder show to view the volume details, We can see that the volume state is error.
But when we filter the list of volumes by specifying the status as error,We found that there were no manage failed volumes in the screening results.
This is because the state of the volumes in which the manage failed is error_managing in the database, and in /github. com/openstack/ cinder/ blob/master/ cinder/ api/v2/ views/volumes. py@62, that is why cinder lit or cinder show
https:/
tell us the state of manage failed volume is error, but not error_managing.
I think this will confuse the user,user may not care whether the state of the volume is error or error_managing,We only distinguish the error_managing state when deleting volumes and handling quotas. So i think error_managing should be included when querying volumes with an error status.