Everywhere, except s4, the user_newtalk indexes are renamed to have `un_` prefix but these drifts from the code has been reported for s4 only:
```lang=json
"user_newtalk un_user_id index-mismatch-code-extra": {
"s4": [
"db1138.eqiad.wmnet",
"db1097.eqiad.wmnet",
"db1081.eqiad.wmnet",
"db1091.eqiad.wmnet",
"db1121.eqiad.wmnet",
"db1103.eqiad.wmnet",
"db1084.eqiad.wmnet"
]
},
"user_newtalk un_user_ip index-mismatch-code-extra": {
"s4": [
"db1138.eqiad.wmnet",
"db1097.eqiad.wmnet",
"db1081.eqiad.wmnet",
"db1091.eqiad.wmnet",
"db1121.eqiad.wmnet",
"db1103.eqiad.wmnet",
"db1084.eqiad.wmnet"
]
},
"user_newtalk user_id index-mismatch-prod-extra": {
"s4": [
"db1138.eqiad.wmnet",
"db1097.eqiad.wmnet",
"db1081.eqiad.wmnet",
"db1091.eqiad.wmnet",
"db1121.eqiad.wmnet",
"db1103.eqiad.wmnet",
"db1084.eqiad.wmnet"
]
},
"user_newtalk user_ip index-mismatch-prod-extra": {
"s4": [
"db1138.eqiad.wmnet",
"db1097.eqiad.wmnet",
"db1081.eqiad.wmnet",
"db1091.eqiad.wmnet",
"db1121.eqiad.wmnet",
"db1103.eqiad.wmnet",
"db1084.eqiad.wmnet"
]
}
```
It seems {T234066} was not completely done and this somehow fell into cracks.