Run Test: slices-bi-singlenode-login
2026-03-04 16:00:48.952647 CET - Run: /usr/local/bin/uv pip install --upgrade slices-cli --extra-index-url=https://doc.slices-ri.eu/pypi/
2026-03-04 16:00:52.004437 CET - Run: slices --version
2026-03-04 16:00:52.181432 CET - version: Slices CLI v2025.1.5
Slices CLI core v1.1.2
Slices CLI bi v2.0.2
Slices clientlib core v5.3.8
Slices clientlib bi v5.1.2
2026-03-04 16:00:52.181686 CET - Run: slices pubkey list --format text
2026-03-04 16:00:52.879242 CET - Pubkey already registered
2026-03-04 16:00:52.879466 CET - Run: slices bi infrastructure list --format csv --all --refresh
2026-03-04 16:00:53.367736 CET - Refreshed infrastructure list. Total: 22 entries.
2026-03-04 16:00:53.367826 CET - Check List Flavors
2026-03-04 16:00:53.367993 CET - Run: slices bi --infra de-munich-bi-vm flavor list -f json
2026-03-04 16:00:54.331732 CET - Check List DiskImages
2026-03-04 16:00:54.331914 CET - Run: slices bi --infra de-munich-bi-vm diskimage list -f json
2026-03-04 16:00:54.918025 CET - Requesting resources
2026-03-04 16:00:54.918478 CET - Run: slices bi --infra de-munich-bi-vm create tst --image 'Ubuntu 24.04.3' --flavor tiny --duration 2h --experiment tst-58c6c952 --user-data /tmp/tmpbb5mp8ly
2026-03-04 16:01:02.156691 CET - Resource ID: r_de-munich-bi-vm_01kjwnvpxqf1gv7n16g6qqxbfw
2026-03-04 16:01:02.156898 CET - Waiting until resource ready
2026-03-04 16:01:04.157274 CET - Run: slices bi --infra de-munich-bi-vm list-resources --format json --experiment tst-58c6c952 tst
2026-03-04 16:01:04.830132 CET - Status: IMAGING
2026-03-04 16:01:07.516617 CET - Status: IMAGING
2026-03-04 16:01:10.220889 CET - Status: IMAGING
2026-03-04 16:01:12.900660 CET - Status: IMAGING
2026-03-04 16:01:15.615589 CET - Status: IMAGING
2026-03-04 16:01:18.310375 CET - Status: BOOTING
2026-03-04 16:01:20.981766 CET - Status: BOOTING
2026-03-04 16:01:23.668093 CET - Status: BOOTING
2026-03-04 16:01:26.338736 CET - Status: BOOTING
2026-03-04 16:01:29.053233 CET - Status: BOOTING
2026-03-04 16:01:31.721442 CET - Status: BOOTING
2026-03-04 16:01:34.397645 CET - Status: BOOTING
2026-03-04 16:01:37.077372 CET - Status: BOOTING
2026-03-04 16:01:39.762985 CET - Status: BOOTING
2026-03-04 16:01:42.487023 CET - Status: BOOTING
2026-03-04 16:01:45.157996 CET - Status: BOOTING
2026-03-04 16:01:47.840349 CET - Status: BOOTING
2026-03-04 16:01:53.522171 CET - Content of log file '/opt/slices-monitor-worker/slices_monitor_tests/03eed1dc-df45-4e5b-a0e0-df1528a2cf30/step_WaitforUP_command_1.txt':
/opt/slices-monitor-worker/slices-cli-venv/bin/slices bi --infra de-munich-bi-vm list-resources --format json --experiment tst-58c6c952 tst
2026-03-04 16:01:53.522245 CET - Content of log file '/opt/slices-monitor-worker/slices_monitor_tests/03eed1dc-df45-4e5b-a0e0-df1528a2cf30/list-resources_json.txt':
There was a connection problem. The service might be down. ⚡
Details: ServiceException (for GET
https://slices-bi.slices-de.eu/apis/bi.slices.eu/v1/projects/proj_account.ilabt.
imec.be_5pzabws7n79ydsagfg3vntg590/experiments/exp_expauth.ilabt.imec.be_01kjwnv
h07fdgs10gwth3x3pj5/resources/): 503 Service Unavailable
No server is available to handle this request.
2026-03-04 16:01:53.522267 CET - Error in test step 'Wait for UP': "slices bi print" failed
2026-03-04 16:01:53.522291 CET - Destroying tst-58c6c952 tst
2026-03-04 16:01:53.522432 CET - Run: slices bi --infra de-munich-bi-vm destroy --experiment tst-58c6c952 tst
2026-03-04 16:01:57.210790 CET - Content of log file '/opt/slices-monitor-worker/slices_monitor_tests/03eed1dc-df45-4e5b-a0e0-df1528a2cf30/step_Destroy_command_1.txt':
/opt/slices-monitor-worker/slices-cli-venv/bin/slices bi --infra de-munich-bi-vm destroy --experiment tst-58c6c952 tst
2026-03-04 16:01:57.210863 CET - Content of log file '/opt/slices-monitor-worker/slices_monitor_tests/03eed1dc-df45-4e5b-a0e0-df1528a2cf30/destroy.txt':
There was a connection problem. The service might be down. ⚡
Details: ServiceException (for GET
https://slices-bi.slices-de.eu/apis/bi.slices.eu/v1/projects/proj_account.ilabt.
imec.be_5pzabws7n79ydsagfg3vntg590/experiments/exp_expauth.ilabt.imec.be_01kjwnv
h07fdgs10gwth3x3pj5/resources/): 503 Service Unavailable
No server is available to handle this request.
2026-03-04 16:01:57.210885 CET - Error in test step 'Destroy': "slices bi destroy" failed (return value is 1)
2026-03-04 16:01:57.210906 CET - Wait 2s before retry
2026-03-04 16:01:59.888266 CET - Content of log file '/opt/slices-monitor-worker/slices_monitor_tests/03eed1dc-df45-4e5b-a0e0-df1528a2cf30/step_DestroyRetry1_retry1_command_1.txt':
/opt/slices-monitor-worker/slices-cli-venv/bin/slices bi --infra de-munich-bi-vm destroy --experiment tst-58c6c952 tst
2026-03-04 16:01:59.888357 CET - Content of log file '/opt/slices-monitor-worker/slices_monitor_tests/03eed1dc-df45-4e5b-a0e0-df1528a2cf30/destroy_retry1.txt':
There was a connection problem. The service might be down. ⚡
Details: ServiceException (for GET
https://slices-bi.slices-de.eu/apis/bi.slices.eu/v1/projects/proj_account.ilabt.
imec.be_5pzabws7n79ydsagfg3vntg590/experiments/exp_expauth.ilabt.imec.be_01kjwnv
h07fdgs10gwth3x3pj5/resources/): 503 Service Unavailable
No server is available to handle this request.
2026-03-04 16:01:59.888378 CET - Error in test step 'Destroy (Retry 1)': "slices bi destroy" failed (return value is 1)
2026-03-04 16:01:59.888399 CET - Wait 2s before retry
2026-03-04 16:02:02.576768 CET - Content of log file '/opt/slices-monitor-worker/slices_monitor_tests/03eed1dc-df45-4e5b-a0e0-df1528a2cf30/step_DestroyRetry2_retry2_command_1.txt':
/opt/slices-monitor-worker/slices-cli-venv/bin/slices bi --infra de-munich-bi-vm destroy --experiment tst-58c6c952 tst
2026-03-04 16:02:02.576842 CET - Content of log file '/opt/slices-monitor-worker/slices_monitor_tests/03eed1dc-df45-4e5b-a0e0-df1528a2cf30/destroy_retry2.txt':
There was a connection problem. The service might be down. ⚡
Details: ServiceException (for GET
https://slices-bi.slices-de.eu/apis/bi.slices.eu/v1/projects/proj_account.ilabt.
imec.be_5pzabws7n79ydsagfg3vntg590/experiments/exp_expauth.ilabt.imec.be_01kjwnv
h07fdgs10gwth3x3pj5/resources/): 503 Service Unavailable
No server is available to handle this request.
2026-03-04 16:02:02.576861 CET - Error in test step 'Destroy (Retry 2)': "slices bi destroy" failed (return value is 1)
2026-03-04 16:02:02.576880 CET - Wait 2s before retry
2026-03-04 16:02:05.256882 CET - Content of log file '/opt/slices-monitor-worker/slices_monitor_tests/03eed1dc-df45-4e5b-a0e0-df1528a2cf30/step_DestroyRetry3_retry3_command_1.txt':
/opt/slices-monitor-worker/slices-cli-venv/bin/slices bi --infra de-munich-bi-vm destroy --experiment tst-58c6c952 tst
2026-03-04 16:02:05.256962 CET - Content of log file '/opt/slices-monitor-worker/slices_monitor_tests/03eed1dc-df45-4e5b-a0e0-df1528a2cf30/destroy_retry3.txt':
There was a connection problem. The service might be down. ⚡
Details: ServiceException (for GET
https://slices-bi.slices-de.eu/apis/bi.slices.eu/v1/projects/proj_account.ilabt.
imec.be_5pzabws7n79ydsagfg3vntg590/experiments/exp_expauth.ilabt.imec.be_01kjwnv
h07fdgs10gwth3x3pj5/resources/): 503 Service Unavailable
No server is available to handle this request.
2026-03-04 16:02:05.256982 CET - Error in test step 'Destroy (Retry 3)': "slices bi destroy" failed (return value is 1)