OSPF packet types are different from OSPF LSA types.
LSA’s are represented by one of these packet types.
Check out the diagram to get a better understanding for the different types of OSPF packet types.

OSPF Packet Types

Step 1: Hello packet received from a neighbor router causes an OSPF interface to be in INIT STATE regardless of other variables at this point. Hello packet contains things like (a) router-id (b) area id (c) AuthType (d) authentication (e)Netmask (f)Hello Int (g)Dead Int (h)DR (i)BDR (g) Neighbor IP
Step 2 (optional):  If its a broadcast/multiaccess environment, the interface will go into TWO-WAY state to see who will be the DR (designated router) and BDR (backup designated router) based on the info provided in the HELLO packet. This can also be triggered by receiving a DBD packet.
Step 3 (optional): EXSTART state on the interface is when its OK to start exchanging topological databases between neighbors after DR/BDR is determined.
Step 4: EXCHANGE state is the actual “exchange” of databases using the database descriptor packet.
Step 5: LOADING state, based on the DBD packets received. Some parts of the database might be out-of-date so then the Router sends link-state requests, updates, and acknowledgements to make sure everything is all synchronized between the two neighbors and databases match up. The meaning is pretty straight forward, request is a request for an LSA-type 1,2,3,4,5, or 7. Update is when the router provides the actual route prefix/mask/area info, and Acknowledgement is when it tells the neighbor “OK I received your packet in good condition”.
Step 6: FULL state, databases are all up to date and synchronized with all the other routers in the area topology, good to go for inserting routes into the forwarding table now!