IBM Support

PH07152: DOCKER REGISTRY SOURCE PLUGIN INCORRECTLY REPORTS IT CANNOT ACCESS THE SPECIFIED REGISTRY IN SOME CASES

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

  • When the plugin receives an HTTP response code >= 300 from a
    registry, it reports that it cannot access the specified
    registry, but does not report the actual error so that the user
    can correct it.
    
    Example:
    
    [Ok] Connecting to the Artifactory Docker registry...
    Repository List: [example-image]
    Repository 'example-image' is found at
    'https://example.com/example-registry'.
    [Ok] Connected successfully.
    [Ok] Listing tags for example-image...
    [Ok] Retrieved 1 tag(s).
    Tag "1" matched the regex "1"
    [Error] import version failed.
    [Error] Unable to connect to
    'https://example.com/example-registry/example-image/manifests/1'
    :
     Please check credentials, image name, and Registry.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The plugin will output "[Error] Unable to connect to         *
    * '<URL>': Please check credentials, image name, and           *
    * Registry." in some cases, but will not output the underlying *
    * reason so the user can correct it.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to plugin version 33                                 *
    ****************************************************************
    

Problem conclusion

  • Fixed in plugin version 33
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH07152

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    627

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-01-10

  • Closed date

    2019-01-28

  • Last modified date

    2019-01-28

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

Document Information

Modified date:
28 January 2019