Carla was trying to verify one of her bugs 14850 and ran into this issue.
Here is the gist of the issue from Carla's email.
On DAS machine:
create a domain with the master-password set to "welcome1" using the command
asadmin create-domain --savemasterpassword true --passwordfile ~/passfile3 domain2
create an ssh node using
asadmin create-node-ssh --nodehost adc2190111 --installdir /scratch/gf/cmott/glassfish3 node2
create an instance (on instance machine). This works fine
asadmin create-instance --node node2 ins2
If I try to start ins2 I get an error which I expected.
On the instance machine I try to set the master password.
asadmin change-master-password --savemasterpassword true --nodedir /scratch/gf/cmott/glassfish3/glassfish/nodes node2
This seems to set the master-password and creates a file called master-password in the agent dir of the node node2
Now I see the following:
on the DAS if I try to start the instance using
asadmin start-instance ins2
I get a failure
on the instance machine if I try to start the instance using
asadmin start-local-instance ins2
I am prompted for the master password and it will start once that is supplied.
If I create a new instance on the instance machine using
asadmin create-local-instance --usemasterpassword true --host dhcp-santaclara22-1fl-west-10-132-181-59.usdhcp.oraclecorp.com --node node2 ins3
I am prompted for the master password and the instance is created.
If I try to start the instance using start-local-instance I am also prompted for the master password. asadmin start-local-instance ins3
I can't seem to start the instance without providing the master password as the instance is starting. This means that the user will not be able to administer the instances from a central location.
I thought that we should be able to start the instances without prompting if the master passwords were the same on both instance and the DAS. What am I missing?"