IT44690: WHEN USING AWS VIRTUAL HOST STYLE URLS, CLOUD CONTAINER OBJECTS CAN BECOME INACCESSIBLE AFTER UPGRADING TO 8.1.18 SERVER.

8.1.22.000-IBM-SPSRV-WindowsX64
8.1.22.000-IBM-SPSRV-Linuxx86_64
8.1.22.000-IBM-SPSRV-Linuxs390x
8.1.22.000-IBM-SPSRV-Linuxppc64le
8.1.22.000-IBM-SPSRV-AIX

APAR status

• Closed as program error.

Error description

• In the dsmffdc.log the following error will be seen:
  
  [ FFDC_GENERAL_SERVER_ERROR ]: [466](jvm.c:1906)(PROCESS: 21,
  JOB: 258) com.tivoli.dsm.cloud.api.ProviderS3Retry
  handleException
  com.amazonaws.services.s3.model.AmazonS3Exception The specified
  key does not exist. (Service: Amazon S3; Status Code: 404; Error
  Code: NoSuchKey; Request ID: Q0YXXXXXXQVVDQW7; S3 Extended
  Request ID:
  jSmHYsFIDI6xxxxxxxxxxxxSPWzTyNT+fl3MxxxxxxxWvzZEcg==; Proxy:
  null) HTTP Status Code: 404
  .
  In versions prior to 8.1.18, IBM Spectrum Protect supported
  path style URLs when communicating with Amazon cloud.
  
  Here is an example of a path style URL:
  
  https://s3.region-code.amazonaws.com/bucket-name/key-name
  
  Starting with 8.1.18, IBM Spectrum Protect supports the
  use of AWS Hosted Style URLs. Here is an example:
  
  https://bucket-name.s3.region-code.amazonaws.com/key-name
  
  If the following conditions are met, this
  defect applies:
  
  1) A cloud-container storage pool is used connected to Amazon
  Web Services (AWS) and AWS Virtual Host Style
  URL(s) are used.
  
  2) IBM Spectrum Protect server was upgraded to 8.1.18 or higher.
  
  IBM Spectrum Protect Versions Affected:     8.1.18 server
  and above.
  
  Additional Keywords:   TS013406312  AWS BUCKET HTTP STATUS CODE
  404 HOST URL
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Storage Protect server users.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 8.1.22. Note that this is     *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed for cloud-container storage pools only. A
  server option fixCloudCntrName is created to specify whether the
  cloud container name correction is going to be performed upon
  the affected container files. This server option can only be
  changed by editing server option file dsmserv.opt and you must
  stop and start the server to activate the updated server options
  file.
  

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

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels