APAR status
Closed as program error.
Error description
Steps to reproduce: 1 - Install WAS Deploy 2 - Add an offline agent to a resource. Observed: Discovery failed icon appears in the Agent Resource after automatic Websphere Discovery execution. Expected: Offline Agents should not be considered for auto discovery.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * Steps to reproduce: * * * * 1 - Install WAS Deploy * * 2 - Add an offline agent to a resource. * * * * Observed: Discovery failed icon appears in the Agent * * Resource * * after automatic Websphere Discovery execution. * * * * Expected: Offline Agents should not be considered for auto * * discovery. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
fixed in version 6.2.4.1
Temporary fix
Comments
APAR Information
APAR number
PI75397
Reported component name
UC DEPLOY
Reported component ID
5725M5400
Reported release
621
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-01-24
Closed date
2017-05-01
Last modified date
2017-05-01
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
R624 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":"621","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 May 2017