Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2119213.1
Update Date:2018-05-30
Keywords:
Solution Type  Problem Resolution Sure

Solution  2119213.1 :   Oracle ZFS Storage Appliance: Renumbering of LUN IDs with the Openstack Cinder Driver  

Related Items 
    

  • Sun ZFS Storage 7420
    •  
  • Oracle ZFS Storage ZS3-2
    •  
  • Oracle ZFS Storage ZS4-4
    •  
  • Solaris Operating System
    •  
  • Oracle ZFS Storage ZS3-4
    •  
  • Sun ZFS Storage 7120
    •  
  • Sun ZFS Storage 7320
    •  
  • Oracle ZFS Storage Appliance Racked System ZS4-4
    •  
  • Oracle ZFS Storage ZS3-BA
    •  
Related Categories 
    

  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
    •  






In this Document


Symptoms


Cause


Solution


References

Created from <SR 3-11661620951>


Applies to:  

Sun ZFS Storage 7320 - Version All Versions and later
Sun ZFS Storage 7420 - Version All Versions and later
Oracle ZFS Storage ZS3-2 - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
Sun ZFS Storage 7120 - Version All Versions and later
7000 Appliance OS (Fishworks)



Symptoms


A LUN ID which is inserted into the (Cinder) mysql DB by OpenStack and which is put (by OpenStack) into the Zone configuration files differs - after a reboot of the entire OpenStack Environment - from the LUN ID offered by the ZFS-SA (it was created by OpenStack as well).


The mysql DB (Cinder) and the Zone-XML have still the original values, but the LUN in the ZFS_SA has got a new one.


In the ZS3 Audit-Log one can see that "Cinder" is Setting (a change) the assigned_number of the LUN to '-1'.


    

  • OS Solaris 11.2 sru 10 with openstack Juno
    • 

  • ZS3 Firmware 2013.06.05.4.2.1-1.1
    • 



 


The reboot of the OpenStack issues commands which assign the LUNs to an Initiator Group they already belonged before.


This causes the LUN to get a new ID assigned - leading to all kind of issues on the client side and for the applications/databases.


As the LUNs get new IDs assigned, the LUNs are not correctly assigned, while the configuration of OpenStack has not been changed for the remaining LUNs.


Steps to reproduce


    

  1. Create LUNs with IDs 1 to 10 and add them to an initiator group.
    2. 

  2. Have everything configured in OpenStack and Database
    3. 

  3. Remove some of the LUNs from the appliance and configuration to create gaps
    4. 

  4. Boot the complete OpenStack on the Solaris Client
    5. 



 


 


Cause


It seems that a command sent from OpenStack client to ZFS-SA causes the ZFS-SA to renumber the LUNs.


 




Bug 22159315 - deleting a lun causes lun renumbering on the ZFS appliance
Bug 22158523 - Can't boot zone as iscsi lun has changed




 


Solution


Long term solution is to update Solaris to Oracle Solaris 11.3.5.6.0 or later.


 


 


 


***Checked for relevance on 30-MAY-2018***


References
 <BUG:22158523> - CAN'T BOOT ZONE AS ISCSI LUN HAS CHANGED
 <BUG:22159315> - RESTART CINDER SERVICE TRIGGERS LUN ID RENUMBERING ON ZFSSA



Attachments

This solution has no attachment


















       

Copyright © 2018 Oracle, Inc.  All rights reserved.

 Feedback