Data type mismatch error while running RT1.3 test about ondatra HOT 12 CLOSED

This is effectively the same issue as #45
We are still waiting on this PR openconfig/public#750 (comment)
But we can do a temporary workaround that is a workaround for the time being.

from ondatra.

Thanks Greg for sharing the details.
Please could you share the workaround.

from ondatra.

The latest merge should fix this issue. Please let me know if it does not.

from ondatra.

Hi Greg,

I have taken latest go.mod (github.com/openconfig/ondatra v0.0.0-20221202185001-1b90e33d211b) and still seeing issue.
Please could you let me know the workaround, i will update my locate repo .

Thanks,
Prabha

from ondatra.

@cprabha, I meant that the latest Ondatra commit has the fix. Can you update Ondatra independently of featureprofiles and try it? I can proceed to update featureprofiles separately.

from ondatra.

Hi Greg,

I have taken "git clone https://github.com/openconfig/ondatra" and updated
all files in "/root//go/pkg/mod/github.com/openconfig/[email protected] " .

Script is still failing, is there anything we need to update apart from ondatra files?

Thanks,
Prabha

from ondatra.

In your featureprofiles directory, can you run?

go get -u github.com/openconfig/ondatra
go mod tidy

from ondatra.

Hi Greg,

I tried steps which have shared and able to update ondatra repo.
But observed ATE RIB call did not retrieve prefix information , ( I could see ATE has received routes ). and test keeps failing but not with data type mismatch instead prefix not found error.

Thanks,
Prabha

from ondatra.

Hi Greg,

Is there a older version ondatra repo which does not have these changes ? which i can update in my go.mod and get passed log for this script ?

Thanks,
Prabha

from ondatra.

Hi Greg,

please could you help with this ?

Thanks,
Prabha

from ondatra.

@cprabha, I'm going to need more information to determine whether there is any problem here. Nothing changed with respect to the other logic, and the unit tests and other integration tests are still passing on our end. Could you please file a new issue that includes at least
(1) logging the path the value of rib.AfiSafi(oc.BgpTypes_AFI_SAFI_TYPE_IPV4_UNICAST).Ipv4Unicast().Neighbor(tc.ate.Port2Neighbor).AdjRibInPre().Route(prefix.v4, 0).AttrIndex() so I can see the fully-qualified path; and
(2) a screenshot of the learned info / received routes by the ATE. Thanks!

from ondatra.

Thanks @greg-dennis
I have opened #59 with the error and path details.
Please check.

Thanks,
Prabha

from ondatra.