Hi Jessica, some time ago, Paul wrote you about his suspicion, that an ARM64 image used for jenkins minions - uses the x86 version of docker-compose. So it was not possible to execute CSIT TCs on a jenkins minions based on that image.
I had a look and I agree with Paul's findings. Docker compose (among other tools) is installed by ansible playbook packer/provision/local-docker.yaml (from ci-management repo). This playbook installs x86 version of docker compose on every platform. I've prepared a patch, which will install required version of docker-compose via pip, so correct version will be available at both x86 and arm64. I've also updated the golang section to download correct binary based on the platform. Patch is available for review at: https://gerrit.onap.org/r/#/c/83491/ I've tested it locally on ARM. My testing environment uses locally installed OpenStack on ARM64 and also packer is executed at (another) ARM64 machine (LF is running packer on x86 to build ARM64 images). The build of builder and docker VM images was successful, i.e. execution of following commands succeeded and images are available in my openstack: packer build -var-file=vars/cloud-env.json -var-file=vars/ubuntu-16.04-arm64.json templates/builder.json packer build -var-file=vars/cloud-env.json -var-file=vars/ubuntu-16.04-arm64.json templates/docker.json By the way, I had to sent another two patches toward LF ansible playbooks, to be able to proceed with ARM64 image builds: https://gerrit.linuxfoundation.org/infra/#/c/15069/ https://gerrit.linuxfoundation.org/infra/#/c/15072/ Please advise, Martin ________________________________ Od: Paul Vaduva <[email protected]> Odesláno: úterý 12. března 2019 10:39 Komu: Klozik Martin; [email protected] Předmět: RE: [onap-discuss][CIA] FW: arm64 node tools Hi Martin, See my comments inline. P.S.: Do we have a solution for deploying arm64 docker images without rancher ? Best Regards, Paul From: Klozik Martin <[email protected]> Sent: Friday, March 8, 2019 5:36 PM To: [email protected]; Paul Vaduva <[email protected]> Subject: Re: [onap-discuss][CIA] FW: arm64 node tools Hi Paul, I had just a quick look at CSIT job and related packer definitions inside the ci-management repo. Before I will dig deeper next week, I would like to ask you: 1) is this still a valid topic I should focus on or do you see any other CI/CD, etc. related task I should take care of / help you with? [Paul Vaduva] Yes, this is still a valid issue that woudl help us a lot. The issue that Jessica is also investigating is here: https://jira.onap.org/browse/CIMAN-229 2) do you know if there was any progress during last few weeks? (e.g. by Jessica or you...) [Paul Vaduva] Based on comments on the previous issue and followint the onap-discuss list I will assume there is no progress. 3) If I got it correctly the main topic is to setup the environment locally (describe it / prepare some automation / etc) so we can run CSIT TCs at ARM to verify our ARM ONAP images. Once environment is prepared, we will use our experience to fix and improve ARM specific CSIT jobs. Am I right? [Paul Vaduva] That is precise what we want to achieve. Please advise, Martin ________________________________ Od: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> za uživatele Paul Vaduva <[email protected]<mailto:[email protected]>> Odesláno: pátek 22. února 2019 16:56 Komu: [email protected]<mailto:[email protected]> Kopie: Adolfo Perez-Duran; [email protected]<mailto:[email protected]>; Klozik Martin; Hrabos Simon; Puzikov Dmitry Předmět: [onap-discuss][CIA] FW: arm64 node tools Hi guys, As per our discussion today I am forwarding you an email about the tooling installed by LF on nodes that run CSIT jobs. IF we can prioritize resources for that maybe someone can take a look into that so we have a local environment to run CSIT jobs (which would be great), and probably help solve Jessica’s issues with the tools for arm64. They use a tool called packer to somehow install all the necessary environment on the arm64 node, more details on the console log here: https://jenkins.onap.org/view/arm64/job/ci-management-packer-merge-ubuntu-16.04-arm64-docker/2/console<https://url10.mailanyone.net/v1/?m=1gfF1H-000BSN-4D&i=57e1b682&c=ASSYnt2DQVUreSrSAtlPWbU459d5nB0rf_LOw4BJKYZZoZ1XcJWcGmAB7jHn1YOb7RBroxWKMYMSv3pRa15c4F_telcnnZdoxXcxAMaI7NhMYZBDdMT1oB7CzwTgbRKYOrVVA6HyxKRcOqqxJ0TXGE8C7fKE_-lL4-NFQLvbB0dHh_ShK-iTYWzMYB_Dhx07mX5uL1bPV-0lHumu0eFv940SI_aXtZx01CT3cseAdiooE52B7mTPQzJcv5OmfeHsrwhSEM-2kVi0cdDZY0gefsU8FDJNGOYNv__VO_sshKWC2TwXv9l5_yB8Q9nDkOGNAs3HbJ8i5bDvSJQiaRzvJQ> Best Regards, Paul Vaduva From: Jessica Wagantall <[email protected]<mailto:[email protected]>> Sent: Friday, January 4, 2019 4:15 AM To: Paul Vaduva <[email protected]<mailto:[email protected]>> Subject: Re: arm64 node tools Thanks for checking Paul. >From the image we are using, I can tell that Docker compose was installed :( 17:47:15 vexxhost: TASK [Install Docker Compose 1.17.1] ******************************************* 17:47:15 vexxhost: Wednesday 31 October 2018 17:47:15 +0000 (0:00:02.218) 0:58:10.423 ***** 17:47:17 vexxhost: changed: [default] 17:47:17 vexxhost: [WARNING]: Consider using get_url or uri module rather than running curl More information on all tools installed is here: https://jenkins.onap.org/view/arm64/job/ci-management-packer-merge-ubuntu-16.04-arm64-docker/2/console<https://url10.mailanyone.net/v1/?m=1gfF1H-000BSN-4D&i=57e1b682&c=ASSYnt2DQVUreSrSAtlPWbU459d5nB0rf_LOw4BJKYZZoZ1XcJWcGmAB7jHn1YOb7RBroxWKMYMSv3pRa15c4F_telcnnZdoxXcxAMaI7NhMYZBDdMT1oB7CzwTgbRKYOrVVA6HyxKRcOqqxJ0TXGE8C7fKE_-lL4-NFQLvbB0dHh_ShK-iTYWzMYB_Dhx07mX5uL1bPV-0lHumu0eFv940SI_aXtZx01CT3cseAdiooE52B7mTPQzJcv5OmfeHsrwhSEM-2kVi0cdDZY0gefsU8FDJNGOYNv__VO_sshKWC2TwXv9l5_yB8Q9nDkOGNAs3HbJ8i5bDvSJQiaRzvJQ> I was really hoping this was a tooling issue hahah, wonder if the version has anything to do with it. Most of the errors we are having in the ARM nodes look like API/ARCH issues, but unfortunatelly my technical issues with this code is not the greatest. I will continue debugging and see what else I can try Thanks a ton! Jess On Thu, Dec 20, 2018 at 9:23 AM Paul Vaduva <[email protected]<mailto:[email protected]>> wrote: Hi Jess, I am writing you about this job: https://jenkins.onap.org/job/vid-arm64-master-verify-csit-healthCheck/3/console<https://url10.mailanyone.net/v1/?m=1gfF1H-000BSN-4D&i=57e1b682&c=kz-HB0Xiw2I7t-jY7_FqIoAv391qyU9Qkn9jgzCu5yf8oY0i701bQxB2QVh8RTgE6k9lXa5pK3euJtbdHD-c_zVZhjj8LF6h2t7opMgkSdDA6wcYx0cjJmDiUbqZlb7qC3RUVY4t-rk8lQXbev2fELhYQl-Qfr_F_zNn0rdR0lezWWVeBNzXvGM9lnKKp8GAlf5U3s_GKvGyA-P-cpkHRHwvFlhYbwb7bxSNsveq-atzBilUS8SYSgYU3h4LzulTQTmyeXLsKrwF_46IEWzRMHNP2-oWtH9D4veFLKUnJTw> mainly the error here: 17:07:41 +++ docker-compose up -d --build 17:07:41 /w/workspace/vid-arm64-master-verify-csit-healthCheck/scripts/vid/start_vid_containers.sh: line 39: /usr/local/bin/docker-compose: cannot execute binary file: Exec format error 17:07:41 +++ TIME_OUT=1200 I have a suspicion that these are tools from your tooling package on the build node And it’s an x86 binary, because I can’t find any where reference of some installing of docker-compose as part of the job, Can you please take a look and confirm or infirm my suspicion? Best Regards, Paul This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks. This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks. This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16368): https://lists.onap.org/g/onap-discuss/message/16368 Mute This Topic: https://lists.onap.org/mt/29999653/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
