messed up default in a vrf

Problem was that servers in a vrf that used a stub area could not reach outside the VRF. The default routes were messed up they were pointing not to the exit but to themselves. I knew this was an area 0 problem as you get a default route when you have a connection to area 0.

The flip side is that when you are setting up a VRF the box that you want to originate has to have 1 interface in area 0 to force the advertisement of a default route

Looking in one of the switches i see that there is an area 0 there. This is not correct there is not supposed to be one. 

 Routing Process 100 with ID 10.202.255.7 VRF up
Area BACKBONE(0.0.0.0) (Inactive)
        Area has existed for 1w0d
        Interfaces in this area: 1 Active interfaces: 1
        Passive interfaces: 1  Loopback interfaces: 0
        No authentication available
        SPF calculation has run 2 times
         Last SPF ran for 0.000125s
        Area ranges are
        Number of LSAs: 90, checksum sum 0x2e88fb
   Area (0.0.0.202)
        Area has existed for 2y9w
        Interfaces in this area: 22 Active interfaces: 21
        Passive interfaces: 19  Loopback interfaces: 1
        This area is a STUB area
        Generates stub default route with cost 1
        No authentication available
        SPF calculation has run 690 times
         Last SPF ran for 0.003378s
        Area ranges are
        Number of LSAs: 31, checksum sum 0xeb8bc

So now need to find the bad interface I just need to know which interface is in area 0 so I can fix it

sho ip ospf int vrf up | inc Vlan|area
 Vlan6626 is up, line protocol is up
    IP address 10.10.10.2/23, Process ID 100 VRF backup, area 0.0.0.0

so fixing the ospf area statement under the SVI (this was NX-OS) fixes the problem.