Hi Team,
Facing an issue while unpack the overlay in some custom location other than "/" directory. From the LAVA linaro documentation I came to know that the -C / command to tar is essential or the test shell will not be able to start. Below are the issues that I am facing because of this.
* My / directory is a read only one and I want it in some /etc or /var. * The LAVA job is getting stuck while doing the unpack with the command below in job definition.
transfer_overlay:
download_command: cd /tmp; wget
unpack_command: tar -C /tmp -xzf
Below I am attaching the test log from LAVA.
[cid:image001.png@01D9455A.1AD8F6A0]
How we can solve the read only filesystem image issue for unpacking the overlay other than "/" directory ?
Regards, Sarath P T
Hi Team,
Any solution for the issue that I pointed here ? I tried below change as well 1) Changed the source code "/usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py" with "/var/lava-%s " custom path
debian = { "TESTER_PS1": r"linaro-test [rc=$(echo $?)]# ", "TESTER_PS1_PATTERN": r"linaro-test [rc=(\d+)]# ", "TESTER_PS1_INCLUDES_RC": True, "boot_cmds": "boot_cmds", "line_separator": "\n", # for lava-test-shell "distro": "debian", "tar_flags": "--warning no-timestamp", "lava_test_sh_cmd": "/bin/bash", "lava_test_dir": "/var/lava-%s", "lava_test_results_part_attr": "root_part", "lava_test_results_dir": "/var/lava-%s", "lava_test_shell_file": "~/.bashrc", }
Status of the change : The overlay unpack is not happening in the specific directory that we applied to lava_test_dir and lava_test_results_dir.
I would appreciate it if you could send the solution of the issue that I raised here.
Regards, Sarath P T
From: P T, Sarath Sent: 20 February 2023 18:35 To: 'lava-users@lists.lavasoftware.org' lava-users@lists.lavasoftware.org Subject: Not able to unpack the overlay other than "/" directory
Hi Team,
Facing an issue while unpack the overlay in some custom location other than "/" directory. From the LAVA linaro documentation I came to know that the -C / command to tar is essential or the test shell will not be able to start. Below are the issues that I am facing because of this.
* My / directory is a read only one and I want it in some /etc or /var. * The LAVA job is getting stuck while doing the unpack with the command below in job definition.
transfer_overlay:
download_command: cd /tmp; wget
unpack_command: tar -C /tmp -xzf
Below I am attaching the test log from LAVA.
[cid:image001.png@01D94B9F.0FBC1D10]
How we can solve the read only filesystem image issue for unpacking the overlay other than "/" directory ?
Regards, Sarath P T
Sarah,
It's hard to debug without the testjob definition. Could you post this here?
Best Regards, Milosz
On Tue, Feb 28, 2023 at 1:00 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Team,
Any solution for the issue that I pointed here ? I tried below change as well
- Changed the source code
*“/usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py”* with *“/var/lava-%s “* custom path
*debian = {*
"TESTER_PS1": r"linaro-test [rc=$(echo $?)]# ",*
"TESTER_PS1_PATTERN": r"linaro-test [rc=(\d+)]# ",*
"TESTER_PS1_INCLUDES_RC": True,*
"boot_cmds": "boot_cmds",*
"line_separator": "\n",*
# for lava-test-shell*
"distro": "debian",*
"tar_flags": "--warning no-timestamp",*
"lava_test_sh_cmd": "/bin/bash",*
"lava_test_dir": "/var/lava-%s",*
"lava_test_results_part_attr": "root_part",*
"lava_test_results_dir": "/var/lava-%s",*
"lava_test_shell_file": "~/.bashrc",*
*} Status of the change :* The overlay unpack is not happening in the specific directory that we applied to *lava_test_dir *and *lava_test_results_dir.*
I would appreciate it if you could send the solution of the issue that I raised here.
Regards,
Sarath P T
*From:* P T, Sarath *Sent:* 20 February 2023 18:35 *To:* 'lava-users@lists.lavasoftware.org' < lava-users@lists.lavasoftware.org> *Subject:* Not able to unpack the overlay other than "/" directory
Hi Team,
Facing an issue while unpack the overlay in some custom location other than “/” directory. From the LAVA linaro documentation I came to know that the -C / command to tar is essential or the test shell will not be able to start. Below are the issues that I am facing because of this.
- My / directory is a read only one and I want it in some /etc or
/var.
- The LAVA job is getting stuck while doing the unpack with the
command below in job definition.
*transfer_overlay:*
download_command: cd /tmp; wget*unpack_command: tar -C /tmp -xzf Below I am attaching the test logfrom LAVA.*
How we can solve the read only filesystem image issue for unpacking the overlay other than “/” directory ?
Regards, Sarath P T
Lava-users mailing list -- lava-users@lists.lavasoftware.org To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
Hi Milosz,
Below I am attaching the test job definition which I used.
priority: high visibility: public device_type: industrial-mtda-simatic-ipc227e-02 tags: - slll-industrial-mtda-simatic-ipc227e-02 visibility: public timeouts: job: minutes: 20 action: minutes: 10 connection: hours: 1 job_name: slll_simatic_swupdate_test actions: - deploy: to: overlay os: debian - boot: method: minimal reset: true failure_retry: 2 auto_login: login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: root prompts: - 'root@ebsy-isar:~#' transfer_overlay: download_command: cd /var ; sleep 10; wget; unpack_command: tar -C /var -xzf - test: definitions: - repository: http://<ip_addr_of_host>/linux-qa-suites.tar.gzhttp://%3cip_addr_of_host%3e/linux-qa-suites.tar.gz from: url path: linux-qa-suites/automated/eps-test/linux_kernel/linux_kernel.yaml name: linux_kernel compression: gz metadata: Description: '"Lava jobs for simatic-ipc277e swupdate test check"' context: arch: x86
Regards, Sarath P T From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 19:28 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Sarah,
It's hard to debug without the testjob definition. Could you post this here?
Best Regards, Milosz
On Tue, Feb 28, 2023 at 1:00 PM P T, Sarath <Sarath_PT@mentor.commailto:Sarath_PT@mentor.com> wrote:
Hi Team,
Any solution for the issue that I pointed here ? I tried below change as well 1) Changed the source code “/usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py” with “/var/lava-%s “ custom path
debian = { "TESTER_PS1": r"linaro-test [rc=$(echo $?)]# ", "TESTER_PS1_PATTERN": r"linaro-test [rc=(\d+)]# ", "TESTER_PS1_INCLUDES_RC": True, "boot_cmds": "boot_cmds", "line_separator": "\n", # for lava-test-shell "distro": "debian", "tar_flags": "--warning no-timestamp", "lava_test_sh_cmd": "/bin/bash", "lava_test_dir": "/var/lava-%s", "lava_test_results_part_attr": "root_part", "lava_test_results_dir": "/var/lava-%s", "lava_test_shell_file": "~/.bashrc", }
Status of the change : The overlay unpack is not happening in the specific directory that we applied to lava_test_dir and lava_test_results_dir.
I would appreciate it if you could send the solution of the issue that I raised here.
Regards, Sarath P T
From: P T, Sarath Sent: 20 February 2023 18:35 To: 'lava-users@lists.lavasoftware.orgmailto:lava-users@lists.lavasoftware.org' <lava-users@lists.lavasoftware.orgmailto:lava-users@lists.lavasoftware.org> Subject: Not able to unpack the overlay other than "/" directory
Hi Team,
Facing an issue while unpack the overlay in some custom location other than “/” directory. From the LAVA linaro documentation I came to know that the -C / command to tar is essential or the test shell will not be able to start. Below are the issues that I am facing because of this.
* My / directory is a read only one and I want it in some /etc or /var. * The LAVA job is getting stuck while doing the unpack with the command below in job definition.
transfer_overlay:
download_command: cd /tmp; wget
unpack_command: tar -C /tmp -xzf
Below I am attaching the test log from LAVA.
[cid:image001.png@01D94BAE.5A7E2730]
How we can solve the read only filesystem image issue for unpacking the overlay other than “/” directory ?
Regards, Sarath P T
_______________________________________________ Lava-users mailing list -- lava-users@lists.lavasoftware.orgmailto:lava-users@lists.lavasoftware.org To unsubscribe send an email to lava-users-leave@lists.lavasoftware.orgmailto:lava-users-leave@lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
This is what I have in my jobs and it works for me. Context should include lava_test_results_dir
context: lava_test_results_dir: "/home/fio/lava-%s"
Then in the boot/transfer_overlay: transfer_overlay: download_command: cd /tmp ; wget unpack_command: tar -C / -xzf
Hope this helps.
Best Regards, Milosz
On Tue, Feb 28, 2023 at 3:17 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Below I am attaching the test job definition which I used.
priority: high
visibility: public
device_type: industrial-mtda-simatic-ipc227e-02
tags:
- slll-industrial-mtda-simatic-ipc227e-02
visibility: public
timeouts:
job:
minutes: 20action:
minutes: 10connection:
hours: 1job_name: slll_simatic_swupdate_test
actions:
deploy:
to: overlay
os: debian
boot:
method: minimal
reset: true
failure_retry: 2
auto_login:
login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: rootprompts:
- 'root@ebsy-isar:~#'
transfer_overlay:
download_command: cd /var ; sleep 10; wget; unpack_command: tar -C /var -xzftest:
definitions:
repository: http://<ip_addr_of_host>/linux-qa-suites.tar.gz
from: url
path: linux-qa-suites/automated/eps-test/linux_kernel/linux_kernel.yaml
name: linux_kernel
compression: gz
metadata:
Description: '"Lava jobs for simatic-ipc277e swupdate test check"'
context:
arch: x86
Regards,
Sarath P T
From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 19:28 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Sarah,
It's hard to debug without the testjob definition. Could you post this here?
Best Regards,
Milosz
On Tue, Feb 28, 2023 at 1:00 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Team,
Any solution for the issue that I pointed here ? I tried below change as well
- Changed the source code “/usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py” with “/var/lava-%s “ custom path
debian = {
"TESTER_PS1": r"linaro-test [rc=$(echo \$?)]# ", "TESTER_PS1_PATTERN": r"linaro-test \[rc=(\d+)\]# ", "TESTER_PS1_INCLUDES_RC": True, "boot_cmds": "boot_cmds", "line_separator": "\n", # for lava-test-shell "distro": "debian", "tar_flags": "--warning no-timestamp", "lava_test_sh_cmd": "/bin/bash", "lava_test_dir": "/var/lava-%s", "lava_test_results_part_attr": "root_part", "lava_test_results_dir": "/var/lava-%s", "lava_test_shell_file": "~/.bashrc",}
Status of the change : The overlay unpack is not happening in the specific directory that we applied to lava_test_dir and lava_test_results_dir.
I would appreciate it if you could send the solution of the issue that I raised here.
Regards,
Sarath P T
From: P T, Sarath Sent: 20 February 2023 18:35 To: 'lava-users@lists.lavasoftware.org' lava-users@lists.lavasoftware.org Subject: Not able to unpack the overlay other than "/" directory
Hi Team,
Facing an issue while unpack the overlay in some custom location other than “/” directory. From the LAVA linaro documentation I came to know that the -C / command to tar is essential or the test shell will not be able to start. Below are the issues that I am facing because of this.
My / directory is a read only one and I want it in some /etc or /var. The LAVA job is getting stuck while doing the unpack with the command below in job definition.
transfer_overlay:
download_command: cd /tmp; wget unpack_command: tar -C /tmp -xzfBelow I am attaching the test log from LAVA.
How we can solve the read only filesystem image issue for unpacking the overlay other than “/” directory ?
Regards, Sarath P T
Lava-users mailing list -- lava-users@lists.lavasoftware.org To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
Hi Milosz,
Thanks for your reply. I have tried below scenario and could able to succeed with the overlay download in a different directory. But the unpack is still not taking in the "/" directory as I am having the read only image. So we have tried in the /etc directory cause its writable and I am showing the test job definition snippet below which I used.
context: lava_test_results_dir: "/etc/lava-%s"
Then in the boot/transfer_overlay: transfer_overlay: download_command: cd /etc ; wget unpack_command: tar -C /etc -xzf
Result status: The test job got stuck after the overlay download and did not proceed with the unpack.
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 20:57 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
This is what I have in my jobs and it works for me. Context should include lava_test_results_dir
context: lava_test_results_dir: "/home/fio/lava-%s"
Then in the boot/transfer_overlay: transfer_overlay: download_command: cd /tmp ; wget unpack_command: tar -C / -xzf
Hope this helps.
Best Regards, Milosz
On Tue, Feb 28, 2023 at 3:17 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Below I am attaching the test job definition which I used.
priority: high
visibility: public
device_type: industrial-mtda-simatic-ipc227e-02
tags:
- slll-industrial-mtda-simatic-ipc227e-02
visibility: public
timeouts:
job:
minutes: 20action:
minutes: 10connection:
hours: 1job_name: slll_simatic_swupdate_test
actions:
deploy:
to: overlay
os: debian
boot:
method: minimal
reset: true
failure_retry: 2
auto_login:
login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: rootprompts:
- 'root@ebsy-isar:~#'
transfer_overlay:
download_command: cd /var ; sleep 10; wget; unpack_command: tar -C /var -xzftest:
definitions:
repository: http://<ip_addr_of_host>/linux-qa-suites.tar.gz
from: url
path:
linux-qa-suites/automated/eps-test/linux_kernel/linux_kernel.yaml
name: linux_kernel compression: gzmetadata:
Description: '"Lava jobs for simatic-ipc277e swupdate test check"'
context:
arch: x86
Regards,
Sarath P T
From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 19:28 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Sarah,
It's hard to debug without the testjob definition. Could you post this here?
Best Regards,
Milosz
On Tue, Feb 28, 2023 at 1:00 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Team,
Any solution for the issue that I pointed here ? I tried below change as well
- Changed the source code
“/usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py” with “/var/lava-%s “ custom path
debian = {
"TESTER_PS1": r"linaro-test [rc=$(echo \$?)]# ", "TESTER_PS1_PATTERN": r"linaro-test \[rc=(\d+)\]# ", "TESTER_PS1_INCLUDES_RC": True, "boot_cmds": "boot_cmds", "line_separator": "\n", # for lava-test-shell "distro": "debian", "tar_flags": "--warning no-timestamp", "lava_test_sh_cmd": "/bin/bash", "lava_test_dir": "/var/lava-%s", "lava_test_results_part_attr": "root_part", "lava_test_results_dir": "/var/lava-%s", "lava_test_shell_file": "~/.bashrc",}
Status of the change : The overlay unpack is not happening in the specific directory that we applied to lava_test_dir and lava_test_results_dir.
I would appreciate it if you could send the solution of the issue that I raised here.
Regards,
Sarath P T
From: P T, Sarath Sent: 20 February 2023 18:35 To: 'lava-users@lists.lavasoftware.org' lava-users@lists.lavasoftware.org Subject: Not able to unpack the overlay other than "/" directory
Hi Team,
Facing an issue while unpack the overlay in some custom location other than “/” directory. From the LAVA linaro documentation I came to know that the -C / command to tar is essential or the test shell will not be able to start. Below are the issues that I am facing because of this.
My / directory is a read only one and I want it in some /etc or /var. The LAVA job is getting stuck while doing the unpack with the command below in job definition.
transfer_overlay:
download_command: cd /tmp; wget unpack_command: tar -C /tmp -xzfBelow I am attaching the test log from LAVA.
How we can solve the read only filesystem image issue for unpacking the overlay other than “/” directory ?
Regards, Sarath P T
Lava-users mailing list -- lava-users@lists.lavasoftware.org To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
On Tue, Feb 28, 2023 at 3:43 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Thanks for your reply. I have tried below scenario and could able to succeed with the overlay download in a different directory. But the unpack is still not taking in the "/" directory as I am having the read only image. So we have tried in the /etc directory cause its writable and I am showing the test job definition snippet below which I used.
context: lava_test_results_dir: "/etc/lava-%s"
Then in the boot/transfer_overlay: transfer_overlay: download_command: cd /etc ; wget unpack_command: tar -C /etc -xzf
Result status: The test job got stuck after the overlay download and did not proceed with the unpack.
Did you try the job with the original unpack_command? The overlay is prepared on the dispatcher with the full absolute path to unpack. So with the job as you posted you'll end up with your files in /etc/etc/lava-0 ... This is not what LAVA expects and that's why you're getting stuck.
Best Regards, Milosz
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 20:57 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
This is what I have in my jobs and it works for me. Context should include lava_test_results_dir
context: lava_test_results_dir: "/home/fio/lava-%s"
Then in the boot/transfer_overlay: transfer_overlay: download_command: cd /tmp ; wget unpack_command: tar -C / -xzf
Hope this helps.
Best Regards, Milosz
On Tue, Feb 28, 2023 at 3:17 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Below I am attaching the test job definition which I used.
priority: high
visibility: public
device_type: industrial-mtda-simatic-ipc227e-02
tags:
- slll-industrial-mtda-simatic-ipc227e-02
visibility: public
timeouts:
job:
minutes: 20action:
minutes: 10connection:
hours: 1job_name: slll_simatic_swupdate_test
actions:
deploy:
to: overlay
os: debian
boot:
method: minimal
reset: true
failure_retry: 2
auto_login:
login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: rootprompts:
- 'root@ebsy-isar:~#'
transfer_overlay:
download_command: cd /var ; sleep 10; wget; unpack_command: tar -C /var -xzftest:
definitions:
repository: http://<ip_addr_of_host>/linux-qa-suites.tar.gz
from: url
path:
linux-qa-suites/automated/eps-test/linux_kernel/linux_kernel.yaml
name: linux_kernel compression: gzmetadata:
Description: '"Lava jobs for simatic-ipc277e swupdate test check"'
context:
arch: x86
Regards,
Sarath P T
From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 19:28 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Sarah,
It's hard to debug without the testjob definition. Could you post this here?
Best Regards,
Milosz
On Tue, Feb 28, 2023 at 1:00 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Team,
Any solution for the issue that I pointed here ? I tried below change as well
- Changed the source code
“/usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py” with “/var/lava-%s “ custom path
debian = {
"TESTER_PS1": r"linaro-test [rc=$(echo \$?)]# ", "TESTER_PS1_PATTERN": r"linaro-test \[rc=(\d+)\]# ", "TESTER_PS1_INCLUDES_RC": True, "boot_cmds": "boot_cmds", "line_separator": "\n", # for lava-test-shell "distro": "debian", "tar_flags": "--warning no-timestamp", "lava_test_sh_cmd": "/bin/bash", "lava_test_dir": "/var/lava-%s", "lava_test_results_part_attr": "root_part", "lava_test_results_dir": "/var/lava-%s", "lava_test_shell_file": "~/.bashrc",}
Status of the change : The overlay unpack is not happening in the specific directory that we applied to lava_test_dir and lava_test_results_dir.
I would appreciate it if you could send the solution of the issue that I raised here.
Regards,
Sarath P T
From: P T, Sarath Sent: 20 February 2023 18:35 To: 'lava-users@lists.lavasoftware.org' lava-users@lists.lavasoftware.org Subject: Not able to unpack the overlay other than "/" directory
Hi Team,
Facing an issue while unpack the overlay in some custom location other than “/” directory. From the LAVA linaro documentation I came to know that the -C / command to tar is essential or the test shell will not be able to start. Below are the issues that I am facing because of this.
My / directory is a read only one and I want it in some /etc or /var. The LAVA job is getting stuck while doing the unpack with the command below in job definition.
transfer_overlay:
download_command: cd /tmp; wget unpack_command: tar -C /tmp -xzfBelow I am attaching the test log from LAVA.
How we can solve the read only filesystem image issue for unpacking the overlay other than “/” directory ?
Regards, Sarath P T
Lava-users mailing list -- lava-users@lists.lavasoftware.org To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
Hi Milosz,
I have used original unpack_command as you suggested but still as read only image its get stuck in the overlay unpack. Below I am showing the context and transfer_overlay session that I used for that. And could you please share the sample staging job definition that you used with job context ?
context: arch: x86 lava_test_results_dir: "/etc/lava-%s"
transfer_overlay: download_command: sleep 10; cd /tmp; wget unpack_command: tar -C / -xzf
Status : The job is get stuck in the overlay unpack.
Regards, Sarath P T -----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 21:23 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
On Tue, Feb 28, 2023 at 3:43 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Thanks for your reply. I have tried below scenario and could able to succeed with the overlay download in a different directory. But the unpack is still not taking in the "/" directory as I am having the read only image. So we have tried in the /etc directory cause its writable and I am showing the test job definition snippet below which I used.
context: lava_test_results_dir: "/etc/lava-%s"
Then in the boot/transfer_overlay: transfer_overlay: download_command: cd /etc ; wget unpack_command: tar -C /etc -xzf
Result status: The test job got stuck after the overlay download and did not proceed with the unpack.
Did you try the job with the original unpack_command? The overlay is prepared on the dispatcher with the full absolute path to unpack. So with the job as you posted you'll end up with your files in /etc/etc/lava-0 ... This is not what LAVA expects and that's why you're getting stuck.
Best Regards, Milosz
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 20:57 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
This is what I have in my jobs and it works for me. Context should include lava_test_results_dir
context: lava_test_results_dir: "/home/fio/lava-%s"
Then in the boot/transfer_overlay: transfer_overlay: download_command: cd /tmp ; wget unpack_command: tar -C / -xzf
Hope this helps.
Best Regards, Milosz
On Tue, Feb 28, 2023 at 3:17 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Below I am attaching the test job definition which I used.
priority: high
visibility: public
device_type: industrial-mtda-simatic-ipc227e-02
tags:
- slll-industrial-mtda-simatic-ipc227e-02
visibility: public
timeouts:
job:
minutes: 20action:
minutes: 10connection:
hours: 1job_name: slll_simatic_swupdate_test
actions:
deploy:
to: overlay
os: debian
boot:
method: minimal
reset: true
failure_retry: 2
auto_login:
login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: rootprompts:
- 'root@ebsy-isar:~#'
transfer_overlay:
download_command: cd /var ; sleep 10; wget; unpack_command: tar -C /var -xzftest:
definitions:
repository: http://<ip_addr_of_host>/linux-qa-suites.tar.gz
from: url
path:
linux-qa-suites/automated/eps-test/linux_kernel/linux_kernel.yaml
name: linux_kernel compression: gzmetadata:
Description: '"Lava jobs for simatic-ipc277e swupdate test check"'
context:
arch: x86
Regards,
Sarath P T
From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 19:28 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Sarah,
It's hard to debug without the testjob definition. Could you post this here?
Best Regards,
Milosz
On Tue, Feb 28, 2023 at 1:00 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Team,
Any solution for the issue that I pointed here ? I tried below change as well
- Changed the source code
“/usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py” with “/var/lava-%s “ custom path
debian = {
"TESTER_PS1": r"linaro-test [rc=$(echo \$?)]# ", "TESTER_PS1_PATTERN": r"linaro-test \[rc=(\d+)\]# ", "TESTER_PS1_INCLUDES_RC": True, "boot_cmds": "boot_cmds", "line_separator": "\n", # for lava-test-shell "distro": "debian", "tar_flags": "--warning no-timestamp", "lava_test_sh_cmd": "/bin/bash", "lava_test_dir": "/var/lava-%s", "lava_test_results_part_attr": "root_part", "lava_test_results_dir": "/var/lava-%s", "lava_test_shell_file": "~/.bashrc",}
Status of the change : The overlay unpack is not happening in the specific directory that we applied to lava_test_dir and lava_test_results_dir.
I would appreciate it if you could send the solution of the issue that I raised here.
Regards,
Sarath P T
From: P T, Sarath Sent: 20 February 2023 18:35 To: 'lava-users@lists.lavasoftware.org' lava-users@lists.lavasoftware.org Subject: Not able to unpack the overlay other than "/" directory
Hi Team,
Facing an issue while unpack the overlay in some custom location other than “/” directory. From the LAVA linaro documentation I came to know that the -C / command to tar is essential or the test shell will not be able to start. Below are the issues that I am facing because of this.
My / directory is a read only one and I want it in some /etc or /var. The LAVA job is getting stuck while doing the unpack with the command below in job definition.
transfer_overlay:
download_command: cd /tmp; wget unpack_command: tar -C /tmp -xzfBelow I am attaching the test log from LAVA.
How we can solve the read only filesystem image issue for unpacking the overlay other than “/” directory ?
Regards, Sarath P T
Lava-users mailing list -- lava-users@lists.lavasoftware.org To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
On Tue, Feb 28, 2023 at 4:15 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
I have used original unpack_command as you suggested but still as read only image its get stuck in the overlay unpack. Below I am showing the context and transfer_overlay session that I used for that. And could you please share the sample staging job definition that you used with job context ?
Sure: https://lava.infra.foundries.io/scheduler/job/17490
The strange thing about your job is there is no command sent over serial to start overlay decompression. Like here: https://lava.infra.foundries.io/scheduler/job/17490#L3404
This one uses a slightly different overlay path, but it still works.
Best Regars, Milosz
context: arch: x86 lava_test_results_dir: "/etc/lava-%s"
transfer_overlay: download_command: sleep 10; cd /tmp; wget unpack_command: tar -C / -xzfStatus : The job is get stuck in the overlay unpack.
Regards, Sarath P T -----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 21:23 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
On Tue, Feb 28, 2023 at 3:43 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Thanks for your reply. I have tried below scenario and could able to succeed with the overlay download in a different directory. But the unpack is still not taking in the "/" directory as I am having the read only image. So we have tried in the /etc directory cause its writable and I am showing the test job definition snippet below which I used.
context: lava_test_results_dir: "/etc/lava-%s"
Then in the boot/transfer_overlay: transfer_overlay: download_command: cd /etc ; wget unpack_command: tar -C /etc -xzf
Result status: The test job got stuck after the overlay download and did not proceed with the unpack.
Did you try the job with the original unpack_command? The overlay is prepared on the dispatcher with the full absolute path to unpack. So with the job as you posted you'll end up with your files in /etc/etc/lava-0 ... This is not what LAVA expects and that's why you're getting stuck.
Best Regards, Milosz
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 20:57 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
This is what I have in my jobs and it works for me. Context should include lava_test_results_dir
context: lava_test_results_dir: "/home/fio/lava-%s"
Then in the boot/transfer_overlay: transfer_overlay: download_command: cd /tmp ; wget unpack_command: tar -C / -xzf
Hope this helps.
Best Regards, Milosz
On Tue, Feb 28, 2023 at 3:17 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Below I am attaching the test job definition which I used.
priority: high
visibility: public
device_type: industrial-mtda-simatic-ipc227e-02
tags:
- slll-industrial-mtda-simatic-ipc227e-02
visibility: public
timeouts:
job:
minutes: 20action:
minutes: 10connection:
hours: 1job_name: slll_simatic_swupdate_test
actions:
deploy:
to: overlay
os: debian
boot:
method: minimal
reset: true
failure_retry: 2
auto_login:
login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: rootprompts:
- 'root@ebsy-isar:~#'
transfer_overlay:
download_command: cd /var ; sleep 10; wget; unpack_command: tar -C /var -xzftest:
definitions:
repository: http://<ip_addr_of_host>/linux-qa-suites.tar.gz
from: url
path:
linux-qa-suites/automated/eps-test/linux_kernel/linux_kernel.yaml
name: linux_kernel compression: gzmetadata:
Description: '"Lava jobs for simatic-ipc277e swupdate test check"'
context:
arch: x86
Regards,
Sarath P T
From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 19:28 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Sarah,
It's hard to debug without the testjob definition. Could you post this here?
Best Regards,
Milosz
On Tue, Feb 28, 2023 at 1:00 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Team,
Any solution for the issue that I pointed here ? I tried below change as well
- Changed the source code
“/usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py” with “/var/lava-%s “ custom path
debian = {
"TESTER_PS1": r"linaro-test [rc=$(echo \$?)]# ", "TESTER_PS1_PATTERN": r"linaro-test \[rc=(\d+)\]# ", "TESTER_PS1_INCLUDES_RC": True, "boot_cmds": "boot_cmds", "line_separator": "\n", # for lava-test-shell "distro": "debian", "tar_flags": "--warning no-timestamp", "lava_test_sh_cmd": "/bin/bash", "lava_test_dir": "/var/lava-%s", "lava_test_results_part_attr": "root_part", "lava_test_results_dir": "/var/lava-%s", "lava_test_shell_file": "~/.bashrc",}
Status of the change : The overlay unpack is not happening in the specific directory that we applied to lava_test_dir and lava_test_results_dir.
I would appreciate it if you could send the solution of the issue that I raised here.
Regards,
Sarath P T
From: P T, Sarath Sent: 20 February 2023 18:35 To: 'lava-users@lists.lavasoftware.org' lava-users@lists.lavasoftware.org Subject: Not able to unpack the overlay other than "/" directory
Hi Team,
Facing an issue while unpack the overlay in some custom location other than “/” directory. From the LAVA linaro documentation I came to know that the -C / command to tar is essential or the test shell will not be able to start. Below are the issues that I am facing because of this.
My / directory is a read only one and I want it in some /etc or /var. The LAVA job is getting stuck while doing the unpack with the command below in job definition.
transfer_overlay:
download_command: cd /tmp; wget unpack_command: tar -C /tmp -xzfBelow I am attaching the test log from LAVA.
How we can solve the read only filesystem image issue for unpacking the overlay other than “/” directory ?
Regards, Sarath P T
Lava-users mailing list -- lava-users@lists.lavasoftware.org To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
Hi Milosz,
Yes it’s a strange behaviour that there is no command sent over serial to start overlay decompression. And is there any server configuration changes you made for accomplishing it ?
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 22:21 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
On Tue, Feb 28, 2023 at 4:15 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
I have used original unpack_command as you suggested but still as read only image its get stuck in the overlay unpack. Below I am showing the context and transfer_overlay session that I used for that. And could you please share the sample staging job definition that you used with job context ?
Sure: https://lava.infra.foundries.io/scheduler/job/17490
The strange thing about your job is there is no command sent over serial to start overlay decompression. Like here: https://lava.infra.foundries.io/scheduler/job/17490#L3404
This one uses a slightly different overlay path, but it still works.
Best Regars, Milosz
context: arch: x86 lava_test_results_dir: "/etc/lava-%s"
transfer_overlay: download_command: sleep 10; cd /tmp; wget unpack_command: tar -C / -xzfStatus : The job is get stuck in the overlay unpack.
Regards, Sarath P T -----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 21:23 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
On Tue, Feb 28, 2023 at 3:43 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Thanks for your reply. I have tried below scenario and could able to succeed with the overlay download in a different directory. But the unpack is still not taking in the "/" directory as I am having the read only image. So we have tried in the /etc directory cause its writable and I am showing the test job definition snippet below which I used.
context: lava_test_results_dir: "/etc/lava-%s"
Then in the boot/transfer_overlay: transfer_overlay: download_command: cd /etc ; wget unpack_command: tar -C /etc -xzf
Result status: The test job got stuck after the overlay download and did not proceed with the unpack.
Did you try the job with the original unpack_command? The overlay is prepared on the dispatcher with the full absolute path to unpack. So with the job as you posted you'll end up with your files in /etc/etc/lava-0 ... This is not what LAVA expects and that's why you're getting stuck.
Best Regards, Milosz
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 20:57 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
This is what I have in my jobs and it works for me. Context should include lava_test_results_dir
context: lava_test_results_dir: "/home/fio/lava-%s"
Then in the boot/transfer_overlay: transfer_overlay: download_command: cd /tmp ; wget unpack_command: tar -C / -xzf
Hope this helps.
Best Regards, Milosz
On Tue, Feb 28, 2023 at 3:17 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Below I am attaching the test job definition which I used.
priority: high
visibility: public
device_type: industrial-mtda-simatic-ipc227e-02
tags:
- slll-industrial-mtda-simatic-ipc227e-02
visibility: public
timeouts:
job:
minutes: 20action:
minutes: 10connection:
hours: 1job_name: slll_simatic_swupdate_test
actions:
deploy:
to: overlay
os: debian
boot:
method: minimal
reset: true
failure_retry: 2
auto_login:
login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: rootprompts:
- 'root@ebsy-isar:~#'
transfer_overlay:
download_command: cd /var ; sleep 10; wget; unpack_command: tar -C /var -xzftest:
definitions:
repository: http://<ip_addr_of_host>/linux-qa-suites.tar.gz
from: url
path:
linux-qa-suites/automated/eps-test/linux_kernel/linux_kernel.yaml
name: linux_kernel compression: gzmetadata:
Description: '"Lava jobs for simatic-ipc277e swupdate test check"'
context:
arch: x86
Regards,
Sarath P T
From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 28 February 2023 19:28 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Sarah,
It's hard to debug without the testjob definition. Could you post this here?
Best Regards,
Milosz
On Tue, Feb 28, 2023 at 1:00 PM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Team,
Any solution for the issue that I pointed here ? I tried below change as well
- Changed the source code
“/usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py” with “/var/lava-%s “ custom path
debian = {
"TESTER_PS1": r"linaro-test [rc=$(echo \$?)]# ", "TESTER_PS1_PATTERN": r"linaro-test \[rc=(\d+)\]# ", "TESTER_PS1_INCLUDES_RC": True, "boot_cmds": "boot_cmds", "line_separator": "\n", # for lava-test-shell "distro": "debian", "tar_flags": "--warning no-timestamp", "lava_test_sh_cmd": "/bin/bash", "lava_test_dir": "/var/lava-%s", "lava_test_results_part_attr": "root_part", "lava_test_results_dir": "/var/lava-%s", "lava_test_shell_file": "~/.bashrc",}
Status of the change : The overlay unpack is not happening in the specific directory that we applied to lava_test_dir and lava_test_results_dir.
I would appreciate it if you could send the solution of the issue that I raised here.
Regards,
Sarath P T
From: P T, Sarath Sent: 20 February 2023 18:35 To: 'lava-users@lists.lavasoftware.org' lava-users@lists.lavasoftware.org Subject: Not able to unpack the overlay other than "/" directory
Hi Team,
Facing an issue while unpack the overlay in some custom location other than “/” directory. From the LAVA linaro documentation I came to know that the -C / command to tar is essential or the test shell will not be able to start. Below are the issues that I am facing because of this.
My / directory is a read only one and I want it in some /etc or /var. The LAVA job is getting stuck while doing the unpack with the command below in job definition.
transfer_overlay:
download_command: cd /tmp; wget unpack_command: tar -C /tmp -xzfBelow I am attaching the test log from LAVA.
How we can solve the read only filesystem image issue for unpacking the overlay other than “/” directory ?
Regards, Sarath P T
Lava-users mailing list -- lava-users@lists.lavasoftware.org To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
On Wed, Mar 1, 2023 at 5:51 AM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Yes it’s a strange behaviour that there is no command sent over serial to start overlay decompression. And is there any server configuration changes you made for accomplishing it ?
No, I'm running vanilla LAVA dispatcher in a container from dockerhub https://hub.docker.com/r/lavasoftware/lava-dispatcher/
Best Regards, Milosz
Hi Milosz,
Now we could able to unpack the overlay in the path that we have given in the job definition. But after exporting the shell (export SHELL=/bin/bash) its not able to proceed with ". /<path_defined_in_definition>/lava-13030/environment" and "/<path_defined_in_definition>/lava-13030/bin/lava-test-runner /<path_defined_in_definition>/lava-13030/0 ". Below I am giving the job definition.
priority: high visibility: public device_type: industrial-mtda-simatic-ipc227e-01 visibility: public timeouts: job: minutes: 30 action: minutes: 20 connection: minutes: 20 job_name: SLLL_CI_MTDA_SIMATIC_IPC227E_DEPLOY_BOOT_TEST_JOB actions: - deploy: to: overlay os: debian - boot: method: minimal reset: true failure_retry: 2 auto_login: login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: root prompts: - 'root@ebsy-isar:~#' transfer_overlay: download_command: sleep 10; cd /home/test ; wget unpack_command: tar -C /home/test -xzf - test: role: - node1 timeout: minutes: 5 definitions: - repository: metadata: description: basic test for some devices on board format: Lava-Test Test Definition 1.0 name: kernel-version os: - debian run: steps: - cd /usr/libexec/ebsy-qa-suites/swupdate - ./swupdate_new.sh from: inline name: mtda-restart path: inline/mtda.yaml context: lava_test_results_dir: /home/test/lava-%s test_character_delay: 10 tags: - slll-industrial-mtda-simatic-ipc227e-01 timeouts: action: minutes: 20 connection: minutes: 20 job: hours: 7 visibility: public job_name: SLLL_X86_TEST_JOB metadata: Description: '"Lava jobs for deploy, boot and usb test"' DEVICES: slll-simatic-ipc227e-mtda-01
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 01 March 2023 14:27 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
On Wed, Mar 1, 2023 at 5:51 AM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Yes it’s a strange behaviour that there is no command sent over serial to start overlay decompression. And is there any server configuration changes you made for accomplishing it ?
No, I'm running vanilla LAVA dispatcher in a container from dockerhub https://hub.docker.com/r/lavasoftware/lava-dispatcher/
Best Regards, Milosz
Hi Milosz,
Any update ?
Regards, Sarath P T
-----Original Message----- From: P T, Sarath Sent: 08 March 2023 15:53 To: 'Milosz Wasilewski' milosz.wasilewski@foundries.io Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: RE: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Hi Milosz,
Now we could able to unpack the overlay in the path that we have given in the job definition. But after exporting the shell (export SHELL=/bin/bash) its not able to proceed with ". /<path_defined_in_definition>/lava-13030/environment" and "/<path_defined_in_definition>/lava-13030/bin/lava-test-runner /<path_defined_in_definition>/lava-13030/0 ". Below I am giving the job definition.
priority: high visibility: public device_type: industrial-mtda-simatic-ipc227e-01 visibility: public timeouts: job: minutes: 30 action: minutes: 20 connection: minutes: 20 job_name: SLLL_CI_MTDA_SIMATIC_IPC227E_DEPLOY_BOOT_TEST_JOB actions: - deploy: to: overlay os: debian - boot: method: minimal reset: true failure_retry: 2 auto_login: login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: root prompts: - 'root@ebsy-isar:~#' transfer_overlay: download_command: sleep 10; cd /home/test ; wget unpack_command: tar -C /home/test -xzf - test: role: - node1 timeout: minutes: 5 definitions: - repository: metadata: description: basic test for some devices on board format: Lava-Test Test Definition 1.0 name: kernel-version os: - debian run: steps: - cd /usr/libexec/ebsy-qa-suites/swupdate - ./swupdate_new.sh from: inline name: mtda-restart path: inline/mtda.yaml context: lava_test_results_dir: /home/test/lava-%s test_character_delay: 10 tags: - slll-industrial-mtda-simatic-ipc227e-01 timeouts: action: minutes: 20 connection: minutes: 20 job: hours: 7 visibility: public job_name: SLLL_X86_TEST_JOB metadata: Description: '"Lava jobs for deploy, boot and usb test"' DEVICES: slll-simatic-ipc227e-mtda-01
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 01 March 2023 14:27 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
On Wed, Mar 1, 2023 at 5:51 AM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Yes it’s a strange behaviour that there is no command sent over serial to start overlay decompression. And is there any server configuration changes you made for accomplishing it ?
No, I'm running vanilla LAVA dispatcher in a container from dockerhub https://hub.docker.com/r/lavasoftware/lava-dispatcher/
Best Regards, Milosz
Sarath,
Sorry, I can't reproduce any of your issues. You need to debug yourself.
Best Regards, Milosz
On Mon, Mar 13, 2023 at 6:11 AM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Any update ?
Regards, Sarath P T
-----Original Message----- From: P T, Sarath Sent: 08 March 2023 15:53 To: 'Milosz Wasilewski' milosz.wasilewski@foundries.io Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: RE: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Hi Milosz,
Now we could able to unpack the overlay in the path that we have given in the job definition. But after exporting the shell (export SHELL=/bin/bash) its not able to proceed with ". /<path_defined_in_definition>/lava-13030/environment" and "/<path_defined_in_definition>/lava-13030/bin/lava-test-runner /<path_defined_in_definition>/lava-13030/0 ". Below I am giving the job definition.
priority: high visibility: public device_type: industrial-mtda-simatic-ipc227e-01 visibility: public timeouts: job: minutes: 30 action: minutes: 20 connection: minutes: 20 job_name: SLLL_CI_MTDA_SIMATIC_IPC227E_DEPLOY_BOOT_TEST_JOB actions:
- deploy: to: overlay os: debian
- boot: method: minimal reset: true failure_retry: 2 auto_login: login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: root prompts:
transfer_overlay: download_command: sleep 10; cd /home/test ; wget unpack_command: tar -C /home/test -xzf
- 'root@ebsy-isar:~#'
- test: role:
timeout: minutes: 5 definitions:
- node1
- repository: metadata: description: basic test for some devices on board format: Lava-Test Test Definition 1.0 name: kernel-version os: - debian run: steps: - cd /usr/libexec/ebsy-qa-suites/swupdate - ./swupdate_new.sh from: inline name: mtda-restart path: inline/mtda.yaml
context: lava_test_results_dir: /home/test/lava-%s test_character_delay: 10 tags:
- slll-industrial-mtda-simatic-ipc227e-01
timeouts: action: minutes: 20 connection: minutes: 20 job: hours: 7 visibility: public job_name: SLLL_X86_TEST_JOB metadata: Description: '"Lava jobs for deploy, boot and usb test"' DEVICES: slll-simatic-ipc227e-mtda-01
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 01 March 2023 14:27 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
On Wed, Mar 1, 2023 at 5:51 AM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Yes it’s a strange behaviour that there is no command sent over serial to start overlay decompression. And is there any server configuration changes you made for accomplishing it ?
No, I'm running vanilla LAVA dispatcher in a container from dockerhub https://hub.docker.com/r/lavasoftware/lava-dispatcher/
Best Regards, Milosz
Hi Milosz,
Thanks for the support you have given. And I could able to achieve the scenario by changing the code from worker side as below
Navigate to the directory : cd /usr/lib/python3/dist-packages/lava_dispatcher
debian = { "TESTER_PS1": r"linaro-test [rc=$(echo $?)]# ", "TESTER_PS1_PATTERN": r"linaro-test [rc=(\d+)]# ", "TESTER_PS1_INCLUDES_RC": True, "boot_cmds": "boot_cmds", "line_separator": "\n", # for lava-test-shell "distro": "debian", "tar_flags": "--warning no-timestamp", "lava_test_sh_cmd": "/bin/bash", "lava_test_dir": "/lava-%s", "lava_test_results_part_attr": "root_part", "lava_test_results_dir": "/etc/lava-%s", "lava_test_shell_file": "~/.bashrc", }
I changed "lava_test_results_dir": "/etc/lava-%s", from "lava_test_results_dir": "/lava-%s", from the above code session. Somehow the lava_test_results_dir variable which we defined in the job definition is not getting override by the default value , that’s why we did the change. Can you post your code snippet from the worker ? and do you know why the job definition is not able to identify the lava_test_results_dir value ?
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 13 March 2023 14:50 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Sarath,
Sorry, I can't reproduce any of your issues. You need to debug yourself.
Best Regards, Milosz
On Mon, Mar 13, 2023 at 6:11 AM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Any update ?
Regards, Sarath P T
-----Original Message----- From: P T, Sarath Sent: 08 March 2023 15:53 To: 'Milosz Wasilewski' milosz.wasilewski@foundries.io Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: RE: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Hi Milosz,
Now we could able to unpack the overlay in the path that we have given in the job definition. But after exporting the shell (export SHELL=/bin/bash) its not able to proceed with ". /<path_defined_in_definition>/lava-13030/environment" and "/<path_defined_in_definition>/lava-13030/bin/lava-test-runner /<path_defined_in_definition>/lava-13030/0 ". Below I am giving the job definition.
priority: high visibility: public device_type: industrial-mtda-simatic-ipc227e-01 visibility: public timeouts: job: minutes: 30 action: minutes: 20 connection: minutes: 20 job_name: SLLL_CI_MTDA_SIMATIC_IPC227E_DEPLOY_BOOT_TEST_JOB actions:
- deploy: to: overlay os: debian
- boot: method: minimal reset: true failure_retry: 2 auto_login: login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: root prompts:
transfer_overlay: download_command: sleep 10; cd /home/test ; wget unpack_command: tar -C /home/test -xzf
- 'root@ebsy-isar:~#'
- test: role:
timeout: minutes: 5 definitions:
- node1
- repository: metadata: description: basic test for some devices on board format: Lava-Test Test Definition 1.0 name: kernel-version os: - debian run: steps: - cd /usr/libexec/ebsy-qa-suites/swupdate - ./swupdate_new.sh from: inline name: mtda-restart path: inline/mtda.yaml
context: lava_test_results_dir: /home/test/lava-%s test_character_delay: 10 tags:
- slll-industrial-mtda-simatic-ipc227e-01
timeouts: action: minutes: 20 connection: minutes: 20 job: hours: 7 visibility: public job_name: SLLL_X86_TEST_JOB metadata: Description: '"Lava jobs for deploy, boot and usb test"' DEVICES: slll-simatic-ipc227e-mtda-01
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 01 March 2023 14:27 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
On Wed, Mar 1, 2023 at 5:51 AM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Yes it’s a strange behaviour that there is no command sent over serial to start overlay decompression. And is there any server configuration changes you made for accomplishing it ?
No, I'm running vanilla LAVA dispatcher in a container from dockerhub https://hub.docker.com/r/lavasoftware/lava-dispatcher/
Best Regards, Milosz
Hi Milosz,
Any update on below query ?
I changed "lava_test_results_dir": "/etc/lava-%s", from "lava_test_results_dir": "/lava-%s", from the above code session. Somehow the lava_test_results_dir variable which we defined in the job definition is not getting override by the default value , that’s why we did the change. Can you post your code snippet from the worker ? and do you know why the job definition is not able to identify the lava_test_results_dir value ?
Regards, Sarath PT
-----Original Message----- From: P T, Sarath Sent: 15 March 2023 19:21 To: 'Milosz Wasilewski' milosz.wasilewski@foundries.io Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: RE: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Hi Milosz,
Thanks for the support you have given. And I could able to achieve the scenario by changing the code from worker side as below
Navigate to the directory : cd /usr/lib/python3/dist-packages/lava_dispatcher
debian = { "TESTER_PS1": r"linaro-test [rc=$(echo $?)]# ", "TESTER_PS1_PATTERN": r"linaro-test [rc=(\d+)]# ", "TESTER_PS1_INCLUDES_RC": True, "boot_cmds": "boot_cmds", "line_separator": "\n", # for lava-test-shell "distro": "debian", "tar_flags": "--warning no-timestamp", "lava_test_sh_cmd": "/bin/bash", "lava_test_dir": "/lava-%s", "lava_test_results_part_attr": "root_part", "lava_test_results_dir": "/etc/lava-%s", "lava_test_shell_file": "~/.bashrc", }
I changed "lava_test_results_dir": "/etc/lava-%s", from "lava_test_results_dir": "/lava-%s", from the above code session. Somehow the lava_test_results_dir variable which we defined in the job definition is not getting override by the default value , that’s why we did the change. Can you post your code snippet from the worker ? and do you know why the job definition is not able to identify the lava_test_results_dir value ?
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 13 March 2023 14:50 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Sarath,
Sorry, I can't reproduce any of your issues. You need to debug yourself.
Best Regards, Milosz
On Mon, Mar 13, 2023 at 6:11 AM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Any update ?
Regards, Sarath P T
-----Original Message----- From: P T, Sarath Sent: 08 March 2023 15:53 To: 'Milosz Wasilewski' milosz.wasilewski@foundries.io Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: RE: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Hi Milosz,
Now we could able to unpack the overlay in the path that we have given in the job definition. But after exporting the shell (export SHELL=/bin/bash) its not able to proceed with ". /<path_defined_in_definition>/lava-13030/environment" and "/<path_defined_in_definition>/lava-13030/bin/lava-test-runner /<path_defined_in_definition>/lava-13030/0 ". Below I am giving the job definition.
priority: high visibility: public device_type: industrial-mtda-simatic-ipc227e-01 visibility: public timeouts: job: minutes: 30 action: minutes: 20 connection: minutes: 20 job_name: SLLL_CI_MTDA_SIMATIC_IPC227E_DEPLOY_BOOT_TEST_JOB actions:
- deploy: to: overlay os: debian
- boot: method: minimal reset: true failure_retry: 2 auto_login: login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: root prompts:
transfer_overlay: download_command: sleep 10; cd /home/test ; wget unpack_command: tar -C /home/test -xzf
- 'root@ebsy-isar:~#'
- test: role:
timeout: minutes: 5 definitions:
- node1
- repository: metadata: description: basic test for some devices on board format: Lava-Test Test Definition 1.0 name: kernel-version os: - debian run: steps: - cd /usr/libexec/ebsy-qa-suites/swupdate - ./swupdate_new.sh from: inline name: mtda-restart path: inline/mtda.yaml
context: lava_test_results_dir: /home/test/lava-%s test_character_delay: 10 tags:
- slll-industrial-mtda-simatic-ipc227e-01
timeouts: action: minutes: 20 connection: minutes: 20 job: hours: 7 visibility: public job_name: SLLL_X86_TEST_JOB metadata: Description: '"Lava jobs for deploy, boot and usb test"' DEVICES: slll-simatic-ipc227e-mtda-01
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 01 March 2023 14:27 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
On Wed, Mar 1, 2023 at 5:51 AM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Yes it’s a strange behaviour that there is no command sent over serial to start overlay decompression. And is there any server configuration changes you made for accomplishing it ?
No, I'm running vanilla LAVA dispatcher in a container from dockerhub https://hub.docker.com/r/lavasoftware/lava-dispatcher/
Best Regards, Milosz
lava-users@lists.lavasoftware.org
-
Milosz Wasilewski -
P T, Sarath