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

bbr on windows stemcell #15

Closed
jgprogramming opened this issue Apr 20, 2018 · 6 comments
Closed

bbr on windows stemcell #15

jgprogramming opened this issue Apr 20, 2018 · 6 comments
Labels

Comments

@jgprogramming
Copy link

Hey,

We use BBR in our CF deployment to backup mysql and UAA (both of these components are on linux stemcells). After adding windows cell to our Cf deployment we get this error.

failed to find instances for deployment cf: couldn't find jobs: finding scripts failed on compute_win/4a129967-7775-43d1-9cc3-cc9b020a957d: 'sudo' is not recognized as an internal or external command

Are there any plans to allow BBR to work with windows vms? Even ability to skip this vm would be helpful.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/156944749

The labels on this github issue will be updated when the story is started.

@alamages
Copy link
Contributor

Hi @jgprogramming

Currently, cf-deployment with windows cells is not supported by bbr. And there is no way to skip an instance in the deployment when running bbr deployment backup/restore.

Emmanouil && @jamesjoshuahill

@julian-hj
Copy link
Member

+1 on this issue--it is blocking us from testing BBR in the persistence pipeline, and I suspect that it will block other teams soon also. I suppose we could deploy the windows cell to a different deployment, but that would be quite a lot of work, and would result in a flaky non-standard deployment for us, so I am reluctant to go down that road.

Is it not possible to just skip windows VMs when traversing a deployment, and just emit a warning? To me that seems like a much better behavior than failing with no way to recover.

@julian-hj
Copy link
Member

One thought--if you are running commands via ssh, you could start your script with Exit which will generate an error, but not exit on unix, and will terminate the shell on windows. (since windows is case insensitive, and Unix is not.)

If you want to not have an ugly error in your logs, then the following seems to swallow the error on Unix without causing parse errors on windows:

Exit 2> exit.txt
rm exit.txt

@alamages
Copy link
Contributor

Hello @julian-hj and @jgprogramming

We have a new 1.2.4 BBR which works with windows VMs (it properly skips them without failing).

@julian-hj
Copy link
Member

@alamages excellent news! We shall unpause DRATS in our pipelines. Thanks for the heads up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants