Questions about kernelCI tools

林 拓真 <[email protected]>
Newsgroups dev.linux.lists.kernelci
Message-ID <OSZPR01MB878233DCFD867C7C54A941F4B53F2@OSZPR01MB8782.jpnprd01.prod.outlook.com>
Hello community.

I am currently trying to run LTP test on LavaLab with Maestro and KCIDB.
Also have currently considered building all modules of KernelCI "on-premise".
then I have two questions about the way I am trying.

Question 1:
Is it possible to get rid of the dependency on GoogleCloud?
(So I am looking for the right way to build KernelCI on-premise more quick and easier…)

Question 2:
I encountered the error below while trying to build Maestro and,
trying to get the API access token for connecting to the kernelci-api container from the pipeline.
Following steps here I have tried: (Referred to https://docs.kernelci.org/admin/api/)
----------------------------------------------------------
Step 1. Run bash in the kernelci-api container.         
$ docker exec ?it kernelci-api /bin/bash

Step 2. Create an administrator within the api app.
$ python3 ?m api.admin ?email “<administrator-mail-address>”
   (trapped) error reading bcrypt version
   Traceback (most recent call last):
   File "/usr/local/lib/python3.11/site-packages/passlib/handlers/bcrypt.py", line 620, in _load_backend_mixin
   version = _bcrypt.__about__.__version__
                           ^^^^^^^^^^^^^^^^^
   AttributeError: module 'bcrypt' has no attribute '__about__’
   Creating admin user...

This above error I encountered does not seem to be fatal as far as I read the KernelCI implementation.
then I went to the next step.

3. Obtain the token of the administrator in the api app.
$ kci user token admin
Error: KerError: Value not found for None
----------------------------------------------------------
Is there any missing steps I should do before?

Thank you.
Hayashi
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.