The actual value computed by md5 isn't that important; even in recon
it's only used as an opaque identifier that assumed to be consistent
across nodes for the same file.
However the way these tests were written with hard coded md5 values
makes them brittle to changes in the RingData format and susceptible
to the burden of needless unrelated test maintenance churn.
e.g.
Related-Change: I23b5e0a8082b30ca257aeb1fab03ab74e6f0b2d4
Change-Id: I9623752c3cd2361f57864f3e938e1baf5e9292d7
053b625f42