[LU-2560] test: obdfilter-survey test_3a: hang at prompting for password Created: 02/Jan/13  Updated: 15/Mar/14  Resolved: 15/Mar/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.3.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Jay Lan (Inactive) Assignee: Minh Diep
Resolution: Won't Fix Votes: 0
Labels: None
Environment:

Server: 2.1.3-1nasS, centos 6.3, 2.6.32_279.2.1.el6
Client: 2.3.0-2nasC, sles11sp2, 3.0.42_0.7.3
1 mds, 2 oss, 2 clients.
git source: https://github.com/jlan/lustre-nas


Attachments: File naster_cfg.v1.sh     File obdfilter-survey_3a.tgz    
Severity: 3
Rank (Obsolete): 5986

 Description   

Attached are a tarball of logs, and the config file naster_cfg.v1.sh I used in testing:

service331 /usr/lib64/lustre/tests # RCLIENTS="service332" sh auster -D /var/acc-sm/test_logs -f naster_cfg.v1 -r -v obdfilter-survey --only 3a >> /var/acc-sm/obdfilter-survey/obdfilter-survey.output 2>&1
10.151.26.39@10.151.26.40's password:

IP addr 10.151.26.39 is the IP addr of ost1_HOST and 10.151.26.40 is the IP addr of ost2_HOST.



 Comments   
Comment by Peter Jones [ 03/Jan/13 ]

Minh

Could you please look into this one?

Thanks

Peter

Comment by Minh Diep [ 03/Jan/13 ]

Hi,

Have you made sure that you can ssh passwordless on all nodes?

Comment by Jay Lan (Inactive) [ 03/Jan/13 ]

Hi Minh,

On the password prompt below:
10.151.26.40@10.151.26.39's password:
Is 10.151.26.40 considered a user name?

10.151.26.39 is service361 and 10.151.26.40 is service362.
I just tried ssh between each other and all fine. However, 10.151.26.40 is not a known user name though, if my assumption is right.

Comment by Jay Lan (Inactive) [ 03/Jan/13 ]

To answer your question, Minh, I tried to do ssh from any one of the 5 systems in my test environment to the other four systems, all went through without asking for password.

Comment by John Fuchs-Chesney (Inactive) [ 08/Mar/14 ]

Jay – is this still a live issue for you?
If not, may I mark it as resolved?
Thanks,
~ jfc.

Comment by Jay Lan (Inactive) [ 10/Mar/14 ]

Please close it.

No longer interested in 2.3.0 client + 2.1.3 server.

We do not see this problem in production with 2.1.5 server or
2.4.1 server.

Comment by John Fuchs-Chesney (Inactive) [ 15/Mar/14 ]

Closed per direction of customer.

Generated at Sat Feb 10 01:26:14 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.