yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1581367] [NEW] Changed SAN iscsi IP addresses in connection_info can prevent VM startup

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: yuyafei <yu.yafei@xxxxxxxxxx>
Date: Fri, 13 May 2016 08:20:07 -0000
Reply-to: Bug 1581367 <1581367@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

The iscsi IP addresses of SAN are stored in nova's block-device-mapping
table after connecting volume and are never re-validated down the line.
Changing the iscsi IP adresses of SAN will prevent the instance from
booting as the stale connection info will enter the instance's XML. We
should check weather the  iscsi IP addresses of SAN are changed before
startup VM, or we need to a way to restore those VMs whose iscsi IP
addresses of SAN are changed.

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

- The iscsi IP addresses of SAN are stored in nova's block-device-mapping table 
- after connecting volume and are never re-validated down the line. Changing the 
- iscsi IP adresses of SAN will prevent the instance from booting as the stale
- connection info will enter the instance's XML. We should check weather the 
- iscsi IP addresses of SAN are changed before startup VM, or we need to a way to
- restore those VMs whose iscsi IP addresses of SAN are changed.
+ The iscsi IP addresses of SAN are stored in nova's block-device-mapping
+ table after connecting volume and are never re-validated down the line.
+ Changing the iscsi IP adresses of SAN will prevent the instance from
+ booting as the stale connection info will enter the instance's XML. We
+ should check weather the  iscsi IP addresses of SAN are changed before
+ startup VM, or we need to a way to restore those VMs whose iscsi IP
+ addresses of SAN are changed.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1581367

Title:
  Changed SAN iscsi IP addresses in connection_info can prevent VM
  startup

Status in OpenStack Compute (nova):
  New

Bug description:
  The iscsi IP addresses of SAN are stored in nova's block-device-
  mapping table after connecting volume and are never re-validated down
  the line. Changing the iscsi IP adresses of SAN will prevent the
  instance from booting as the stale connection info will enter the
  instance's XML. We should check weather the  iscsi IP addresses of SAN
  are changed before startup VM, or we need to a way to restore those
  VMs whose iscsi IP addresses of SAN are changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1581367/+subscriptions