Hi All,
I have recently started seeing an issue with my health check jobs at the stage where the Linaro bootfs is deployed. It looks like the permissions are wrong somewhere.
I see no problems when running Android jobs. I have not changed anything on the TC2 boards, and I have not changed anything on the dispatcher apart from upgrade to the latest version of LAVA.
I have attached a log for more details.
Before I start looking into whether or not this is a problem with my specific LAVA environment, I just wanted to check if this was a known issue? If so, has there been any config changes that I need to apply please to prevent this from happening? Could this be to do with linaro-media-create?
Thanks Dean
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Hi Dean,
I can't say I've seen anything like this. I'm assuming this isn't just on one TC2, but on any device?
Dave
On 4 Nov 2013, at 12:30, Dean Arnold Dean.Arnold@arm.com wrote:
<job_1602.log>
Hi Dave,
In our setup we only have fastmodels and TC2 so unfortunately I have been unable to try this on any other development boards.
I don't seem to see it on the 64bit fastmodels jobs I have running but it is happening on all of our TC2 boards. Open Embedded seems to run fine of the models and Android is ok on TC2, so it only seems to apply to Ubuntu on TC2.
Thanks Dean
-----Original Message----- From: Dave Pigott [mailto:dave.pigott@linaro.org] Sent: 05 November 2013 10:22 To: Dean Arnold Cc: linaro-validation@lists.linaro.org Validation; Ian Spray; Basil Eljuse Subject: Re: [Linaro-validation] Cannot change ownership to uid 0, gid 1 when deploying linaro bootfs
Hi Dean,
I can't say I've seen anything like this. I'm assuming this isn't just on one TC2, but on any device?
Dave
On 4 Nov 2013, at 12:30, Dean Arnold Dean.Arnold@arm.com wrote:
<job_1602.log>
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Hi Dean,
Only difference I can see is that our health check doesn't use l-m-c and we use a 1 month older release:
--------------Begin included-------------- { "timeout": 36000, "job_name": "lab-health-vexpress-tc2", "health_check": true, "logging_level":"DEBUG", "notify_on_incomplete": ["lava-notification@lists.linaro.org"], "actions": [ { "command": "deploy_linaro_image", "parameters": { "image": "http://releases.linaro.org/13.04/ubuntu/vexpress/vexpress-quantal_developer_..." } }, { "command": "boot_linaro_image" }, { "command": "deploy_linaro_android_image", "parameters": { "data": "http://releases.linaro.org/13.04/android/vexpress/userdata.tar.bz2", "boot": "http://releases.linaro.org/13.04/android/vexpress/boot.tar.bz2", "system": "http://releases.linaro.org/13.04/android/vexpress/system.tar.bz2" } }, { "command": "boot_linaro_android_image" }, { "command": "submit_results", "parameters": { "stream": "/private/team/linaro/lab-health/", "server": "http://lava-health:0uwg4a3i3m17mgut0zt00gg80bzdh3dytps1bms86iirz12ijmg25twu3..." } } ] } --------------End included-------------- Can you try that and see if it works?
Thanks
Dave
On 5 Nov 2013, at 10:33, Dean Arnold Dean.Arnold@arm.com wrote:
Hi Dave,
In our setup we only have fastmodels and TC2 so unfortunately I have been unable to try this on any other development boards.
I don't seem to see it on the 64bit fastmodels jobs I have running but it is happening on all of our TC2 boards. Open Embedded seems to run fine of the models and Android is ok on TC2, so it only seems to apply to Ubuntu on TC2.
Thanks Dean
-----Original Message----- From: Dave Pigott [mailto:dave.pigott@linaro.org] Sent: 05 November 2013 10:22 To: Dean Arnold Cc: linaro-validation@lists.linaro.org Validation; Ian Spray; Basil Eljuse Subject: Re: [Linaro-validation] Cannot change ownership to uid 0, gid 1 when deploying linaro bootfs
Hi Dean,
I can't say I've seen anything like this. I'm assuming this isn't just on one TC2, but on any device?
Dave
On 4 Nov 2013, at 12:30, Dean Arnold Dean.Arnold@arm.com wrote:
<job_1602.log>
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Hi Dave,
I have just kicked off a run that uses your definition. As soon as the results come in I will let you know.
Cheers Dean
-----Original Message----- From: Dave Pigott [mailto:dave.pigott@linaro.org] Sent: 05 November 2013 11:49 To: Dean Arnold Cc: linaro-validation@lists.linaro.org Validation; Ian Spray; Basil Eljuse Subject: Re: [Linaro-validation] Cannot change ownership to uid 0, gid 1 when deploying linaro bootfs
Hi Dean,
Only difference I can see is that our health check doesn't use l-m-c and we use a 1 month older release:
--------------Begin included-------------- { "timeout": 36000, "job_name": "lab-health-vexpress-tc2", "health_check": true, "logging_level":"DEBUG", "notify_on_incomplete": ["lava-notification@lists.linaro.org"], "actions": [ { "command": "deploy_linaro_image", "parameters": { "image": "http://releases.linaro.org/13.04/ubuntu/vexpress/vexpress- quantal_developer_20130423-299.img.gz" } }, { "command": "boot_linaro_image" }, { "command": "deploy_linaro_android_image", "parameters": { "data": "http://releases.linaro.org/13.04/android/vexpress/userdata.tar.bz2", "boot": "http://releases.linaro.org/13.04/android/vexpress/boot.tar.bz2", "system": "http://releases.linaro.org/13.04/android/vexpress/system.tar.bz2" } }, { "command": "boot_linaro_android_image" }, { "command": "submit_results", "parameters": { "stream": "/private/team/linaro/lab-health/", "server": "http://lava- health:0uwg4a3i3m17mgut0zt00gg80bzdh3dytps1bms86iirz12ijmg25twu3tgypdnt cdy29pxstx90n2q71s4cws6c10dk2zjx8c6m50nxo2kcdzao4bgfckd8nyfuqc08@valida tion.linaro.org/RPC2/" } } ] } --------------End included-------------- Can you try that and see if it works?
Thanks
Dave
On 5 Nov 2013, at 10:33, Dean Arnold Dean.Arnold@arm.com wrote:
Hi Dave,
In our setup we only have fastmodels and TC2 so unfortunately I have
been unable to try this on any other development boards.
I don't seem to see it on the 64bit fastmodels jobs I have running
but it is happening on all of our TC2 boards. Open Embedded seems to run fine of the models and Android is ok on TC2, so it only seems to apply to Ubuntu on TC2.
Thanks Dean
-----Original Message----- From: Dave Pigott [mailto:dave.pigott@linaro.org] Sent: 05 November 2013 10:22 To: Dean Arnold Cc: linaro-validation@lists.linaro.org Validation; Ian Spray; Basil Eljuse Subject: Re: [Linaro-validation] Cannot change ownership to uid 0,
gid
1 when deploying linaro bootfs
Hi Dean,
I can't say I've seen anything like this. I'm assuming this isn't
just
on one TC2, but on any device?
Dave
On 4 Nov 2013, at 12:30, Dean Arnold Dean.Arnold@arm.com wrote:
<job_1602.log>
-- IMPORTANT NOTICE: The contents of this email and any attachments
are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ,
Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1
9NJ, Registered in England & Wales, Company No: 2548782
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Hi Dave,
The Ubuntu job fails yet again, even without using l-m-c. Is there a way to prevent LAVA from cleaning up the files after the job so that I can check the permissions on the image?
I wonder if something has gone wrong with my dispatcher environment.
Cheers Dean
-----Original Message----- From: Dean Arnold Sent: 05 November 2013 11:54 To: 'Dave Pigott' Cc: linaro-validation@lists.linaro.org Validation; Ian Spray; Basil Eljuse Subject: RE: [Linaro-validation] Cannot change ownership to uid 0, gid 1 when deploying linaro bootfs
Hi Dave,
I have just kicked off a run that uses your definition. As soon as the results come in I will let you know.
Cheers Dean
-----Original Message----- From: Dave Pigott [mailto:dave.pigott@linaro.org] Sent: 05 November 2013 11:49 To: Dean Arnold Cc: linaro-validation@lists.linaro.org Validation; Ian Spray; Basil Eljuse Subject: Re: [Linaro-validation] Cannot change ownership to uid 0,
gid
1 when deploying linaro bootfs
Hi Dean,
Only difference I can see is that our health check doesn't use l-m-c and we use a 1 month older release:
--------------Begin included-------------- { "timeout": 36000, "job_name": "lab-health-vexpress-tc2", "health_check": true, "logging_level":"DEBUG", "notify_on_incomplete": ["lava-notification@lists.linaro.org"], "actions": [ { "command": "deploy_linaro_image", "parameters": { "image": "http://releases.linaro.org/13.04/ubuntu/vexpress/vexpress- quantal_developer_20130423-299.img.gz" } }, { "command": "boot_linaro_image" }, { "command": "deploy_linaro_android_image", "parameters": { "data": "http://releases.linaro.org/13.04/android/vexpress/userdata.tar.bz2", "boot": "http://releases.linaro.org/13.04/android/vexpress/boot.tar.bz2", "system": "http://releases.linaro.org/13.04/android/vexpress/system.tar.bz2" } }, { "command": "boot_linaro_android_image" }, { "command": "submit_results", "parameters": { "stream": "/private/team/linaro/lab-health/", "server": "http://lava-
health:0uwg4a3i3m17mgut0zt00gg80bzdh3dytps1bms86iirz12ijmg25twu3tgypdnt
cdy29pxstx90n2q71s4cws6c10dk2zjx8c6m50nxo2kcdzao4bgfckd8nyfuqc08@valida
tion.linaro.org/RPC2/" } } ] } --------------End included-------------- Can you try that and see if it works?
Thanks
Dave
On 5 Nov 2013, at 10:33, Dean Arnold Dean.Arnold@arm.com wrote:
Hi Dave,
In our setup we only have fastmodels and TC2 so unfortunately I
have
been unable to try this on any other development boards.
I don't seem to see it on the 64bit fastmodels jobs I have running
but it is happening on all of our TC2 boards. Open Embedded seems to run fine of the models and Android is ok on TC2, so it only seems to apply to Ubuntu on TC2.
Thanks Dean
-----Original Message----- From: Dave Pigott [mailto:dave.pigott@linaro.org] Sent: 05 November 2013 10:22 To: Dean Arnold Cc: linaro-validation@lists.linaro.org Validation; Ian Spray;
Basil
Eljuse Subject: Re: [Linaro-validation] Cannot change ownership to uid 0,
gid
1 when deploying linaro bootfs
Hi Dean,
I can't say I've seen anything like this. I'm assuming this isn't
just
on one TC2, but on any device?
Dave
On 4 Nov 2013, at 12:30, Dean Arnold Dean.Arnold@arm.com wrote:
<job_1602.log>
-- IMPORTANT NOTICE: The contents of this email and any attachments
are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1
9NJ,
Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge
CB1
9NJ, Registered in England & Wales, Company No: 2548782
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Hi Dean,
I'm pretty sure we haven't cleaned anything up, so the master image will still be in the appropriate state. You *may* need to remount the various testboot and testrootfs partitions. In these situations I tend to just follow the commands the dispatcher has sent and then inspect/play around with the mounted directories to see if something has got corrupted.
I'd start with an "fdisk -l" to check all your partitions are ok. Then an "ls -l /dev/disk/by-label" to check all the formatting links are correct. Then I'd do the mount. First thing to check then, is that when you mount, what the permissions appear to be. After that I'd unmount and start doing the mkfs commands from the log and then remount - one possibility is that there is some device table corruption so the old data isn't being blown away.
That's where I'd start. After that it's difficult to suggest until you get further information.
Thanks
Dave
On 5 Nov 2013, at 13:55, Dean Arnold Dean.Arnold@arm.com wrote:
Hi Dave,
The Ubuntu job fails yet again, even without using l-m-c. Is there a way to prevent LAVA from cleaning up the files after the job so that I can check the permissions on the image?
I wonder if something has gone wrong with my dispatcher environment.
Cheers Dean
-----Original Message----- From: Dean Arnold Sent: 05 November 2013 11:54 To: 'Dave Pigott' Cc: linaro-validation@lists.linaro.org Validation; Ian Spray; Basil Eljuse Subject: RE: [Linaro-validation] Cannot change ownership to uid 0, gid 1 when deploying linaro bootfs
Hi Dave,
I have just kicked off a run that uses your definition. As soon as the results come in I will let you know.
Cheers Dean
-----Original Message----- From: Dave Pigott [mailto:dave.pigott@linaro.org] Sent: 05 November 2013 11:49 To: Dean Arnold Cc: linaro-validation@lists.linaro.org Validation; Ian Spray; Basil Eljuse Subject: Re: [Linaro-validation] Cannot change ownership to uid 0,
gid
1 when deploying linaro bootfs
Hi Dean,
Only difference I can see is that our health check doesn't use l-m-c and we use a 1 month older release:
--------------Begin included-------------- { "timeout": 36000, "job_name": "lab-health-vexpress-tc2", "health_check": true, "logging_level":"DEBUG", "notify_on_incomplete": ["lava-notification@lists.linaro.org"], "actions": [ { "command": "deploy_linaro_image", "parameters": { "image": "http://releases.linaro.org/13.04/ubuntu/vexpress/vexpress- quantal_developer_20130423-299.img.gz" } }, { "command": "boot_linaro_image" }, { "command": "deploy_linaro_android_image", "parameters": { "data": "http://releases.linaro.org/13.04/android/vexpress/userdata.tar.bz2", "boot": "http://releases.linaro.org/13.04/android/vexpress/boot.tar.bz2", "system": "http://releases.linaro.org/13.04/android/vexpress/system.tar.bz2" } }, { "command": "boot_linaro_android_image" }, { "command": "submit_results", "parameters": { "stream": "/private/team/linaro/lab-health/", "server": "http://lava-
health:0uwg4a3i3m17mgut0zt00gg80bzdh3dytps1bms86iirz12ijmg25twu3tgypdnt
cdy29pxstx90n2q71s4cws6c10dk2zjx8c6m50nxo2kcdzao4bgfckd8nyfuqc08@valida
tion.linaro.org/RPC2/" } } ] } --------------End included-------------- Can you try that and see if it works?
Thanks
Dave
On 5 Nov 2013, at 10:33, Dean Arnold Dean.Arnold@arm.com wrote:
Hi Dave,
In our setup we only have fastmodels and TC2 so unfortunately I
have
been unable to try this on any other development boards.
I don't seem to see it on the 64bit fastmodels jobs I have running
but it is happening on all of our TC2 boards. Open Embedded seems to run fine of the models and Android is ok on TC2, so it only seems to apply to Ubuntu on TC2.
Thanks Dean
-----Original Message----- From: Dave Pigott [mailto:dave.pigott@linaro.org] Sent: 05 November 2013 10:22 To: Dean Arnold Cc: linaro-validation@lists.linaro.org Validation; Ian Spray;
Basil
Eljuse Subject: Re: [Linaro-validation] Cannot change ownership to uid 0,
gid
1 when deploying linaro bootfs
Hi Dean,
I can't say I've seen anything like this. I'm assuming this isn't
just
on one TC2, but on any device?
Dave
On 4 Nov 2013, at 12:30, Dean Arnold Dean.Arnold@arm.com wrote:
<job_1602.log>
-- IMPORTANT NOTICE: The contents of this email and any attachments
are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1
9NJ,
Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge
CB1
9NJ, Registered in England & Wales, Company No: 2548782
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782<job_1610.log>
Hi Dean,
Just a quick note: We have a 100K limit on e-mails, so I'm having to moderate them through to the list. Could you zip the files up before attaching them?
Thanks
Dave
On 5 Nov 2013, at 14:40, Dave Pigott dave.pigott@linaro.org wrote:
s the d
Dean Arnold Dean.Arnold@arm.com writes:
Hi Dave,
The Ubuntu job fails yet again, even without using l-m-c. Is there a way to prevent LAVA from cleaning up the files after the job so that I can check the permissions on the image?
I wonder if something has gone wrong with my dispatcher environment.
I have seen this before: https://bugs.launchpad.net/lava-dispatcher/+bug/954870
We never really found out what was going on though -- it's bizarre, why does sometimes tar start complaining about not being able to chown on a vfat partition? I agree with Dave that booting into the master image and playing around with commands similar to those which fail might be interesting.
Cheers, mwh
Thanks Dave/Michael,
When you saw the issue in the ticket below, I know you didn't ever discover the root cause but how did you resolve this problem in the short term? Did it just happen intermittently? I have tried multiple different images using both l-m-c and the prebuilt ones from releases.linaro.org but nothing seems to shift the problem.
I have also tried manually playing about with the commands on a few of the boards as suggested and I couldn't see anything obvious that was going wrong which would cause this. I have also moved the boards to a new dispatcher to see if that somehow made a difference, just in case the image which was being deployed was getting screwed up on the dispatcher side. Overall I have had no joy whatsoever.
I was thinking of putting a fresh master image on one of the boards and running the lava-first-boot scripts to see if this fixes things. As different images and dispatcher environments don't make a difference, I am assuming the problem is related to the master image. What release are you guys currently using for the master images on your vexpresstc2 devices?
In the lava-master-image-scripts, should running the following be enough for what I need?
./lava-create-master vexpresstc2
Cheers, Dean
-----Original Message----- From: Michael Hudson-Doyle [mailto:michael.hudson@linaro.org] Sent: 05 November 2013 20:06 To: Dean Arnold; Dean Arnold; Dave Pigott Cc: linaro-validation@lists.linaro.org Validation; Ian Spray; Basil Eljuse Subject: Re: [Linaro-validation] Cannot change ownership to uid 0, gid 1 when deploying linaro bootfs
Dean Arnold Dean.Arnold@arm.com writes:
Hi Dave,
The Ubuntu job fails yet again, even without using l-m-c. Is there a
way to prevent LAVA from cleaning up the files after the job so that I can check the permissions on the image?
I wonder if something has gone wrong with my dispatcher environment.
I have seen this before: https://bugs.launchpad.net/lava-dispatcher/+bug/954870
We never really found out what was going on though -- it's bizarre, why does sometimes tar start complaining about not being able to chown on a vfat partition? I agree with Dave that booting into the master image and playing around with commands similar to those which fail might be interesting.
Cheers, mwh
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Hi Dean,
Make sure you've cloned the latest lava-master-image-scripts from git and you'll be using the same as us. The device is unified for all vexpress now, so it's just "./lava-create-master vexpress".
More conveniently, if you go to: http://images.validation.linaro.org/lava-masters/
You'll see the vexpress image in a tgz format that you can download.
Thanks
Dave
On 6 Nov 2013, at 10:09, Dean Arnold Dean.Arnold@arm.com wrote:
Thanks Dave/Michael,
When you saw the issue in the ticket below, I know you didn't ever discover the root cause but how did you resolve this problem in the short term? Did it just happen intermittently? I have tried multiple different images using both l-m-c and the prebuilt ones from releases.linaro.org but nothing seems to shift the problem.
I have also tried manually playing about with the commands on a few of the boards as suggested and I couldn't see anything obvious that was going wrong which would cause this. I have also moved the boards to a new dispatcher to see if that somehow made a difference, just in case the image which was being deployed was getting screwed up on the dispatcher side. Overall I have had no joy whatsoever.
I was thinking of putting a fresh master image on one of the boards and running the lava-first-boot scripts to see if this fixes things. As different images and dispatcher environments don't make a difference, I am assuming the problem is related to the master image. What release are you guys currently using for the master images on your vexpresstc2 devices?
In the lava-master-image-scripts, should running the following be enough for what I need?
./lava-create-master vexpresstc2
Cheers, Dean
-----Original Message----- From: Michael Hudson-Doyle [mailto:michael.hudson@linaro.org] Sent: 05 November 2013 20:06 To: Dean Arnold; Dean Arnold; Dave Pigott Cc: linaro-validation@lists.linaro.org Validation; Ian Spray; Basil Eljuse Subject: Re: [Linaro-validation] Cannot change ownership to uid 0, gid 1 when deploying linaro bootfs
Dean Arnold Dean.Arnold@arm.com writes:
Hi Dave,
The Ubuntu job fails yet again, even without using l-m-c. Is there a
way to prevent LAVA from cleaning up the files after the job so that I can check the permissions on the image?
I wonder if something has gone wrong with my dispatcher environment.
I have seen this before: https://bugs.launchpad.net/lava-dispatcher/+bug/954870
We never really found out what was going on though -- it's bizarre, why does sometimes tar start complaining about not being able to chown on a vfat partition? I agree with Dave that booting into the master image and playing around with commands similar to those which fail might be interesting.
Cheers, mwh
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
linaro-validation@lists.linaro.org
-
Dave Pigott -
Dean Arnold -
Michael Hudson-Doyle