PK77395: Sticky is not honored on restarts of builds

APAR status

• Closed as program error.

Error description

• On a restart of a project that has a pool of servers defined, th
  e
  restart selects another server. This is not expected behavior...
  .
  
  
  
  
  
  The CM team was ok with step 12 failing, but when restarting the
   project
  at step 13 a different server was selected. The project needs to
   run on
  the original server. The project is defined with the sticky bit
  set.
  
  
  To reproduce:
  
  1) Make a project with sticky bit set
  
  2) Make six steps with a fail step at step 3 for example:
  
    echo hello
  
    echo hello
  
    exit 1
  
    echo hello
  
    echo hello
  
    echo hello
  
  3) deselect the failed step and restart the build
  
  
  
  Running the above project a few times against a pool of servers
  will
  show the defect. A sticky project should stick to a server regar
  dless of
  restarts.
  
  
  
  This functionality worked in 7.0.2 iFix 1 and has since not work
  ed
  properly.
  

Local fix

Problem summary

• Sticky server choice ignored after a restart.
  

Problem conclusion

• Roll back of code change at line 123 of Project.pm resolved
  defect.
  

Temporary fix

Comments

APAR Information

• 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

  BUILD FORGE EE

• Fixed component ID

  5724Q6101

Applicable component levels

• R700 PSN

     UP