During the investigation of the issue we found the root cause of the issue. We suppose that issue related with problems in Swift configuration.
Based on [1] we are able to say that in configuration files missing following:
1. proxy-server.conf (/etc/swift/proxy-server.conf)
The varible pipeline from config section [pipeline:main] should contain container_sync, but the varible pipeline from config section [pipeline:main] is not contain container_sync parameter.
2. container-sync-realms.conf (/etc/swift/container-sync-realms.conf)
The config file should contain specifying the allowable cluster/clusters and their information, but config file contain only commented text
Please @mos-swift confirm that results of our investigation is correct and perform appropriate action to resolve this issue.
Hello all,
During the investigation of the issue we found the root cause of the issue. We suppose that issue related with problems in Swift configuration.
Based on [1] we are able to say that in configuration files missing following:
1. proxy-server.conf (/etc/swift/ proxy-server. conf)
The varible pipeline from config section [pipeline:main] should contain container_sync, but the varible pipeline from config section [pipeline:main] is not contain container_sync parameter.
[pipeline:main]
pipeline = catch_errors crossdomain healthcheck cache bulk tempurl ratelimit formpost swift3 s3token authtoken keystone staticweb container_quotas account_quotas slo proxy-server
2. container- sync-realms. conf (/etc/swift/ container- sync-realms. conf)
The config file should contain specifying the allowable cluster/clusters and their information, but config file contain only commented text
Please @mos-swift confirm that results of our investigation is correct and perform appropriate action to resolve this issue.