IBM Support

PH12966: POWERSHELL PLUGIN FAILS WHEN SCRIPT DOESN'T EXPLICITLY EXIT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The powershell plugin fails with a very nondescript error when a
    user invokes a script that doesn't explicitly end with the
    'exit' keyword (I.E. exit 0)
    

Local fix

  • Any scripts that are executed must end in exit 0 (or exit1 if
    they want to fail).
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All end users on all supported browsers.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When users specify powershell scripts that don't explicitly  *
    * end in the exit keyword, the plugin execution fails. The     *
    * exact error message returned is 'No MSFT_NetAdapter objects  *
    * found with property 'InterfaceIndex' equal to '1'. Verify    *
    * the value of the property and retry.' This error is          *
    * unrelated to any failure in the script or in the script      *
    * execution, and should not be failing the step. It is a       *
    * global error that powershell creates in the system Error     *
    * variable when a script doesn't exit.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A fix has been released with version 9 of the plugin. Instead of
    relying on the global Error variable to fail the step, failures
    from the powershell script execution are saved in their own
    variable, which will now be used to fail the step. Also, this
    fix also introduces a bug in the error output where the error
    text is never printed to stdout.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH12966

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    702

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-05

  • Closed date

    2019-06-13

  • Last modified date

    2019-06-13

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"702","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
13 June 2019