All, The upgrade of the ADB host ashes within the CI Lab ran into problems. This does not appear to be an issue with the upgrade of the OS from Raring to Saucy but rather an issue with the hardware itself. Currently when rebooting the host ashes it automatically goes into the BIOS screen but does accept any keyboard input so configuration changes cannot be made nor can the BIOS screen be exited. This issue persists whether using the KVM connection to the system or a USB keyboard physically connected to the system.
The issue triggering the automatic shift into the BIOS configuration seems to be memory related. Further troubleshooting will occur when someone from IS is physically in the data center. Many thanks to Mike from CTS who attempted the help resolve the issue Friday evening with the physical keyboard. What does this mean for testing? Until ashes can be restored to service (or replaced if that fails) the following devices will be unavailable for testing: flo-01, flo-02, flo-03, maguro-01, maguro-02, maguro-03, maguro-04, maguro-05, maguro-06, mako-01, mako-02, mako-04, mako-05, mako-06, mako-07, mako-09, mako-10, mako-11, manta-01, and manta-02 This will result in the following tests/jobs not being able to be run: eventstat, smem, memevent, touch-smoke-daily With the ADB host ashes being down it was decided not to proceed with the OS upgrade of the other ADB host okiku. I will send out more information on Monday. ~w -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
