@Afroz Baig
Firstly you really don't need to modify manually the krb5.conf as they MUST be identical on all the cluster nodes. What you should do is run scp from the Ambari server where you configured the passwordless connection.
Assuming your Ambari Server hosts file entry has all the cluster node and egdenode1 is your target
# scp /etc/krb5.conf root@edgnode1:/etc/
This will copy and overwrite the incorrect krb5.conf on the edge node. Assuming you have a user named analyst01 on the edge node who intends to run a job after the update you will do the following as user analyst1 assuming he has his keytab in his home directory
# su - analyst01
To determine if he has a valid ticket, in the below he didn't have one
# klist
klist: No credentials cache found (filename: /tmp/krb5cc_0)
Grab a ticket
$ kinit -kt /home/analyst01/analyst01.keytab
Now he should be able to grab a valid ticket and the klist should validate that
$ klist
Ticket cache: FILE:/tmp/krb5cc_1013
Default principal: analyst01-xxx@{REALM}
Valid starting Expires Service principal
04/13/2019 23:25:32 04/14/2019 23:25:32 krbtgt/_host@{REALM}
04/13/2019 23:25:32 04/14/2019 23:25:32 HTTP/_host@{REALM}You don't need to restart any services on the edge node !
