[Windows] Missing bosh create-env support

[ZPascal]

Hi community,

we've faced the case that currently the create-env parameter is not supported by the bosh cli.

How we've identified the case?
We've faced the case thats it's not possible to use the Bosh Lite on Windows machines.

Background information:
Bosh Lite setup

[rkoster]

@ZPascal Could you try removing those lines and check if the VirtualBox CPI gets any further? There is no point in removing those lines if the VirtualBox CPI does not work, given that there are no other CPI's that want to support windows.

[ZPascal]

@rkoster Do you mean the corresponding lines inside the bosh CLI? I'll organize a Windows machine and try it out.

[rkoster]

Yes the corresponding lines inside the bosh cli.

[ZPascal]

@rkoster I've removed the code lines and tested it again on the Windows machine. Now, I've faced another issue, but not directly related anymore to the Bosh CLI. Do you have ever seen that issue or should I start to debug it?

[beyhan]

@ZPascal this looks like a wrong network configuration in the BOSH manifest. You can check the docs here to correct it.

[rkoster]

@ZPascal can this issue be closed?

[ZPascal]

@rkoster No, I have not fixed the issue/ tested the solution yet. As a follow-up, I'll definitely open a PR inside this repository to adjust the used version of the utils implementation.

[ZPascal]

FYI @rkoster & @beyhan To give you an update on that topic. I've executed the bosh create-env "<src>/bosh.yml" --state .\state.json ... -v internal_cidr=192.168.56.0/24 ... command and the BOSH part works as expected, but now we are back on VBox CPI release and now I've faced an issue related to command execution and used environment. (screenshot) I think you know, that the release is a bit shaky and does not officially support Windows.

I'll further work as a side topic on it, but how should we continue with this topic? Should I open the corresponding PR to adapt the Bosh CLI or should we roll it out, if everything works as expected (my preferred solution)?

[bgandon]

The bosh create-env is probably starting to compile the VirtualBox CPI in the local (Windows) machine. We would need the normal non-debug log to take a step back and understand at which steps this fails.

[ZPascal]

Hi @bgandon, for me it looks like BOSH wants to compile the Golang CPI part with classical Bash syntax. Do you have any idea, where I can find the corresponding part inside the source code?

C:\Users\ZPascal\Workspace\vbox>C:\Users\ZPascal\Workspace\bosh-cli\out\bosh create-env "C:\Users\ZPascal\Workspace\bosh-deployment\bosh.yml"  --state .\state.json  -o "C:\Users\ZPascal\Workspace\bosh-deployment\virtualbox\cpi.yml" -o "C:\Users\ZPascal\Workspace\bosh-deployment\virtualbox\outbound-network.yml"  -o "C:\Users\ZPascal\Workspace\bosh-deployment\bosh-lite.yml"  -o "C:\Users\ZPascal\Workspace\bosh-deployment\bosh-lite-runc.yml"  -o "C:\Users\ZPascal\Workspace\bosh-deployment\uaa.yml"  -o "C:\Users\ZPascal\Workspace\bosh-deployment\credhub.yml"  -o "C:\Users\ZPascal\Workspace\bosh-deployment\jumpbox-user.yml"  --vars-store .\creds.yml  -v director_name=bosh-lite  -v internal_ip=192.168.56.6  -v internal_gw=192.168.56.1  -v internal_cidr=192.168.56.0/24  -v outbound_network_name=NatNetwork
Deployment manifest: 'C:\Users\ZPascal\Workspace\bosh-deployment\bosh.yml'
Deployment state: '.\state.json'
 
Started validating
  Downloading release 'bosh'... Finished (00:00:38)
  Validating release 'bosh'... Finished (00:00:01)
  Downloading release 'bpm'... Finished (00:00:16)
  Validating release 'bpm'... Finished (00:00:00)
  Downloading release 'bosh-virtualbox-cpi'... Finished (00:00:46)
  Validating release 'bosh-virtualbox-cpi'... Finished (00:00:05)
  Downloading release 'garden-runc'... Finished (00:01:17)
  Validating release 'garden-runc'... Finished (00:00:01)
  Downloading release 'bosh-warden-cpi'... Finished (00:00:33)
  Validating release 'bosh-warden-cpi'... Finished (00:00:00)
  Downloading release 'os-conf'... Finished (00:00:01)
  Validating release 'os-conf'... Finished (00:00:01)
  Downloading release 'uaa'... Finished (00:01:20)
  Validating release 'uaa'... Finished (00:00:00)
  Downloading release 'credhub'... Finished (00:00:56)
  Validating release 'credhub'... Finished (00:00:00)
  Validating cpi release... Finished (00:00:00)
  Validating deployment manifest... Finished (00:00:00)
  Downloading stemcell... Finished (00:02:16)
  Validating stemcell... Finished (00:00:01)
Finished validating (00:08:22)
 
Started installing CPI
  Compiling package 'golang-1-linux/79f531850e62e3801f1dfa4acd11c421aebe653cd4316f6e49061818071bb617'... Failed (00:00:00)
Failed installing CPI (00:00:00)
 
Installing CPI:
  Compiling job package dependencies for installation:
    Compiling job package dependencies:
      Compiling package:
        Starting command bash -x packaging:
          exec: "bash": executable file not found in %!P(MISSING)ATH%!(NOVERB)
 
Exit code 1

[jpalermo]

The compilation is happening down here

[ZPascal]

@jpalermo Thank you for pointing me to the right code lines. I'll check the possible options.