[HDDS-5463] [FSO] Recon Container API does not work correctly with FSO

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Labels: pull-request-available
• Assignee: Arafat Khan
• Reporter: Yuan Gu
• Created: 19/Jul/21 21:29
• Updated: 31/Mar/23 07:40
• Resolved: 31/Mar/23 07:40

Description

How to reproduce the bug: (on a clean master directory)

1. Enabled FSO by adding 

   OZONE-SITE.XML_ozone.om.enable.filesystem.paths=true;
   OZONE-SITE.XML_ozone.om.metadata.layout=PREFIX;

    to docker-config. Also make sure 

   OZONE-SITE.XML_ozone.recon.om.snapshot.task.interval.delay=1m

   so no need to wait more than 1 minute.

1. Updated docker-compose.yaml by setting the x-layout_version to 

   x-layout_version:
     &metadata_layout
     OZONE-SITE.XML_ozone.om.metadata.layout: ${OZONE_OM_METADATA_LAYOUT:-PREFIX}
     OZONE-SITE.XML_ozone.om.enable.filesystem.paths: ${OZONE_OM_ENABLE_FILESYSTEM_PATHS:-true}
   

1. run docker-compose, exec into OM CLI when docker is up
2. Write a key to make container non-zero
3. Go to

   http://localhost:9888/api/v1/containers

   and wait for 1 minute.

1. The container endpoint should not working as expected (still 0).

cc smeng, avijayan

Issue Links

• Discovered while testing: HDDS-7496 Make default bucket layout FSO in a backwards compatible way
• is duplicated by: HDDS-5904 Update Recon for files created with FSO Buckets
• is duplicated by: HDDS-7763 Recon: Support FSO buckets in container to key mapping
• relates to: HDDS-7140 Ozone Recon UI and Functionality Improvements
• links to: GitHub Pull Request #4182