Skip to main content
NetApp Knowledge Base

CONTAP-741156: After S3 FlexGroup expansion, S3 GetObject requests may unexpectedly fail with HTTP error "404 Not Found"

  1. Last updated
  2. Save as PDF
Views:
133
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Issue

Expanding an already full S3 FlexGroup from 1 or 2 constituents to 3 or more constituents could result in S3 read requests failing with HTTP error "404 Not Found"
If this ONTAP S3 instance is used as target for FabricPool then it can result in potential data loss on the FabricPool aggregates.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.