nextcloud / nextcloud/circles

Circle shares not synced when adding first member from a new remote instance

Open
#2,829 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
JavaScript
Stars
177
Forks
68
Avg merge
2d 22h
Merged PRs (30d)
60

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

New members from an instance with no previous members don't get existing circle shares synced in federated environment.


Steps to reproduce
  1. setup federation environment with two Nextcloud instances (e.g. nc_1 + nc_2)
  2. on nc_1 as bob:
  • create test_team and check "Allow federated members"
  • create test_folder and share with test_team
  • add john from nc_2 (john@nc_2)
  1. on nc_2 as john:
  • navigate to files > "All files"
  • notice how shared folder does not appear

note: if there's already another member from nc_2 on test_team and has access to test_folder, adding a new member does show the resource correctly for them.

Expected behaviour
  • john should see test_folder among his files has the resource was shared with a team he belongs to
  • entries should be created on oc_circles_mount and oc_circles_mountpoint for given resource on nc_2
Actual behaviour
  • john does not see test_folder among his files.
  • entries are not created on oc_circles_mount and oc_circles_mountpoint for given resource on nc_2
Server configuration

Web server: Apache/Nginx

Database: MySQL/Maria/SQLite/PostgreSQL

PHP version: 8.5/8.4/8.3

Nextcloud version: Nextcloud 36.0.0 dev

List of activated apps Enabled: - appstore: 3.0.0-dev.0 - circles: 36.0.0-dev.0 - cloud_federation_api: 3.0.0-dev.0 - comments: 3.0.0-dev.0 - contactsinteraction: 3.0.0-dev.0 - dashboard: 9.0.0-dev.0 - dav: 3.0.0-dev.0 - federatedfilesharing: 3.0.0-dev.0 - federation: 3.0.0-dev.0 - files: 4.0.0-dev.0 - files_pdfviewer: 8.0.0-dev.0 - files_reminders: 3.0.0-dev.0 - files_sharing: 3.0.0-dev.0 - files_trashbin: 3.0.0-dev.0 - files_versions: 3.0.0-dev.0 - lookup_server_connector: 3.0.0-dev.0 - oauth2: 3.0.0-dev.0 - profile: 3.0.0-dev.0 - provisioning_api: 3.0.0-dev.0 - recommendations: 8.0.0-dev.0 - settings: 3.0.0-dev.0 - sharebymail: 3.0.0-dev.0 - sharing: 2.0.0-dev.1 - systemtags: 3.0.0-dev.0 - text: 9.0.0-dev.0 - theming: 4.0.0-dev.0 - twofactor_backupcodes: 3.0.0-dev.0 - updatenotification: 3.0.0-dev.0 - user_status: 3.0.0-dev.0 - viewer: 8.0.0-dev.0 - weather_status: 3.0.0-dev.0 - webhook_listeners: 3.0.0-dev.0 - workflowengine: 4.0.0-dev.0 Disabled: - admin_audit: 3.0.0-dev.0 - contacts: 8.8.0-dev.0 - encryption: 4.0.0-dev.0 - files_external: 3.0.0-dev.0 - globalsiteselector: 2.7.3 - groupfolders: 23.0.0-dev.3 - hmr_enabler: 1.4.0-dev.0 - profiler: 6.0.0-dev.0 - testing: 3.0.0-dev.0 - user_ldap: 3.0.0-dev.0 - user_oidc: 8.11.0 ``` If you have access to your command line run e.g.: sudo -u www-data php occ app:list from within your Nextcloud installation folder ```
Nextcloud configuration
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
Browser

Browser name: Firefox/Chrome/Safari/…

Browser version: 124/125/…

Operating system: Windows/Ubuntu/Mac/…

Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the two-instance federation setup described in the issue, then trace the path taken when the first remote member is added to a circle. Inspect why oc_circles_mount and oc_circles_mountpoint entries are not created on the remote instance; done means john sees test_folder and both entries are created in the new-instance case.

Written by the indexing model from the issue text.

Assessment

Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.