action #163190: [IBM-HPVS] Establish workflow to run custom BCI container commands and obtain the logs - Containers and images - openSUSE Project Management Tool

Actions

Copy link

action #163190

closed

coordination #117583: [containers] BCI Testing on IBM Hyper Protect Platform (HPVS)

[IBM-HPVS] Establish workflow to run custom BCI container commands and obtain the logs

Added by ph03nix 8 months ago. Updated 4 months ago.

Status:

Resolved

Priority:

High

Assignee:

mloviska

Target version:

Start date:

2024-07-03

Due date:

% Done:

Estimated time:

Tags:

containers

Description

In order to being able to test BCI containers in the IBM-Hyper Protect Platform (HPVS) we need being able to run any already release BCI container from registry.suse.com with custom commands (e.g. true, rpm -q, ...) and obtain the output of this container run.

e.g we would need to run the command echo "Hello World" from the BCI-Base 15-SP6 container and see, if the container runs the echo command and if we can obtain the "Hello World" in the container logs.

This is the base line for any upcoming real test scenarios in IBM HPVS.

This ticket is about establishing a workflow to run custom container commands and obtain the resulting logs

Acceptance criteria¶

Provide ability to run a custom command on an already released SUSE BCI container (registry.suse.com)
Provide ability to obtain the container logs

Related issues 2 (0 open — 2 closed)

Actions

Copy link

Updated by ph03nix 7 months ago

Priority changed from Normal to High

Increasing priority as we have been asked to make this happen rather soon. Martin, don't feel pressed by it but I would say we need to deliver something in 1-2 weeks of time.

Actions

Copy link

Updated by mloviska 7 months ago

Status changed from Workable to In Progress

Actions

Copy link

Updated by mloviska 7 months ago

I see that we have an access to serial

Connected to domain 'k8s_897a95533bd94883a725d6b9f4efd7a9_0787_47cf6dd5-bde7-4ae5-9a03-480add696fae'
Escape character is ^] (Ctrl + ])
# decrypt user-data...
0 token decrypted, 0 encrypted token ignored
# run attestation...
# set hostname...
# finish root disk setup...
# Thu Jul 18 13:44:38 UTC 2024
# HPL11 build:23.6.1 enabler:23.5.1
# HPL11099I: bootloader end
hpcr-dnslookup[395]: HPL14000I: Network connectivity check completed successfully.
hpcr-logging[632]: Configuring logging ...
hpcr-logging[633]: Version [1.1.133]
hpcr-logging[633]: Configuring logging, input [/var/hyperprotect/user-data.decrypted] ...
hpcr-logging[633]: Sending logging probe to [https://logs.eu-gb.logging.cloud.ibm.com/logs/ingest/?hostname=openqa-vm&now=1721310281] ...
hpcr-logging[633]: HPL01010I: Logging has been setup successfully.
hpcr-logging[632]: Logging has been configured
hpcr-catch-failure[735]: VSI has failed to start!
hpcr-catch-failure[735]: HPL10000E: One or more service failed -> systemd triggered hpl-catch-failed service
hpcr-catch-failure[739]: Shutdown scheduled for Thu 2024-07-18 13:49:42 UTC, use 'shutdown -c' to cancel.

Actions

Copy link

Updated by mloviska 7 months ago

Status changed from In Progress to Blocked

# write OS to root disk...
# decrypt user-data...
0 token decrypted, 0 encrypted token ignored
# run attestation...
# set hostname...
# finish root disk setup...
# Mon Jul 22 13:51:47 UTC 2024
# HPL11 build:24.7.1 enabler:24.7.1
# HPL11099I: bootloader end
hpcr-dnslookup[413]: HPL14000I: Network connectivity check completed successfully.
hpcr-logging[425]: Configuring logging ...
hpcr-logging[426]: Version [1.1.163]
hpcr-logging[426]: Configuring logging, input [/var/hyperprotect/user-data.decrypted] ...
hpcr-logging[426]: Sending logging probe to [https://logs.eu-gb.logging.cloud.ibm.com/logs/ingest/?hostname=testing-openqa&now=1721656309] ...
hpcr-logging[426]: Post "https://logs.eu-gb.logging.cloud.ibm.com/logs/ingest/?hostname=testing-openqa&now=1721656309": dial tcp 141.125.86.131:443: i/o timeout
hpcr-catch-failure[527]: VSI has failed to start!
hpcr-catch-failure[527]: HPL10000E: One or more service failed -> systemd triggered hpl-catch-failed service
hpcr-catch-failure[539]: Shutdown scheduled for Mon 2024-07-22 13:57:19 UTC, use 'shutdown -c' to cancel.

Seems like we need to re-configure the logger, I still have my only account that was created by Mike so this is a blocker to me as long as this is not clear what we should do next

Actions

Copy link

Updated by ph03nix 7 months ago

Seems like we need to re-configure the logger, I still have my only account that was created by Mike so this is a blocker to me as long as this is not clear what we should do next

Thanks for the feedback. I contacted Mike about this issue and asked for help.

Actions

Copy link