This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
civilinfrastructureplatform:ciptestingknownissues [2018/11/02 16:22] rajmarshall [B@D Virtual Machine Troubleshooting Guide] add note on debian stretch vagrant virtualbox install |
civilinfrastructureplatform:ciptestingknownissues [2018/11/09 11:09] rajmarshall web proxy link andded |
||
---|---|---|---|
Line 97: | Line 97: | ||
=== 5. Debian stretch provides vagrant and virtual box which do not work together === | === 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!): | + | 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' | sudo apt-add-repository 'deb http://download.virtualbox.org/virtualbox/debian stretch contrib' | ||
Line 106: | Line 106: | ||
---- | ---- | ||
+ | |||
+ | === 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 behing 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]] |