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

Test all external storages with encryption enabled #23657

Closed
10 of 11 tasks
LukasReschke opened this issue Mar 30, 2016 · 17 comments
Closed
10 of 11 tasks

Test all external storages with encryption enabled #23657

LukasReschke opened this issue Mar 30, 2016 · 17 comments
Assignees
Milestone

Comments

@LukasReschke
Copy link
Member

Due to the problems with some external storages in 9.0 with regard to the stream wrapper (which returned less than 8192 bytes) I'm going to manually retest all external storages with encryption enabled as well.

cc @owncloud/qa @rperezb Is there any way that we can come up with some automated way to test them with encryption enabled as well? That would be rocking 🚀

@LukasReschke LukasReschke self-assigned this Mar 30, 2016
@LukasReschke
Copy link
Member Author

Also cc @Xenopathic @icewind1991 @DeepDiver1975 might be worth to have https://github.com/owncloud/core/tree/0e687993c8afb36876e7d90c229b97b4aaf43b70/apps/files_external/tests adjusted to also run once with encryption enabled.

@LukasReschke LukasReschke added this to the 9.0.1-current-maintenance milestone Mar 30, 2016
@LukasReschke
Copy link
Member Author

cc @schiesbn As discussed

@LukasReschke
Copy link
Member Author

Google works but seems broken in 9.0 due to another issue… Debugging…

Edit: Fixed with #23660

@RobinMcCorkell
Copy link
Member

It would be better to isolate the behaviour that encryption sometimes breaks on, and create a unit test for that behaviour to apply for all storages. That way we keep true to individual unit tests which will make testing quicker and less prone to cross-component failures.

@rperezb
Copy link

rperezb commented Mar 31, 2016

@jvillafanez can you please help here

@LukasReschke
Copy link
Member Author

@rperezb @jvillafanez @owncloud/qa I tested all storages except "OpenStack Object Storage", "SMB" and "Sharepoint". Could you give this a test as well? 🚀

@jvillafanez
Copy link
Member

Sure, I'm building a docker image to test OpenStack (in fact devstack), but it will require a bit of time. I hope the image is mostly ready today and we can test it tomorrow

@RobinMcCorkell
Copy link
Member

@jvillafanez We already have a Docker image - see xenopathic/ceph-keystone

@jvillafanez
Copy link
Member

Setting up devstack

Unfortunately I can't make it work using docker. In my case, it complains about network issues trying to work with iptables, specially it doesn't have permissions to add new entries in iptables (I'm not willing to force heavy requirements)

The ceph-keystone didn't work for neither @Xenopathic nag me about this next week 😉

mounting via loopback
mount: Could not find any loop device. Maybe this kernel does not know
       about the loop device? (If so, recompile or `modprobe loop'.)

I'll use a VM as a fallback.

@jvillafanez
Copy link
Member


Sharepoint downloads fail with a "Bad signature" error. Uploads looks good (ownCloud 9.01 RC1)

@jvillafanez
Copy link
Member

SMB works fine 👍

@LukasReschke
Copy link
Member Author

@jvillafanez Thanks. Let me see what I can do about Sharepoint fail. I have an idea what it could be 💭

@LukasReschke
Copy link
Member Author

@jvillafanez
Copy link
Member

For sharepoint with encryption, file deletion isn't working, but renaming the file is (with and without the "Use RetryWrapper" patch)

@jvillafanez
Copy link
Member

OpenStack works fine 👍

@ghost ghost modified the milestones: 9.0.2-current-maintenance, 9.0.1 Apr 8, 2016
@PVince81
Copy link
Contributor

Can we close this and continue in the sharepoint ticket if that's the only one remaining ?

@ghost ghost closed this as completed Apr 20, 2016
@lock
Copy link

lock bot commented Aug 5, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 5, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants