Replica Arbiter Set - mongodb

Question

I need to change my arbiter as AWS retiring my ec2 instance "Retiring: This instance is scheduled for retirement..."
So I need to change my arbiter server, I created a new server, added all the things that exist in that server as I already save AMI for that.
For changing the replica set members, I use the javascript slice method that mentioned in the official MongoDB documents
Set the configuration in the new variable
cfg = rs.conf()
Removing the member from the new variable
cfg.members.splice(2,1) //remove the third member that is not in use and need to change
Then Overwrite the replica set configuration document by using the following command:-
rs.reconfig(cfg)
myreplicaSetName:ARBITER> rs.status()
{
"set" : "myreplicaSetName",
"date" : ISODate("2019-12-10T06:49:35.584Z"),
"myState" : 7,
"term" : NumberLong(3),
"syncingTo" : "",
"syncSourceHost" : "",
"syncSourceId" : -1,
"heartbeatIntervalMillis" : NumberLong(2000),
"optimes" : {
"lastCommittedOpTime" : {
"ts" : Timestamp(1575960573, 1),
"t" : NumberLong(3)
},
"readConcernMajorityOpTime" : {
"ts" : Timestamp(1575960573, 1),
"t" : NumberLong(3)
},
"appliedOpTime" : {
"ts" : Timestamp(1575960573, 1),
"t" : NumberLong(3)
},
"durableOpTime" : {
"ts" : Timestamp(1575960573, 1),
"t" : NumberLong(3)
}
},
"members" : [
{
"_id" : 0,
"name" : "myhostname:port",
"health" : 1,
"state" : 1,
"stateStr" : "PRIMARY",
"uptime" : 120,
"optime" : {
"ts" : Timestamp(1575960573, 1),
"t" : NumberLong(3)
},
"optimeDurable" : {
"ts" : Timestamp(1575960573, 1),
"t" : NumberLong(3)
},
"optimeDate" : ISODate("2019-12-10T06:49:33Z"),
"optimeDurableDate" : ISODate("2019-12-10T06:49:33Z"),
"lastHeartbeat" : ISODate("2019-12-10T06:49:33.593Z"),
"lastHeartbeatRecv" : ISODate("2019-12-10T06:49:35.267Z"),
"pingMs" : NumberLong(0),
"lastHeartbeatMessage" : "",
"syncingTo" : "",
"syncSourceHost" : "",
"syncSourceId" : -1,
"infoMessage" : "",
"electionTime" : Timestamp(1554185040, 1),
"electionDate" : ISODate("2019-04-02T06:04:00Z"),
"configVersion" : 15
},
{
"_id" : 1,
"name" : "my2ndhostname:port",
"health" : 1,
"state" : 2,
"stateStr" : "SECONDARY",
"uptime" : 120,
"optime" : {
"ts" : Timestamp(1575960573, 1),
"t" : NumberLong(3)
},
"optimeDurable" : {
"ts" : Timestamp(1575960573, 1),
"t" : NumberLong(3)
},
"optimeDate" : ISODate("2019-12-10T06:49:33Z"),
"optimeDurableDate" : ISODate("2019-12-10T06:49:33Z"),
"lastHeartbeat" : ISODate("2019-12-10T06:49:33.592Z"),
"lastHeartbeatRecv" : ISODate("2019-12-10T06:49:34.289Z"),
"pingMs" : NumberLong(1),
"lastHeartbeatMessage" : "",
"syncingTo" : "myhostname:port",
"syncSourceHost" : "myhostname:port",
"syncSourceId" : 0,
"infoMessage" : "",
"configVersion" : 15
},
{
"_id" : 2,
"name" : "my3rdhostname:port",
"health" : 1,
"state" : 7,
"stateStr" : "ARBITER",
"uptime" : 312,
"syncingTo" : "",
"syncSourceHost" : "",
"syncSourceId" : -1,
"maintenanceMode" : 1,
"infoMessage" : "could not find member to sync from",
"configVersion" : 15,
"self" : true,
"lastHeartbeatMessage" : ""
}
],
"ok" : 1
}
Everything goes with the reconfig, firstly it shows OTHER when I added as ARbiter then when I login to mongodb in the arbiter server, it shows ARBITER too, so it means new ARBITER is successfully set. But why its shows in the
"infoMessage" : "could not find member to sync from",