cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nik Martin (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-251) If one primary storage is put into maintenance mode, entire cloud goes down. CS 3.02
Date Wed, 03 Oct 2012 21:59:07 GMT


Nik Martin commented on CLOUDSTACK-251:

I have all the logs and have a cloud in a lab in the same configuration if any testing or
supporting logs are needed. I also have the logs from the failure this bug is in reference
> If one primary storage is put into maintenance mode, entire cloud goes down. CS 3.02
> ------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-251
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Storage Controller
>         Environment: Cloudstack 3.02 on Centos, Xenserevr 6.2 Hypervisors
>            Reporter: Nik Martin
>            Priority: Critical
>              Labels: storage
> I have two SANs in a cluster, both are Primary storage.  One is HD based,and one is SSD
based.  I use storage tags "HD" and "SSD" respectively.  The HD based SAN is a single 20TB
volume, with 1 iSCSI target, and 1 LUN.  The SSD SAN is two 5TB volumes, each with 1 target,
and 1 LUN each, in an Active-Active configuration.  The SSD SAN suffered from a mis-configuration
issue, so we had to put it into maintenance mode in a hurry, and shut it down.  I fully expected
the Volumes and VMs provisioned on the SSD SAN to be unavailable.  The problem is Cloudstack
continued to try to access Volume id 204, which is Target0 on the SSD san.  It shut every
VM down, and put all Hypervisors into Alert state, and went into a loop trying to connect
to a volume that is in maintenance mode.  This creates a very bad situation for me and my
customers. My entire cloud was offline until we could re-synchronize the Active-Actibve volumes
on the SSD SAN and bring it back online

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message