Bug #52044
closedBucket sync policy core dumped
100%
Description
Hello,
Tried to follow as from one of the redhat enginner suggested to create the multisite flow based on the document and it core-dumped with:
WARNING: cannot find source zone id for name=* WARNING: cannot find source zone id for name=*
Steps how it was created:
radosgw-admin sync group create --group-id=general-symmetrical-hkg-sin-sync-group --status=allowed radosgw-admin sync group flow create --group-id=general-symmetrical-hkg-sin-sync-group --flow-id=general-symmetrical-hkg-sin-sync-group-flow --flow-type=symmetrical --zones=hkg,sin radosgw-admin sync group pipe create --group-id=general-symmetrical-hkg-sin-sync-group --pipe-id=symmetrical-hkg-sin --source-zones='*' --source-bucket='*' --dest-zones='*' --dest-bucket='*' radosgw-admin period update --rgw-realm=company --commit
Now the bucket part will come which will inherit the symmetrical-hkg-sin pipe:
radosgw-admin sync group create --bucket=mlflow-artifacts-bucket --group-id=mlflow-artifacts-bucket-default --status=enabled
And here is the above error with a huge dump came:
radosgw-admin sync group pipe create --bucket=mlflow-artifacts-bucket --group-id=mlflow-artifacts-bucket-default --pipe-id=symmetrical-hkg-sin --source-zones='*' --dest-zones='*'
I've attached the dump and the crash info.
Files
Updated by Ist Gab almost 3 years ago
New line is missing from the Steps how it was created:
radosgw-admin sync group create --group-id=general-symmetrical-hkg-sin-sync-group --status=allowed radosgw-admin sync group flow create --group-id=general-symmetrical-hkg-sin-sync-group --flow-id=general-symmetrical-hkg-sin-sync-group-flow --flow-type=symmetrical --zones=hkg,sin radosgw-admin sync group pipe create --group-id=general-symmetrical-hkg-sin-sync-group --pipe-id=symmetrical-hkg-sin --source-zones='*' --source-bucket='*' --dest-zones='*' --dest-bucket='*'
Updated by Pawel Szweminski over 2 years ago
Hey,
I have the same warning in 16.2.5 version.
Updated by Soumya Koduri almost 2 years ago
I couldn't reproduce the crash but probably https://github.com/ceph/ceph/pull/46403 fixes it.
Updated by Ist Gab almost 2 years ago
Soumya Koduri wrote:
I couldn't reproduce the crash but probably https://github.com/ceph/ceph/pull/46403 fixes it.
So in the next octopus this one at least will be fixed?
Updated by Soumya Koduri almost 2 years ago
Ist Gab wrote:
Soumya Koduri wrote:
I couldn't reproduce the crash but probably https://github.com/ceph/ceph/pull/46403 fixes it.
So in the next octopus this one at least will be fixed?
Sure, will backport. Meanwhile could you please verify the fix once its merged into main.
Updated by Casey Bodley almost 2 years ago
- Status changed from New to Fix Under Review
- Backport set to octopus pacific quincy
- Pull request ID set to 46403
Updated by Casey Bodley almost 2 years ago
- Status changed from Fix Under Review to Pending Backport
- Assignee changed from Yehuda Sadeh to Soumya Koduri
Updated by Backport Bot almost 2 years ago
- Copied to Backport #55917: quincy: Bucket sync policy core dumped added
Updated by Backport Bot almost 2 years ago
- Copied to Backport #55918: pacific: Bucket sync policy core dumped added
Updated by Backport Bot almost 2 years ago
- Copied to Backport #55919: octopus: Bucket sync policy core dumped added
Updated by Backport Bot almost 2 years ago
- Tags changed from multisite,rgw,sync to multisite,rgw,sync backport_processed
Updated by Konstantin Shalygin about 1 year ago
- Status changed from Pending Backport to Resolved
- % Done changed from 0 to 100