Bug 5085

Summary: incorrect host used by systemtap in kepler
Product: [Yocto Project Subprojects] Eclipse Plugin Reporter: Alexandru Georgescu <alexandru.c.georgescu>
Component: eclipse-pluginAssignee: Jessica <jessica.zhang>
Status: VERIFIED WORKSFORME QA Contact:
Severity: normal    
Priority: Undecided CC: david.lerner26, ioanax.grigoropol, yp.ep.watcher, yp.watcher
Version: 1.5   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
systemtap
none
systemtap screenshot none

Description Alexandru Georgescu 2013-08-30 09:25:38 UTC
Created attachment 1451 [details]
systemtap

1. Prepare a kepler environment
2. Open Systemtap tool
3. Launch a core-image-sato-sdk (qemux86-64) image
3. Fill in all the data for creating a connection. Make sure you add the correct ip address for the remote host (e.g. 192.168.7.6)
4.Press ok


EXPECTED RESULT
4. SYstemtap script launches and connects to the qemu image

ACTUAL RESULT
4. The host used by systemtap is localhost, not the one specified in the previous window (192.168.7.6)
*see attachment
Comment 1 Jessica 2013-09-03 20:28:14 UTC
The connection is for ssh terminal to the local host which the crosstap script will be running, so it's behaving as expected
Comment 2 Alexandru Georgescu 2013-09-04 05:51:02 UTC
(In reply to comment #1)
> The connection is for ssh terminal to the local host which the crosstap
> script will be running, so it's behaving as expected

Actually crosstap runs from the local host and connects to the remote machine
e.g:  crosstap root@192.168.1.88 trace_open.stp

How am I supposed to connect to the qemu/remote_machine if I don't input it's address?
Comment 3 Jessica 2013-09-04 22:41:56 UTC
Alex,

The remote host ip is pass to crosstap script that'll be running from the opened local terminal, as I said, the window is really for openning the local terminal for running the crosstap script which we programatically pass over the remote host ip and crosstap script has the capability to do remote connection, etc.  I've attached the screenshot for crosstap, there you need to enter the remote host IP.  Everything is working as designed.
Comment 4 Jessica 2013-09-04 22:42:38 UTC
Created attachment 1461 [details]
systemtap screenshot
Comment 5 Alexandru Georgescu 2013-09-18 11:34:31 UTC
(In reply to comment #4)
> Created attachment 1461 [details]
> systemtap screenshot


If I specify the remote host with the IP of the QEMU image, e.g. 192.168.7.6 I get the error from the first attachment. In the error clearly says: connection name: 127.0.0.1 which is different from 192.168.7.6.
Comment 6 Jessica 2013-09-18 18:55:08 UTC
Alex,

I've tried again and it still works for me.  So for the window, you enter your qemu ip address for remote host and remote user as root?  when it comes up the local window, you enter your local user name to login to your local host e.g. jzhang, then it should open a local terminal, there, you should see the crosstap script is running and the output is coming back
Comment 7 Alexandru Georgescu 2013-11-20 14:03:30 UTC
(In reply to comment #6)
> Alex,
> 
> I've tried again and it still works for me.  So for the window, you enter
> your qemu ip address for remote host and remote user as root?  when it comes
> up the local window, you enter your local user name to login to your local
> host e.g. jzhang, then it should open a local terminal, there, you should
> see the crosstap script is running and the output is coming back

Verified. 
On the Juno version it didn't ask me for using the host user and passwd and this is why I opened the bug in the first place.
If this is the intended workflow, then I will mark this as verified.
Comment 8 Alexandru Georgescu 2013-11-20 14:07:43 UTC
*** Bug 5446 has been marked as a duplicate of this bug. ***