"no module named keystone" error

[SinumOfficial]

Hey y'all, sorry if I seem like a noob at this, that's because I kinda am a noob when it comes to Linux. Basically, I have followed all instructions to a t, but when i do the ./build.sh 277, it runs the iLO4 toolbox just fine, but throws that error "no module named keystone" from * or whatever. I have attempted to install keystone, but I think it installed via python3 instead of 2? I am not sure how to properly install it, considering you can't normally get python2 without extra commands, and I really don't know what those commands would be for the rest of what I need, if the issue is on my end since I don't have enough knowledge. Thanks!

[SinumOfficial]

Sorry, I forgot to attach a screenshot.

[kendallgoto]

please check the readme for specifics - you do need python2 though. for building, likely the docker solution in the readme will be the easiest to use

[SinumOfficial]

I have tried using either command. You know that python2 isn't accessible anymore unless you use the dev stuff, correct? You can't just sudo apt install pyhton2, it isn't found anymore. And since I'm new to Linux I can't find any guides on how to install python2's keystone. I had to use this link just to install python2 itself. Any (updated, since the readme can't) help would be appreciated. Thanks!

Update: I even found something called "pyenv" but I'm still too new to Linux that it didn't work (I'm sure there's a command I have to use to tell it to use pyenv or something, I don't know). Maybe you can update the instructions with the latest build of Ubuntu? Because it is just not working. And I tried using the docker command, didn't help.

[kendallgoto]

the docker command should work regardless of the dependencies that are missing. what trouble are you having with it?

[SinumOfficial]

I've sent pictures of the issues I've had. I asked my friend who is familiar with Linux to help me out, and he had the same problems following the instructions that I had, and he had to do some seriously convoluted stuff just to get it to compile properly. I'm sending a screenshot of what he did to get it to work. I feel like this should be a thing. Python2 isn't easily accessible anymore, and I think that's what is giving everyone major issues, it's not clearly stated how to get it properly.

[kendallgoto]

there shouldnt be any issue building via the docker and that isolates dependency differences with python2 and python3. working with python2 isn't easy, but it isn't this repo written in python2, it's an upstream dependency. i have a native go implementation i'm writing but i haven't released it.

i cant troubleshoot anything you've provided without actual indication of what doesn't work in the docker environment which appears to work fine for myself and the folks who PR'd it as is.

[legomannetje]

The issue with the v2.77 tag is that the 'pip install -r requirements.txt' is not present. This will indeed give this error, if you add that in the file after the source activate, it will

[joshbrien]

The issue with the v2.77 tag is that the 'pip install -r requirements.txt' is not present. This will indeed give this error, if you add that in the file after the source activate, it will

Legend. This fixed it for me. Thanks!