IZ50520: CFMUPDATENODE NOT RECOGNIZING "MINMANAGED-INSTALLING" MODE

Readme and Release notes for release 1.7.1.7 CSM-1.7.1.7-power-Linux
Readme and Release notes for release 1.7.1.8 CSM-1.7.1.8-power-AIX
Readme and Release notes for release 1.7.1.8 CSM-1.7.1.8-power-Linux
Readme and Release notes for release 1.7.1.8 CSM-1.7.1.8-x86-Linux
Readme and Release notes for release 1.7.1.7 CSM-1.7.1.7-power-AIX
Readme and Release notes for release 1.7.1.7 CSM-1.7.1.7-x86-Linux
Readme and Release notes for release 1.7.1.9 CSM-1.7.1.9-power-AIX
Readme and Release notes for release 1.7.1.9 CSM-1.7.1.9-power-Linux
Readme and Release notes for release 1.7.1.9 CSM-1.7.1.9-x86-Linux
Readme and Release notes for release 1.7.1.10 CSM-1.7.1.10-power-AIX
Readme and Release notes for release 1.7.1.10 CSM-1.7.1.10-power-Linux
Readme and Release notes for release 1.7.1.10 CSM-1.7.1.10-x86-Linux
Readme and Release notes for release 1.7.1.11 CSM-1.7.1.11-power-AIX
Readme and Release notes for release 1.7.1.11 CSM-1.7.1.11-power-Linux
Readme and Release notes for release 1.7.1.11 CSM-1.7.1.11-x86-Linux
Readme and Release notes for release 1.7.1.12 CSM-1.7.1.12-power-AIX
Readme and Release notes for release 1.7.1.13 CSM-1.7.1.13-power-AIX

APAR status

• Closed as program error.

Error description

• We had a customer experience a problem installing
  MinManaged nodes
  (axinbcu2d01,axinbcu2stdby01) and level3 advised to open
  APAR.
  
  axinbcu2m01:~ # monitorinstall
  Node                    Mode                  Status
  ---------------------------------------------------------
  ---------------
  --
  axinbcu2a01             MinManaged            MinManaged
  axinbcu2d01             MinManaged-Installing Waiting for
  Reboot and Install
  axinbcu2d02             MinManaged            MinManaged
  axinbcu2d03             MinManaged            MinManaged
  axinbcu2stdby01         MinManaged-Installing Waiting for
  Reboot and Install
  
  
  Had customer do updatenode -n axinbcu2stdby01 and now
  Status is "Updatenode failed"
  
  Level3 found the Status failure is due to a bug in
  cfmupdatenode in not recognizing the
  "MinManaged-Installing"
  mode and treating the node as if it was Managed.
  
  axinbcu2m01:~ # monitorinstall
  Node                    Mode                  Status
  ---------------------------------------------------------
  ---------------
  --
  axinbcu2a01             MinManaged            MinManaged
  axinbcu2d01             MinManaged-Installing Waiting for
  Reboot and Install
  axinbcu2d02             MinManaged            MinManaged
  axinbcu2d03             MinManaged            MinManaged
  axinbcu2stdby01         MinManaged-Installing Updatenode
  failed
  
  
  Had customer do the following:
  
  chnode -n axinbcu2stdby01 Mode=MinManaged
  updatenode -n axinbcu2stdby01
  
  Now Status is correctly saying "Installed"
  
  axinbcu2m01:/opt/csm/csmbin # monitorinstall
  Node                    Mode                  Status
  ---------------------------------------------------------
  ------------
  --
  axinbcu2a01             MinManaged            MinManaged
  axinbcu2d01             MinManaged            Waiting for
  Reboot and Install
                        axinbcu2d02             MinManaged
            MinManaged
  axinbcu2d03             MinManaged            MinManaged
  axinbcu2stdby01         MinManaged            Installed
  
  
  Seems that updatenode is not recognizing
  "MinManaged-Installing" Mode
  as "MinManaged" and treating the node like any other
  non-minmanaged node,
  and failing. It should treat "MinManaged-Installing" the
  same as "MinManaged".
  

Local fix

Problem summary

•  cfmupdatenode checks if a node is MinManaged to
  determine
  if clocal exists locally on the node, or if
  clocal needs
  to be run from the directory that is mounted
  from the
  management server.  If the Mode of the node is
  MinManaged-Installed, cfmupdatenode is failing
  to
  recognize this as a MinManaged node.   In this
  

Problem conclusion

•  The check in cfmupdatenode to determine if a
  node is
  MinMangaged has been modified to include the
  Mode of
  MinManaged-Installed.
  

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:

  U827334 U827335

Fix information

• Fixed component name

  CSM FOR AIX BAS

• Fixed component ID

  5765F6700

Applicable component levels

• R171 PSY U872436

     UP16/03/24 I 1000

PTF to Fileset Mapping

• U827334 csm.core 1.7.1.2

• U827335 csm.server 1.7.1.2

• U828687 csm.server 1.7.1.3

• U828688 csm.core 1.7.1.3

• U830583 csm.server 1.7.1.4

• U830584 csm.core 1.7.1.4

• U832562 csm.server 1.7.1.5

• U834204 csm.server 1.7.1.6

• U835515 csm.core 1.7.1.5

• U835517 csm.server 1.7.1.7

• U836300 csm.server 1.7.1.8

• U836301 csm.core 1.7.1.6

• U836480 csm.server 1.7.1.9

• U839132 csm.server 1.7.1.10

• U827334 csm.core 1.7.1.2

• U827335 csm.server 1.7.1.2

• U828687 csm.server 1.7.1.3

• U828688 csm.core 1.7.1.3

• U830583 csm.server 1.7.1.4

• U830584 csm.core 1.7.1.4

• U832562 csm.server 1.7.1.5

• U834204 csm.server 1.7.1.6

• U835515 csm.core 1.7.1.5

• U835517 csm.server 1.7.1.7

• U836300 csm.server 1.7.1.8

• U836301 csm.core 1.7.1.6

• U836480 csm.server 1.7.1.9

• U839132 csm.server 1.7.1.10

• U840142 csm.server 1.7.1.11

• U840142 csm.server 1.7.1.11

• U844047 csm.server 1.7.1.12

• U844047 csm.server 1.7.1.12

• U872436 csm.server 1.7.1.13

• U872436 csm.server 1.7.1.13