Bug 10008

Summary: [Test Case 25] connection to Target can not be carried out
Product: [Yocto Project Subprojects] Eclipse Plugin Reporter: David Rodriguez <david.israelx.rodriguez.castellanos>
Component: eclipse-pluginAssignee: Jose Perez C <jose.perez.carranza>
Status: RESOLVED NOTABUG QA Contact: Humberto Ibarra <humberto.ibarra.lopez>
Severity: normal    
Priority: Medium CC: brian.avery, ioanax.grigoropol, jose.perez.carranza, sgw, yp.ep.watcher, yp.watcher
Version: 2.2   
Target Milestone: 2.2 M3   
Hardware: x86   
OS: x86_64   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
Physical DUT ssh dialog box
none
qemu ssh dialog box none

Description David Rodriguez 2016-07-22 20:24:22 UTC
Created attachment 3309 [details]
Physical DUT ssh dialog box

STATUS: FAILED
BUILD: 2.2_M2 : 36feb38045b7a2af86ece147fec54b0db3bf491f
ENVIRONMENT: Mars on Fedora 22 x86_64
STEPS TO REPRODUCE: 

1-In Eclipse, switch to Remote System Explorer to create a connection based on SSH, input the remote target IP address as the Host name, make sure disable the proxy in Window->Preferences->General->Network Connection, set Direct as Active Provider field.

2-Configure connection from Eclipse: Run->Run Configurations->C/C++ Remote Application\<Yocto_Image>->New Connection->General->SSH Only

3-Then right click to connect, input the user ID and password (optional).

4-expand the connection, it will show the Sftp Files etc.

EXPECTED OUTCOME: 
Connection to Target cannot be carried out following the steps in Test case 25, 
in active qemu machine or either physical DUT in the same Host Network. Attached are screen capture.
Comment 1 David Rodriguez 2016-07-22 20:25:45 UTC
Created attachment 3310 [details]
qemu ssh dialog box
Comment 2 David Rodriguez 2016-07-22 20:30:56 UTC
*In description  where says "EXPECTED OUTCOME:" should be say "OBTAINED RESULT:"
Comment 3 brian avery 2016-07-25 23:50:15 UTC
Questions:
1) Can you log into the qemu instance from a bash shell?
2) the xterm that is popped up shows a last line that has something like:
rw ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=256M oprofile.time=1

Does the ip address you are connecting to match the one in the "last line"  It looks like eclipse is not always cleaning up the old qemu instances in which case, running it again will result in the qemu instance incrementing the ip to .4, .6 ... etc.
Comment 4 Saul Wold 2016-07-28 14:47:29 UTC
Please provide the requested info.
Comment 5 David Rodriguez 2016-07-29 16:12:16 UTC
(In reply to comment #3)
1)Yes, I can.
2)the ip in this case for qemux86 machine is 
ip:192.168.7.2 Bcast: 192.168.7.255 Mask:255.255.255.0

To be more specific:

ENVIRONMENT: Mars on Fedora 22 x86_64

Connection is set up in a clean new connection configuration as step 2 at Description says, to connect either a qemux86 machine (qemu machine is run independently from a clean poky/build/environment-runqemu), or to a physical DUT (NUC6i5SYH) on the network (10.219.106.148, booted in a genericx-64 image). 

ssh service is restart successfully with "service sshd restart" on host before try to connect it. The attached screenshot (Physical DUT ssh dialog box) shows a pop window asking for a password, it does not accept any, and connection is not possible because of that, in both scenarios. The other screen shoot shows an error I couldn't reproduce.

Thanks.
Comment 6 David Rodriguez 2016-07-29 16:22:37 UTC
Changing status of the bug. :$
Comment 7 brian avery 2016-08-30 16:19:10 UTC
Thanks for the screenshot. It helps clarify what's happening.

1) the ssh connection needs to be root@<ip address>, NOT username@<ip address>
2) For the std sdk image the password for root is empty.
Please retry it with  the correct credentials.
Comment 8 Humberto Ibarra 2016-09-01 14:56:23 UTC
Brian is right, this required 'root' to set the connection correctly. Tried this out last week during the most recent master run and it works as expected. I could set the connection from terminal and from eclipse too, via Remote System Explorer.

I think this should be closed.
Comment 9 Jose Perez C 2016-09-01 15:00:25 UTC
based on previous bug this is not a bug.
Comment 10 Jose Perez C 2016-09-01 15:04:55 UTC
(In reply to comment #9)
> based on previous bug this is not a bug.

*Based on previews comment Comment 8