Bug 1299826

Summary: owncloud external smb storage seeks "foo" instead of a user share ?
Product: [Fedora] Fedora EPEL Reporter: lejeczek <peljasz>
Component: owncloudAssignee: James Hogarth <james.hogarth>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: epel7CC: awilliam, ignatenko, james.hogarth, peljasz, shawn
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-22 00:33:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description lejeczek 2016-01-19 10:54:12 UTC
Description of problem:

in my external "SMB / CIFS using OC login" I have "Username as share" ticked in.
Yet in the logs I see:

..
ownCloud[26619]: {PHP} session setup failed: NT_STATUS_LOGON_FAILURE params(-d 0 '//my.server.mine/foo' -c 'ls') at /usr/share/owncloud/apps/files_external/3rdparty/smb4php/smb.php#206
..

and I cannot access that external storage resource in "File"


Version-Release number of selected component (if applicable):

owncloud-8.0.9-1.el7.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 James Hogarth 2016-04-25 06:40:33 UTC
The 8.1 update moves from the old smb4php code to using Icewind smb

Can you please verify if you see the behaviour on the new update that has recently gone stable.

As a reminder if you missed the Fedora Magazine and Fedora/EPEL mailing list emails please ensure you are updated to 8.1 and fully tested before the 8.2 update.

Due to the way upstream handles updates it's not possible to jump 8.0 to 8.2 so it's important to have updated to 8.1 and fully tested your installation before the 8.2 update gets pushed stable in a few weeks.

Comment 2 James Hogarth 2016-05-22 00:33:53 UTC
Since it's been a month with no response and 8.2.4 is about to go stable I'm closing this bug.

If you see it on 8.2.4 please reopen with steps to reproduce it.