APAR status
Closed as program error.
Error description
It is possible for a component to be deployed before it is finished being imported into Codestation. To reproduce: 1. Create an application that deploys by downloading a component version's artifacts from codestation. ("Download Artifacts"). 2. Run a version import for that component such that it takes a long time (minutes) to complete You may accomplish this by throttling the network between the import agent and the UCD server, or you may simply use a use a very large file. 3. While the import is running and not yet completed, run a deployment process, selecting the "Latest Version" of the component. Notice that the (essentially uncompleted) version is selected. 4. Notice that the Download Artifacts step fails. 5. Notice that the version import now fails as well.
Local fix
1) Introduce a delay between a version import and the download artifacts step in deployment. You would use the "wait" process step. How much of a delay you need to use will take some experimenting to determine. 2) Use status gates to ensure that a certain status of a component version is set before triggering the deployment. 3) Certain UCD plugins can download artifacts directly from source artifact repositories. This can eliminate the need to duplicate files in Codestation.
Problem summary
**************************************************************** * USERS AFFECTED: * * All end users on all supported browsers. * **************************************************************** * PROBLEM DESCRIPTION: * * It is possible for a component to be deployed before it is * * finished being imported into Codestation. * * * * To reproduce: * * 1. Create an application that deploys by downloading a * * component * * version's artifacts from codestation. ("Download * * Artifacts"). * * 2. Run a version import for that component such that it * * takes a * * long time (minutes) to complete You may accomplish this by * * throttling the network between the import agent and the UCD * * server, or you may simply use a use a very large file. * * 3. While the import is running and not yet completed, run a * * deployment process, selecting the "Latest Version" of the * * component. Notice that the (essentially uncompleted) * * version is * * selected. * * 4. Notice that the Download Artifacts step fails. * * 5. Notice that the version import now fails as well. * **************************************************************** * RECOMMENDATION: * * Fixed in version 7.0.1.2 * ****************************************************************
Problem conclusion
Fix is provided in IBM UrbanCode Deploy 7.0.1.2
Temporary fix
Comments
APAR Information
APAR number
PI89045
Reported component name
UC DEPLOY
Reported component ID
5725M5400
Reported release
624
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-10-18
Closed date
2018-12-19
Last modified date
2018-12-19
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":"624","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
19 December 2018