-
Notifications
You must be signed in to change notification settings - Fork 24
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
parse_dfs_path_strict: Hostname <hostname> is not ours. #321
Comments
Thanks for the information. Can you run |
Sure, here it is:
netbios name seems to be the name of the SmbShare: apiVersion: samba-operator.samba.org/v1alpha1
kind: SmbShare
metadata:
name: backup-windows
namespace: smb
spec:
shareName: "backup"
readOnly: false
browseable: true
securityConfig: smb-security
commonConfig: smb-config
storage:
pvc:
name: backup-windows
scaling:
availabilityMode: standard
minClusterSize: 1
groupMode: never |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am not really sure, if this is something important. When I deploy a SmbShare with the following SmbCommonConfig and access it by IP or Hostname of a cluster node, the pod logs:
As far as I can see, so far everything works fine. Access, file creation, updating something works. But every action is logged with the above entry. So feel free to just close this, if it is negligible.
Great work. samba-operator is a real cool and easy to use solution.
The text was updated successfully, but these errors were encountered: