IBM Support

PI69794: UNABLE TO PARSE BLUEPRINT EVEN THOUGH STANDARD YAML SYNTAX IS USED

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

  • A blueprint containing valid yaml syntax shows error "Syntax
    errors in <blueprint_name>" and the line with the error shows an
    "Unable to parse" error.
    
    Even though the blueprint contains valid yaml syntax it is not
    in a form that the blueprint editor writes by default.  For
    example, by default the blueprint editor writes a property with
    a parameterized value as:
    
        urbancode_deploy_url: { get_param: ucd_server_url }
    
    The following is also valid yaml syntax, but is flagged with a
    parsing error:
    
        urbancode_deploy_url:
            get_param: ucd_server_url
    
    
    Another example is the syntax for get_attr.  By default the
    blueprint editor writes
    
        application: { get_attr: [resource_tree, application_name] }
    
    The following is also valid yaml syntax, but is flagged with a
    parsing error:
    
        application:
            get_attr:
            - vepc_resource_tree
            - application_name
    

Local fix

  • The only work around is to format the syntax in a way that is
    understood by the blueprint editor.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * A blueprint containing valid yaml syntax shows error "Syntax *
    * errors in <blueprint_name>" and the line with the error      *
    * shows an                                                     *
    * "Unable to parse" error.                                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A fix is available in IBM UrbanCode Deploy 6.2.2
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI69794

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-09-27

  • Closed date

    2016-12-05

  • Last modified date

    2016-12-05

  • 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

  • R600 PSN

       UP

  • R600 PSY

       UP

  • R601 PSN

       UP

  • R601 PSY

       UP

  • R610 PSN

       UP

  • R610 PSY

       UP

  • R611 PSN

       UP

  • R611 PSY

       UP

  • R612 PSN

       UP

  • R612 PSY

       UP

  • R613 PSN

       UP

  • R613 PSY

       UP

  • R620 PSN

       UP

  • R620 PSY

       UP

  • R621 PSN

       UP

  • R621 PSY

       UP

  • R622 PSN

       UP

  • R622 PSY

       UP

  • R623 PSN

       UP

  • R623 PSY

       UP

[{"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":"620","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
05 December 2016