Welcome to the Linux Foundation Forum!

Devstack fails

Options
ofrommel
ofrommel Posts: 8
in LFS252 Class Forum - Discontinued

While working on Lab 3.2 building devstack on the "compute-node" failed with the following error message:

2016-02-25 10:38:58.356 | Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-b0XZjj/SQLAlchemy-Utils

2016-02-25 10:38:58.891 | + /home/ubuntu/devstack/inc/python:pip_install:L1: exit_trap

2016-02-25 10:38:58.892 | + ./stack.sh:exit_trap:L474: local r=1

2016-02-25 10:38:58.892 | ++ ./stack.sh:exit_trap:L475: jobs -p

2016-02-25 10:38:58.894 | + ./stack.sh:exit_trap:L475: jobs=

2016-02-25 10:38:58.894 | + ./stack.sh:exit_trap:L478: [[ -n '' [[

2016-02-25 10:38:58.894 | + ./stack.sh:exit_trap:L484: kill_spinner

2016-02-25 10:38:58.894 | + ./stack.sh:kill_spinner:L370: '[' '!' -z '' ']'

2016-02-25 10:38:58.894 | + ./stack.sh:exit_trap:L486: [[ 1 -ne 0 [[

2016-02-25 10:38:58.894 | + ./stack.sh:exit_trap:L487: echo 'Error on exit'

2016-02-25 10:38:58.894 | Error on exit

2016-02-25 10:38:58.895 | + ./stack.sh:exit_trap:L488: generate-subunit 1456396675 63 fail

2016-02-25 10:38:59.142 | + ./stack.sh:exit_trap:L489: [[ -z /opt/stack/logs [[

2016-02-25 10:38:59.142 | + ./stack.sh:exit_trap:L492: /home/ubuntu/devstack/tools/worlddump.py -d /opt/stack/logs

2016-02-25 10:38:59.322 | + ./stack.sh:exit_trap:L498: exit 1

I tried the same on my own machine with the same error, so I guess it's a problem with the devstack repo. Maybe you should consider hosting your own copy of devstack?

Comments

  • TangJianyu
    TangJianyu Posts: 5
    edited May 2016
    Options

    Same thing here, I found some tips on the internet but didn't resolve this issue.

     

    2016-05-07 05:33:42.150 | +inc/python:pip_install:1                  exit_trap

    2016-05-07 05:33:42.154 | +./stack.sh:exit_trap:474                  local r=2

    2016-05-07 05:33:42.157 | ++./stack.sh:exit_trap:475                  jobs -p

    2016-05-07 05:33:42.161 | +./stack.sh:exit_trap:475                  jobs=

    2016-05-07 05:33:42.165 | +./stack.sh:exit_trap:478                  [[ -n '' ]]

    2016-05-07 05:33:42.168 | +./stack.sh:exit_trap:484                  kill_spinner

    2016-05-07 05:33:42.172 | +./stack.sh:kill_spinner:370               '[' '!' -z '' ']'

    2016-05-07 05:33:42.176 | +./stack.sh:exit_trap:486                  [[ 2 -ne 0 ]]

    2016-05-07 05:33:42.179 | +./stack.sh:exit_trap:487                  echo 'Error on exit'

    2016-05-07 05:33:42.180 | Error on exit

    2016-05-07 05:33:42.184 | +./stack.sh:exit_trap:488                  generate-subunit 1462598913 309 fail

  • serewicz
    serewicz Posts: 1,000
    Options

    Thank you for letting us know of the issue. DevStack installs software from various repositories during the ./stack.sh process. Some of these repos are hosted for us. It would seem that our host has an issue with the gpg keys. While there is a way to avoid checking the gpg key, it is bad form and poor security. I have asked the support team to look into the issue and hope to report to you that it has been fixed shortly.

    Thank you again for letting us know.

  • serewicz
    serewicz Posts: 1,000
    edited May 2016
    Options

    Hello,

    The labs have been updated to use working repos. Please try the lab again. Remember that each lab section will require using the link for that particular lab. Also, due to a recent change from DevStack you may need to source a file prior to running ./stack.sh. Use the command: source openrc admin to set the parameters prior to running ./stack.sh

  • bike2wrk
    bike2wrk Posts: 14
    edited August 2016
    Options

    Hi,

    Do we have to follow the Devstack setup instructions in Lab Exercise 2.1 before we access OpenStack to complete our labs that require access to OpenStack? 

     

  • serewicz
    serewicz Posts: 1,000
    Options

    Hello Bike,

    Each lab has a link that should start it at the necessary point. So if you wanted to continue you could click on the next lab section and it would already be configured.

    Most sections build on one another. There may be some steps that work without needing all the previous steps, but this has not been tested.

    Best regards,

     

Categories

Upcoming Training