SES Multisite confiiguration and zone info errors

This document (7023642) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Enterprise Storage 5.5
SUSE Enterprise Storage 5 (SES)
SUSE Linux Enterprise Server 12 Service Pack 3 (SLES 12 SP3)

Situation

When creating a secondary zone in the second cluster of a multisite configuration, the following error is observed:

cluster2:~ # radosgw-admin zone create --rgw-zonegroup=tests --rgw-zone=ses5node208 --access-key=$SYSTEM_ACCESS_KEY --secret=$SYSTEM_SECRET_KEY --endpoints=http://ses5node208:80 --default
2019-01-15 07:57:07.178645 7f7042df0dc0  0 failed reading obj info from .rgw.root:zone_info.062ab666-8b5e-4bf5-85da-1a6328f20635: (2) No such file or directory
2019-01-15 07:57:07.178730 7f7042df0dc0  0 WARNING: could not read zone params for zone id=062ab666-8b5e-4bf5-85da-1a6328f20635 name=ses5node109
2019-01-15 07:57:07.181246 7f7042df0dc0  0 failed reading obj info from .rgw.root:zone_info.9c63e69f-f1ac-407a-87e1-9a298268d926: (2) No such file or directory
2019-01-15 07:57:07.181279 7f7042df0dc0  0 WARNING: could not read zone params for zone id=9c63e69f-f1ac-407a-87e1-9a298268d926 name=ses5node108

The multisite configuration works correctly and syncs data, regardless of the errors. Likewise, the ses5node208 zone is on cluster2 while ses5node108 is on cluster1 and the following error is observed.

cluster2:~ # radosgw-admin zone get --rgw-zone=ses5node108
unable to initialize zone: (2) No such file or directory

cluster2:~ # radosgw-admin zone get --rgw-zone=ses5node208
{
    "id": "9893daaf-3586-47a3-93a1-29165b21254b",
    "name": "ses5node208",
    "domain_root": "ses5node208.rgw.meta:root",
    "control_pool": "ses5node208.rgw.control",
    "gc_pool": "ses5node208.rgw.log:gc",
    "lc_pool": "ses5node208.rgw.log:lc",
    "log_pool": "ses5node208.rgw.log",
    "intent_log_pool": "ses5node208.rgw.log:intent",
    "usage_log_pool": "ses5node208.rgw.log:usage",
    "reshard_pool": "ses5node208.rgw.log:reshard",
    "user_keys_pool": "ses5node208.rgw.meta:users.keys",
    "user_email_pool": "ses5node208.rgw.meta:users.email",
    "user_swift_pool": "ses5node208.rgw.meta:users.swift",
    "user_uid_pool": "ses5node208.rgw.meta:users.uid",
    "system_key": {
        "access_key": "fXwUpqnG2TDd9KtO5ADF",
        "secret_key": "J0pG4XA8WVhh898wLiT7g9GAYNwnt3FkMTFBDvuD"
    },
    "placement_pools": [
        {
            "key": "default-placement",
            "val": {
                "index_pool": "ses5node208.rgw.buckets.index",
                "data_pool": "ses5node208.rgw.buckets.data",
                "data_extra_pool": "ses5node208.rgw.buckets.non-ec",
                "index_type": 0,
                "compression": ""
            }
        }
    ],
    "metadata_heap": "",
    "tier_config": [],
    "realm_id": "d032c15e-3fa7-49f9-9cee-ded7ea60e9f3"
}

Resolution

The errors are normal and working as designed.

Cause

Zone information is local to individual clusters, while zone group information is global.

Notice that getting zone group information does not return errors.

cluster2:~ # radosgw-admin zonegroup get --rgw-zone=ses5node108
{
    "id": "bfcfe234-489a-4038-864f-087f144ac644",
    "name": "tests",
    "api_name": "tests",
    "is_master": "true",
...

cluster2:~ # radosgw-admin zonegroup get --rgw-zone=ses5node208
{
    "id": "bfcfe234-489a-4038-864f-087f144ac644",
    "name": "tests",
    "api_name": "tests",
    "is_master": "true",
...

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.