Bug #12041
Spurious reboot breaks test suite which cannot connect to the remote shell
Start date:
2016-12-19
Due date:
% Done:
0%
Description
After we deal with the boot menu the kernel starts booting, but then suddenly we reboot. This second time we don’t add the magic kernel commandline options, so the remote shell is not running when we reach the Greeter.
Scenario: VirtualBox guest modules are available # features/virtualization.feature:4
Given a computer # features/step_definitions/common_steps.rb:122
And the computer is an old pentium without the PAE extension # features/step_definitions/erase_memory.rb:29
[log] CLICK on (1024,384)
[log] TYPE " autotest_never_use_this_option blacklist=psmouse
"
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
calling as root: echo 'hello?'
And I start Tails from DVD with network unplugged and I login # features/step_definitions/common_steps.rb:196
Remote shell seems to be down
Last ignored exception was: Errno::ECONNRESET: Connection reset by peer @ io_fillbuf - fd:37 (Timeout::Error)
./features/support/helpers/misc_helpers.rb:83:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:33:in `try_for'
./features/support/helpers/exec_helper.rb:16:in `wait_until_remote_shell_is_up'
./features/support/helpers/vm_helper.rb:485:in `wait_until_remote_shell_is_up'
./features/step_definitions/common_steps.rb:345:in `/^the computer (re)?boots Tails$/'
./features/step_definitions/common_steps.rb:204:in `/^I start Tails( from DVD)?( with network unplugged)?( and I login)?$/'
features/virtualization.feature:7:in `And I start Tails from DVD with network unplugged and I login'
When Tails has booted a 32-bit kernel # features/step_definitions/checks.rb:99
Then the VirtualBox guest modules are available # features/step_definitions/checks.rb:126
Scenario failed at time 02:55:57
Files
Subtasks
Related issues
Related to Tails - Bug #11892: Sometimes the remote shell doesn't start because of missing initial Space when modifying the kernel cmdline | In Progress | 2016-10-31 |
History
#1 Updated by intrigeri 2016-12-19 17:10:10
- Subject changed from Test suite cannot sometimes connect to the remote shell: "Errno::ECONNRESET: Connection reset by peer @ io_fillbuf" to Spurious reboot breaks test suite which cannot connect to the remote shell
- Description updated
#2 Updated by intrigeri 2016-12-19 17:11:10
#3 Updated by anonym 2017-01-11 18:57:37
Possible solution: similar to the TAB spamming + reboot madness, we could recover by doing a reboot (+ redo the boot steps) if we reach the Greeter and the remote shell is down.
#4 Updated by Anonymous 2018-08-17 14:54:08
- related to Bug #11892: Sometimes the remote shell doesn't start because of missing initial Space when modifying the kernel cmdline added