Upgrade to TL8 failed: bos.net.NFS.client 6.1.8.1 (usr: COMMITTED, root:

UNIX AIX
1

dears

i am trying to upgrade the TL from TL7 to TL8 and i facing this issue AIX6.1

 << End of Success Section >>
  
+-----------------------------------------------------------------------------+
                   BUILDDATE Verification ...
+-----------------------------------------------------------------------------+
Verifying build dates...
0503-466 installp: The build date requisite check failed for fileset     bos.net.nfs.client.
Installed fileset build date is 1043.  Selected fileset does not have a build date, but one is required.
0503-466 installp: The build date requisite check failed for fileset     bos.net.nfs.client.
Installed fileset build date is 1044.  Selected fileset does not have a build date, but one is required.
0503-466 installp: The build date requisite check failed for fileset     bos.net.nfs.client.
Installed fileset build date is 1048.  Selected fileset does not have a build date, but one is required.
0503-466 installp: The build date requisite check failed for fileset     bos.net.nfs.client.
Installed fileset build date is 1141.  Selected fileset does not have a build date, but one is required.
0503-466 installp: The build date requisite check failed for fileset     bos.net.nfs.client.
Installed fileset build date is 1207.  Selected fileset does not have a build date, but one is required.
installp: Installation failed due to BUILDDATE requisite failure.

lppchk -v
lppchk:  The following filesets need to be installed or corrected to bring
         the system to a consistent state:
  bos.net.nfs.client 6.1.8.1              (usr: COMMITTED, root: not installed)
2

1) will bosboot build a boot image?
2) if yes, afterwards, try a force install of bos.net.nfs.client

(my vacation starts NOW - so I wont be back for a few days. If you have a support contract - open a PMR now!!)

3

There is an IBM report about a seemingly similar problem in AIX 7.1. The offered solution is to get a fix and/or download a new version of the update from a certain location.

I suggest you open a PMR as MichaelFelt already said, this is probably a bug in IBMs packaging.

I hope this helps.

bakunin