User Tools

Site Tools


civilinfrastructureplatform:ciptestingknownissues

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
civilinfrastructureplatform:ciptestingknownissues [2017/06/14 12:06]
rajmarshall [B@D Virtual Machine Known Issues and their Workarounds] improve formatting
civilinfrastructureplatform:ciptestingknownissues [2018/11/09 11:10] (current)
rajmarshall fix typo!
Line 7: Line 7:
 Known issues of the VM created within the CIP project including LAVAv2 and KernelCI. Known issues of the VM created within the CIP project including LAVAv2 and KernelCI.
  
-=== Issue #84: Disk Space Filling up === 
- 
-There is a known issue with LAVA2 that it does not clear out some temporary files see https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​84 
- 
----- 
  
 === Issue #53: U Boot Prompt Detection === === Issue #53: U Boot Prompt Detection ===
  
-LAVA looks for the U-Boot prompt but due to differing forms of this prompt may not find it, see https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​53 for background.+LAVA looks for the U-Boot prompt but due to differing forms of this prompt may not find it, see https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​53 for background ​and a manual fix for the beaglebone.
  
 ---- ----
Line 21: Line 16:
 === Issue #87: Test times may be shown incorrectly === === Issue #87: Test times may be shown incorrectly ===
  
-If you suspend your host with Vagrant still running, when you awaken it the VM still has the time when suspended and it does not get updated to the time now. See https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​87 for the associated issue.+If you suspend your host with Vagrant still running, when you awaken it the VM still has the time when suspended and it does not get updated to the time now. See https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​87 for the associated issue. With Vagrant 2.1.2 this issue no longer occurs so upgrading your vagrant installation is a workaround - and therefore that issue has been closed.
  
 ---- ----
  
-=== Issue #56: LAVA health check wastes 30 seconds waiting for initramfs shell === 
  
-LAVA's health check will pause at the auto-login-action see https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​56 for the associated issue. 
  
----- 
  
-=== Issue #92: Virtualbox GUI reports "​Invalid settings detected"​ === +=== Issue #121 The QEMU health check may timeout ​===
-  +
-This shows up on Settings dialog of the B@D VM. See https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​92 for the associated issue. +
- +
----- +
-=== Issue #99: Issues with installing when running behind a web proxy === +
-When attempting to install B@D on a machine behind a web proxy you may experience the issues detailed here: https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​99 +
----- +
-=== Issue #103: Build artifacts referenced in the Beaglebone black health check are no longer accessible ​=== +
-The beaglebone black health check and other tests for that device reference files on the linaro website that have now moved location. See https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​103 for the history of this issue. +
- +
-*** Important *** +
-These changes need applying whether the user is using b@d from git or the pre-provisioned box. +
- +
- +
-The installation procedure is as follows: +
- +
-1. On the VM +
-  wget https://​s3-us-west-2.amazonaws.com/​download.cip-project.org/​ciptesting/​b%40d/​tests/​tests-0.1.tgz +
-  wget https://​s3-us-west-2.amazonaws.com/​download.cip-project.org/​ciptesting/​b%40d/​tests/​tests-0.1.sha256sum +
-  wget https://​s3-us-west-2.amazonaws.com/​download.cip-project.org/​ciptesting/​b%40d/​tests/​tests-0.1.tgz.sig +
- +
-2. Check the integrity of the download - see [[ciptestingboardatdeskdingledevdeployment#​using-sha256sum-and-gpg-to-check-integrity-and-signature-of-pre-provisioned-box|these instructions for the box]] replace with the appropriate file names. +
- +
-  cd /vagrant +
-  sudo tar zxf $DOWNLOADDIR/​tests-0.1.tgz +
- +
-3. If you have already created a Beaglebone black health check then you +
-need to replace it with the new /​vagrant/​tests/​bbb_debian_ramdisk_test.yaml +
- +
-//In the longer term there will be a 0.9.2 release of b@d which will +
-include a local version of initramfs and versions of the BBB kernel to +
-provide an initial health check.//+
  
 +If the QEMU Health check times out, try adjusting the values in the script along the lines of those values mentioned in https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​121
  
 ---- ----
Line 119: Line 80:
 8. Mount /dev/sdb1 to /storage 8. Mount /dev/sdb1 to /storage
  
-9. Consider moving the /var directory to the new drive since that is where the build artifacts are stored. [[https://​linuxconfig.org/​how-to-move-var-directory-to-another-partition]]+9. Consider moving the /var directory to the new drive since that is where the build artifacts are stored. [[https://​linuxconfig.org/​how-to-move-var-directory-to-another-partition]]. As the /home directory is likely to be larger than /var unless you do a lot of builds of different versions of the CIP kernel you may also wish to move /home onto its own partition. 
 + 
 +(If wanting to expand primary vmdk disk sda, resizing via vdi & gparted: https://​computingforgeeks.com/​step-by-step-guide-on-how-to-extend-vdi-and-vmdk-hard-disks-on-virtualbox/​)
  
 ---- ----
 +=== 4. Logging in on the LAVA web interface fails silently ===
 +
 +If you have not rebooted the virtual machine after the initial provision, logging in as administrator will return you to the home page but with the login still available. You need: \\
 +  vagrant halt 
 +  vagrant up
 +
 +in order to have the LAVA installation running cleanly so that login works. ​
 +
 +----
 +
 +=== 5. Debian stretch provides vagrant and virtual box which do not work together ===
 +
 +In order to have versions of these packages which work together in Debian stretch, run the following (on the host!) see [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​121|#​121]]: ​
 +
 +  sudo apt-add-repository 'deb http://​download.virtualbox.org/​virtualbox/​debian stretch contrib'​
 +  curl -O https://​www.virtualbox.org/​download/​oracle_vbox_2016.asc
 +  sudo apt-key add oracle_vbox_2016.asc
 +  sudo apt-get update
 +  sudo apt-get install virtualbox-5.1
 +
 +----
 +
 +=== 6. Connecting to the Beaglebone using ssh ===
 +If you have problems connecting to the BBB using ssh - though the health check does not reuire this - use the following [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​157|procedure]]:​
 +
 +
 +   * The usb power cable must be connected to the host (as well as the ftdi cable but this isn't used here) the eth1 device will appear - but is not being assigned an IP address
 +   * Then sudo ifconfig eth1 192.168.7.1 (on the host) ssh root@192.168.7.2 should then work.
 +   * Note that the BBB will reboot during the health test and the above setting will be lost so an edit to /​etc/​network/​interfaces will be necessary to set this address
 +
 +----
 +
 +=== 7. Extending the kernelci timeout date ===
 +
 +Builds in kernelci become invisible to the web interface after 14 days - though the builds are still accessible from LAVA tests, if you wish to increase that timeout edit the DATE_RANGE setting in /​etc/​linaro/​kernelci-frontend.cfg. See the discussion in [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​164|#​164]] - now closed.
 +
 +----
 +
 +=== 8. Provisioning B@D from behind a web proxy ===
 +
 +You may have errors when trying to provision B@D when operating behind some web proxies, see [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​195|#​195]] for a discussion and hints.
  
 [[civilinfrastructureplatform:​ciptestingboardatdesksingledevfeaturepage | Back to the B@D Features page]] [[civilinfrastructureplatform:​ciptestingboardatdesksingledevfeaturepage | Back to the B@D Features page]]
civilinfrastructureplatform/ciptestingknownissues.1497441999.txt.gz · Last modified: 2017/06/14 12:06 by rajmarshall