IT17611: BLOCK STORAGE ATTACHMENT FAILED FOR PUREAPPLICATION PATTERN DEPLOYMENT

IBM PureApplication System Version 2.2.3.0

APAR status

• Closed as program error.

Error description

• The PureApplication Knowledge Center documents a limit of 256
  LUNs for each cloud group.  The system itself uses 2 of
  these LUNs, and every data store and attached Raw,
  Block or Block Shared volume also uses up a LUN. Pattern
  deployments that include attaching block storage will fail if
  the 256 limit has been reached.
  
  https://www.ibm.com/support/knowledgecenter/SSCR9A_2.2.1/doc/sys
  temconsole/t_addstoragevolume.html
  
  The maximum number of LUNs per cloud group is 256. If you exceed
  this limit, you can not increase the storage for the cloud group
  by adding data stores, but would instead need to increase the
  size of existing data stores.
  
  If this problem is encountered a storage attachment operation
  may never complete. For subsequent attachments in the same
  cloud group or on the same instance, the history section on the
  instance page may include this message:
  
  "The block storage was not attached to the virtual machine.
  Search for string \"Block storage attachment failed\" in the
  workload problem determination logs to get more details."
  
  The job logs in a management collection set may also include
  this message:
  
  CWZIP1987E An error occurred when
  contacting vCenter: java.lang.RuntimeException:
  com.ibm.purescale.utils.LockUnavailableException: timed
  out waiting for lock.
  

Local fix

• Look for any block storage volumes in the cloud group that can
  be deleted or detached from instances to reduce the number of
  attached storage volumes in the cloud group to less than the 256
  limit.  You might need assistance from IBM Support to
  clear held locks and allow subsequent block storage attachments
  to succeed.
  

Problem summary

• There was a problem in the code checking for the storage SCSI
  ID limitation. The code has also been updated to throw a more
  detailed error when there is a problem obtaining a SCSI ID.
  

Problem conclusion

• A code fix is being provided in PureApplication System and
  BlueMix Local System version 2.2.3.0.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  PAPP SYS 8382 I

• Fixed component ID

  5725G3200

Applicable component levels

• R223 PSY

     UP