Due to difference in GPDB 5.x and GPDB 6.x, there are functions that are on 5.x and not available on 6.x, therefore they can not be used and can cause a failure during the upgrade.
Most of these are captured in the gpupgrade initialize state.
However, CAST that are created by the user and not the system in the pg_catalog schema are not checking during this state. Therefore the gpupgrade initialize will pass but the gpupgrade execute will fail. To move forward you need to revert the upgrade and drop these CASTS from the source.
To get a list of CASTS that need to be dropped please run this query in the DB.
SELECT c.oid AS castoid,
c.castsource::regtype,
c.casttarget::regtype,
c.castfunc::regprocedure
FROM pg_cast c
JOIN pg_proc p ON (c.castfunc = p.oid)
WHERE p.pronamespace = 11 -- 11 is pg_catalog
AND c.oid >= 16384;