Skip to content

Support exporting diego-release on windows #602

@ciriarte

Description

@ciriarte

Summary

bosh export-release command doesn't work on Windows.

Steps to Reproduce

  1. Deploy a diego on a Windows instance
  2. Execute bosh export-release diego/2.53.1 windows2019/2019.41
  3. The following error occurs
Using environment '10.0.0.5' as client 'ops_manager'

Task 234

Task 234 | 02:51:46 | Preparing package compilation: Finding packages to compile (00:00:00)
Task 234 | 02:51:46 | Compiling packages: diego-sshd/622ea18875a9cbf4fcfceb3cbc5a70a1ce6ada36
Task 234 | 02:51:46 | Compiling packages: healthcheck/76a441a1fec6d48b60825f8d28310653dca1c2b3 (00:06:07)
                    L Error: Action Failed get_task: Task 68f38b7f-12ce-481f-5eab-7ef4d2c414e8 result: Compiling package healthcheck: Running packaging script: Running packaging script: Command exited with 1; Stdout: , Stderr: + ldd ${BOSH_INSTALL_TARGET}/healthcheck && echo "healthcheck must be s ...
+                                        ~~
The token '&&' is not a valid statement separator in this version.
At line:16 char:88
+ ... /healthcheck && echo "healthcheck must be statically linked" && false
+                                                                  ~~
The token '&&' is not a valid statement separator in this version.
At line:1 char:1
+ iex (get-content -raw packaging)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ParserError: (:) [Invoke-Expression], ParseException
    + FullyQualifiedErrorId : InvalidEndOfLine,Microsoft.PowerShell.Commands.InvokeExpressionCommand


Task 234 | 02:57:59 | Compiling packages: diego-sshd/622ea18875a9cbf4fcfceb3cbc5a70a1ce6ada36 (00:06:13)
                    L Error: Action Failed get_task: Task 46c4e2e1-06a7-4749-70d2-89536451d3bf result: Compiling package diego-sshd: Running packaging script: Running packaging script: Command exited with 1; Stdout: , Stderr: + ldd ${BOSH_INSTALL_TARGET}/diego-sshd && echo 'diego-sshd must be sta ...
+                                       ~~
The token '&&' is not a valid statement separator in this version.
At line:16 char:86
+ ... T}/diego-sshd && echo 'diego-sshd must be statically linked' && false
+                                                                  ~~
The token '&&' is not a valid statement separator in this version.
At line:1 char:1
+ iex (get-content -raw packaging)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ParserError: (:) [Invoke-Expression], ParseException
    + FullyQualifiedErrorId : InvalidEndOfLine,Microsoft.PowerShell.Commands.InvokeExpressionCommand


Task 234 | 02:57:59 | Error: Action Failed get_task: Task 68f38b7f-12ce-481f-5eab-7ef4d2c414e8 result: Compiling package healthcheck: Running packaging script: Running packaging script: Command exited with 1; Stdout: , Stderr: + ldd ${BOSH_INSTALL_TARGET}/healthcheck && echo "healthcheck must be s ...
+                                        ~~
The token '&&' is not a valid statement separator in this version.
At line:16 char:88
+ ... /healthcheck && echo "healthcheck must be statically linked" && false
+                                                                  ~~
The token '&&' is not a valid statement separator in this version.
At line:1 char:1
+ iex (get-content -raw packaging)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ParserError: (:) [Invoke-Expression], ParseException
    + FullyQualifiedErrorId : InvalidEndOfLine,Microsoft.PowerShell.Commands.InvokeExpressionCommand



Task 234 Started  Thu Nov 11 02:51:46 UTC 2021
Task 234 Finished Thu Nov 11 02:57:59 UTC 2021
Task 234 Duration 00:06:13
Task 234 error

Capturing task '234' output:
  Expected task '234' to succeed but state is 'error'

Exit code 1

Expected result: It exports the release.

Diego repo

Environment Details

diego-release 2.53.1

Possible Causes or Fixes (optional)

I don't think the version of powershell installed in the rootfs supports the pipeline chain operators.

Additional Text Output, Screenshots, contextual information (optional)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions