Details
-
Bug
-
Resolution: Fixed
-
Low
-
6.1.0, 7.4.0, 7.6.0
-
None
-
4
-
Severity 3 - Minor
-
3
-
Description
Issue Summary
Removing a mirror from a copy of a Bitbucket instance (backup or otherwise) will sometimes cause the mirror to be removed from the original instance as well as the copy.
Steps to Reproduce
- Add a mirror to a running Bitbucket instance
- Make a copy of said instance and start it
- Navigate to the mirrors page delete the mirror
Expected Results
The mirror should be removed from the copy, but not from the original.
Actual Results
The mirror is removed from the original and from the copy.
Workaround
If you are using Smart Mirrors or Mirror Farms with your production instance, you need to remove their configuration from the staging instance before starting it, because otherwise your staging environment may attempt to synchronize with the mirrors. You can use the queries below to remove the configuration from the database.
DELETE FROM plugin_setting WHERE key_name LIKE 'acnct.bitbucket.mirror.%'; DELETE FROM plugin_setting WHERE key_name = 'ac.addon.list' AND key_value LIKE '%mirror%'; DELETE FROM AO_8E6075_MIRRORING_REQUEST; DELETE FROM AO_8E6075_MIRROR_SERVER;
For more information, refer to our documentation.
Attachments
Issue Links
- is related to
-
BSERV-11510 Mirror's unexpected removal may overload the upstream cluster
-
- Closed
-
- mentioned in
-
Page Loading...