cloudfoundry / smb-volume-release Goto Github PK
View Code? Open in Web Editor NEWBOSH release with SMB driver and broker
License: Apache License 2.0
smb-volume-release's Issues
SMB3 Encryption support
Does this tile support Encryption in SMB3?
Release 0.1.6 fails to export to linux
If I try to export the smb-volume-release 0.1.6 to a linux stemcell I get the error below. I'm not sure how other releases that have windows packages mixed in solve this.
Perhaps the windows package's packaging script can skip if exporting to a linux stemcell since the linxu stemcell won't be using the windows job anyway?
Task 107619 | 21:20:20 | Compiling packages: golang-smbvolume-windows/a979fc2219d6964af5f0ae38f1e9cd1df75e5325 (00:01:07)
L Error: Action Failed get_task: Task 22c10af0-a5e0-44bd-4473-633707b871d8 result: Compiling package golang-smbvolume-windows: Running packaging script: Running packaging script: Command exited with 2; Stdout: , Stderr: packaging: line 1: =: command not found
packaging: line 2: syntax error near unexpected token `('
packaging: line 2: `trap { $host.SetShouldExit(1) }'
Cosmetic issues w/marketplace and space name
The broker release has some minor cosmetic issues needing cleanup, specifically:
- the system space created has a typo "smb-voloume-service-space"
- no marketplace icon image within Apps Manager.
Would also suggest leaving the "Default Location" field under the Service Broker Application pane blank (and mandatory). Currently the tile defaults to "useast" which most users overlook and often wish to override (in some circumstances this also causes issue with no Gen4 hardware support in USEast).
Support Bionic stemcell
Describe the bug
Hi all,
we tried to compile the smb-volume release for Ubuntu Bionic and ran into the following error:
+ make
help2man: can't get `--help' info from automake-1.15
Try `--no-discard-stderr' if option outputs to stderr
make: *** [doc/automake-1.15.1] Error 255
A possible explanation could be that automake-1.15 from the cifs-utils package no longer works with newer versions of Perl which are consumed from Bionic (see issue: crosstool-ng/crosstool-ng#987 (comment)).
To Reproduce
Steps to reproduce the behavior:
bosh -e bosh export-release -d compilation-workspace smb-volume/3.1.0 ubuntu-bionic/0.18
With deployed manifest:
name: compilation-workspace
releases:
- name: smb-volume
version: "3.1.0"
stemcells:
- alias: default
os: ubuntu-bionic
version: latest
instance_groups: []
update:
canaries: 1
max_in_flight: 1
canary_watch_time: 1000-90000
update_watch_time: 1000-90000
Expected behavior
Successful compilation and export of tgz packages.
Version of smb-volume-release
3.1.0
Full error log:
Task XXXX | 14:03:06 | Compiling packages: cifs-utils/2b5f90c43280309ef547f546893b29386d66c4b4ac3387a6e65aad6c696bade5 (00:01:42)
L Error: Action Failed get_task: Task 30846a25-06d1-4396-538f-1da9cee3c248 result: Compiling package cifs-utils: Running packaging script: Running packaging script: Command exited with 2; Truncated stdout: /usr/bin/install -c -m 644 autoconf.m4 general.m4 status.m4 oldnames.m4 specific.m4 autoheader.m4 autoupdate.m4 autotest.m4 autoscan.m4 lang.m4 c.m4 erlang.m4 fortran.m4 functions.m4 go.m4 headers.m4 types.m4 libs.m4 programs.m4 '/var/vcap/data/compile/cifs-utils/temp/share/autoconf/autoconf'
[...]
Makefile:3687: recipe for target 'doc/automake-1.15.1' failed
, Stderr: + source /var/vcap/packages/python-2.7/bosh/compile.env
++ export PATH=/var/vcap/packages/python-2.7/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
++ PATH=/var/vcap/packages/python-2.7/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
++ export PYTHONPATH=/var/vcap/packages/python-2.7/lib/python2.7/site-packages:
++ PYTHONPATH=/var/vcap/packages/python-2.7/lib/python2.7/site-packages:
+ temp_path=/var/vcap/data/compile/cifs-utils/temp
+ mkdir /var/vcap/data/compile/cifs-utils/temp
+ tar xf autoconf-2.69.tar.gz
+ pushd autoconf-2.69
+ ./configure --prefix=/var/vcap/data/compile/cifs-utils/temp
+ make
+ make install
+ export PATH=/var/vcap/packages/python-2.7/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/var/vcap/data/compile/cifs-utils/temp/bin
+ PATH=/var/vcap/packages/python-2.7/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/var/vcap/data/compile/cifs-utils/temp/bin
+ popd
+ tar xf automake-1.15.tar.gz
+ pushd automake-1.15
+ ./configure --prefix=/var/vcap/data/compile/cifs-utils/temp
configure: WARNING: Fortran compiler cannot create executables
configure: WARNING: Fortran 77 compiler cannot create executables
+ make
help2man: can't get `--help' info from automake-1.15
Try `--no-discard-stderr' if option outputs to stderr
make: *** [doc/automake-1.15.1] Error 255
Thanks!
cc @StefanWutz
Add support for cf CLI v8
cf CLI v7 support was added 2 years ago.
Now v8 is available and the relevant errands should be updated to accept that version of the cf CLI.
Submit smb-volume-release to bosh.io
So it is easy to download release tarballs.
Get `permission denied error` while writing to the share drive
Hi:
We've deployed smb-volume-release with the latest CF release and the deploy works, and we've also deployed SMB test server so we can run some test.
After pushing pora and try to write a file into the shared mount, we get an permission denied error.
After some troubleshooting, we noticed we were using bind options like {"uid":"1000","gid":"1000","username":"smbuser","password":"<redacted>"},
it used a different uid/gid from what is used by smbdriver. the default uid/gid used by smbdriver is 2000.
after changing the bind options to below fixed the issue.
{"uid":"2000","gid":"2000","username":"smbuser","password":"<redacted>"},
so our questions are: Is that behavior expected? why do we want uid/gid to be configured by the user? would it be easier just removing this option?
Regard
Kai
Generate the smb tile to use xenial stemcell
`smbbrokerpush` uses a `CF_HOME` dir that collides with other errands
Refer to similar issue on NFS here.
Errands may fail with the following error upon subsequent deploys when CF_HOME is set to the same directory as another errand:
cf version 6.41.0+dd4c76cdd.2018-11-28
API endpoint: https://api.sys.maraudon.cf-app.com
API endpoint: https://api.sys.maraudon.cf-app.com (API version: 2.128.0)
Not logged in. Use 'cf login' to log in.
FAILED
Service account currently logged in. Use 'cf logout' to log out service account and try again.
Steps to reproduce:
- Run
smbbrokerpusherrand followed bynfsbrokerpush(this should fail with the above error)
We're feeling pretty confident that this is the root case:
- The NFS errand sets
CF_HOMEto/var/vcap/bosh/home/cf/.cfhere as does the SMB errand (we'll open a separate issue on those repos) - If you login as a CF UAA client, then login as a CF UAA user, the CF CLI will throw the above error
- We configure the NFS errand with a user, but the SMB errand with a client which causes the NFS errand will fail
Workaround is to either disable one of the errands or SSH onto the co-located errand VM and run rm -rf /var/vcap/bosh/home/cf/.cf.
The way other components avoid this is to create a CF_HOME dir that is unique to their release, e.g. export CF_HOME=/var/vcap/data/push-apps-manager/. Could y'all do something similar with SMB errand?
Please configure GITBOT
Pivotal uses GITBOT to synchronize Github issues and pull requests with Pivotal Tracker.
Please add your new repo to the GITBOT config-production.yml in the Gitbot configuration repo.
If you don't have access you can send an ask ticket to the CF admins. We prefer teams to submit their changes via a pull request.
Steps:
- Fork this repo: cfgitbot-config
- Add your project to
config-production.ymlfile - Submit a PR
If there are any questions, please reach out to [email protected].
Test Tracker integration removal
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.