smpatch entitlement permissions?
I was wondering if I could get some clarification on why this error is occurring:
# smpatch update -i 124258-03
Error: One or more of the updates specified do not have entitlement permissions.
This occurs with several patches, on several systems that connect to a LPS to receive patches. The one above happens to be a ufs/nfs patch. If I try to update with a list of patches, the whole operation fails because "One or more" of the patches do not have entitlement permissions.
Here are some more patches this shows up with:
125731-01XML and XSLT libraries patch
125329-02libsldap.so.1 patch
125118-01netstat patch
125114-01cpustat patch
124252-02nfssrv patch
[718 byte] By [
cbcrawfoa] at [2007-11-27 3:09:26]
# 1
The error may be occurring because the system is not getting the correct entitlement tokens. Does the error also occur on the LPS?
To verify which entitlement tokens the system is receiving, run the command:
# cat /var/sadm/spool/cache/entitlement/*title*
The ouput should look something like:
-START-ENTITLEMENT-TOKENS-
Solaris10
SolarisAllUpdates
Solaris10Security
SolarisSecurityUpdates
Solaris10Security
SolarisSecurityUpdates
SolarisDataIntegrityUpdates
SolarisHardwareUpdates
SolarisUtilityUpdates
Public
--END-ENTITLEMENT-TOKENS--
Specifically, SolarisAllUpdates and Public should be present. Have there been any changes recently such as re-registering the LPS or contract renewals?
# 2
I recently had to re-register the LPS server because it was giving me errors mentioning that it could not complete authorization, you may need to re-register the system.
It looks like I'm missing SolarisAllUpdates at least for the entitlement tokens:
# cat /var/sadm/spool/cache/entitlement/*title*
-START-ENTITLEMENT-TOKENS-
Solaris10Security
SolarisSecurityUpdates
SolarisDataIntegrityUpdates
SolarisHardwareUpdates
SolarisUtilityUpdates
Public
--END-ENTITLEMENT-TOKENS--
The error also occurs on the LPS (when connecting to itself and directly to Sun).
I'm guessing I didn't re-register the system correctly...
# 3
It may be worth trying to re-register the system again using the commands below. If you have more than one support contract, try using a different subscription key in the registration profile. Note that the cacaoadm commands are for Solaris 10 6/06 or later.
# cacaoadm stop
# cacaoadm status
# /usr/lib/cc-ccr/bin/eraseCCRRepository
# rm /var/scn/persistence/SCN*
# sconadm register -a -r <registration profile>
