Upgrade is failing from R81.10 to R82

[Blason_R]

Hi Team,

I am trying to upgrade the management server from R81.10 to R82 using migrate import export. The regular upgrade process is failing hence went for migrate import/export.

However this one is failing as well, any clue?

Failed reading json object: [com.checkpoint.objects.CloudApplication,{_persistence_fetchGroup:null,dlesession:0,objId:019fe41c-278d-4773-9823-8b874b507584,checkPointObjId:null,folder:4e8dd6c3-043b-4a00-9388-88d6e72faea2,domainsPreset:null,permissionPrimitivePresetId:cd05a6d2-c552-38f8-a12c-4fcb830dec90,readPrimitiveId:f9430bdc-ed67-3d06-b914-e2d7b62c189e,domainId:41e821a0-3720-11e3-aa6e-0800200c9fde,metaInfo:[com.checkpoint.management.dlecommon.ngm_api.MetaInfoForTopLevel,{_persistence_fetchGroup:null,metaOwned:false,newObject:false,lockStateResponse:null,validationState:OK,deletable:true,renameable:true,lastModifytime:[java.util.Date,1728914404540],lastModifier:System,creationTime:[java.util.Date,1697378222291],creator:System}],featuresPreset:null,features:null,tags:[java.util.HashSet,[]],systemTags:null,actions:null,dynamicFeatures:null,objectValidationState:null,dynamicContent:null,name:f3c33ab4-d032-4bba-944b-096c59777636,icon:General/globalsNa,color:BLACK,comments:,displayName:,customFields:null,accessKey:fKKgAey+G193LTPoEFPM0HEHPl73/9rqQvUSlH8U1nI=,clientId:164c018c-0023-4fd6-af3b-7edcdb987246,baseUrl:,mgmtInstancePath:,authPath:,keyExpiration:[java.util.Date,1760450404156],lastConnected:null,cloudTenantId:,cloudAppStatus:INIT_CONNECTED,tunnelEncKey:}]

[the_rock]

Just curious, why did regular upgrade fail?

Andy

[Blason_R]

Filesystem not compliant with checkpoint standard

[the_rock]

Not sure if below sk might be related..

Andy

https://support.checkpoint.com/results/sk/sk180769

[Kryten]

We had a similar Issue when upgrading from R81.10 to EA R82. It turned out to be the filesystem as well and for us the solution was to do a clean install of R81.10, which changed the filesystem to XFS. Upgrading from older versions keeps the ext3 filesystem, only a clean install will change it.

[JH_Ranger]

I also prefer doing clean installs when upgrading to R81.20 or R82. If you have an open-server on VMWare, then R81.20/R82 won't be compatible with multiple virtual disks anyway, so a clean install will be the only way forward (the_rock mentioned the relevant SK in the post above).

[the_rock]

Yea...sometimes clean install is needed.

Andy

[Itai_Minuhin]

Hi, 

My name is Itai and I'm a group manager in Check Point R&D. My team is responsible for the management server upgrade. 

I'm sorry for your bad upgrade experience, I will be glad to assist. 

If you are willing to share the upgrade logs, we will review them, try to pinpoint the issue and get back to you. 

The logs are stored on your management server at the following path, you can email them to me

• /var/log/upgrade-export.<time stamp>.tgz
• /var/log/upgrade-import.<time stamp>.tgz

Also, its very likely that the in-place upgrade attempt and export-import attempt have failed due to the same issue, since both processes are very similar under the hood. 

Thanks, 

Itai 

[Bob_Zimmerman]

I'm pretty sure '$FWDIR/bin/upgrade_tools/migrate export' and import are only used to move between two systems at the same version (e.g, physical server running R81.10 to a newer physical server running R81.10). You have to use '$FWDIR/scripts/migrate_server export' and import to move between versions.

[Blason_R · Accepted solution]

Well we installed the latest HFA and then tried for upgrade which went successful Thanks everyone for your inputs.

[the_rock]

Nice work!