Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable22] Fix removing remote shares when the remote server is unreachable #29565

Merged
merged 6 commits into from
Mar 10, 2022

Conversation

backportbot-nextcloud[bot]
Copy link

backport of #25332

danxuliu and others added 6 commits November 5, 2021 14:06
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The federated server needs to be stopped during the tests, so it is now
stopped in the FederationContext for each scenario instead of just once
in the run.sh script.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Technically, saying that a storage has no updates when it's not
available is correct.

This makes it possible to retrieve the cache entry for the mount point
and also to list and remove unavailable federated shares.

Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Signed-off-by: Vincent Petry <vincent@nextcloud.com>

Co-authored-by: Carl Schwan <carl@carlschwan.eu>
@PVince81
Copy link
Member

PVince81 commented Nov 5, 2021

let's hold for now as this changes the behavior of unavailable external storages

@szaimen
Copy link
Contributor

szaimen commented Nov 8, 2021

let's hold for now as this changes the behavior of unavailable external storages

Does it fix #20995?

Copy link
Member

@skjnldsv skjnldsv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@blizzz
Copy link
Member

blizzz commented Nov 10, 2021

moved to 22.2.2

@skjnldsv skjnldsv mentioned this pull request Jan 7, 2022
9 tasks
@solracsf
Copy link
Member

solracsf commented Jan 7, 2022

Should this be merged now?

@MichaIng MichaIng added the 3. to review Waiting for reviews label Jan 12, 2022
@skjnldsv skjnldsv mentioned this pull request Jan 20, 2022
8 tasks
@skjnldsv
Copy link
Member

@PVince81 ?

@skjnldsv skjnldsv mentioned this pull request Jan 25, 2022
5 tasks
@skjnldsv
Copy link
Member

Ping

@blizzz blizzz mentioned this pull request Feb 11, 2022
12 tasks
@blizzz blizzz mentioned this pull request Mar 9, 2022
@blizzz
Copy link
Member

blizzz commented Mar 10, 2022

@PVince81 ping

@PVince81
Copy link
Member

I still feel a bit scared to merge this in 22.

on the other hand, we didn't see any related federated share issues for 23 so far

@blizzz
Copy link
Member

blizzz commented Mar 10, 2022

I still feel a bit scared to merge this in 22.

on the other hand, we didn't see any related federated share issues for 23 so far

changes look ok imo, but i would not know whether there are possible side effects.

So, merge now, keep open and merge later, or close (m/k/c)?

@blizzz
Copy link
Member

blizzz commented Mar 10, 2022

Vincent said merge.

@blizzz blizzz merged commit 06600f6 into stable22 Mar 10, 2022
@blizzz blizzz deleted the backport/25332/stable22 branch March 10, 2022 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants