Welcome to the Linux Foundation Forum!

Lab 3.2 stack.sh fails

Options
lenzandy
lenzandy Posts: 6
edited December 2016 in LFS252 Class Forum - Discontinued

stack.sh fails

========

2016-12-21 22:26:03.683 | + cd /opt/stack/nova

2016-12-21 22:26:03.683 | + git checkout stable/liberty

2016-12-21 22:26:03.688 | error: pathspec 'stable/liberty' did not m

atch any file(s) known to git.

2016-12-21 22:26:03.689 | + exit_trap

2016-12-21 22:26:03.689 | + local r=1

2016-12-21 22:26:03.689 | ++ jobs -p

2016-12-21 22:26:03.691 | + jobs=

2016-12-21 22:26:03.691 | + [[ -n '' ]]

2016-12-21 22:26:03.691 | + kill_spinner

2016-12-21 22:26:03.692 | + '[' '!' -z '' ']'

2016-12-21 22:26:03.692 | + [[ 1 -ne 0 ]]

2016-12-21 22:26:03.692 | + echo 'Error on exit'

2016-12-21 22:26:03.692 | Error on exit

2016-12-21 22:26:03.692 | + generate-subunit 1482358693 470 fail

2016-12-21 22:26:04.131 | + [[ -z /opt/stack/logs ]]

2016-12-21 22:26:04.132 | + /home/ubuntu/devstack/tools/worlddump.py

 -d /opt/stack/logs

2016-12-21 22:26:04.317 | + exit 1

=====

then run:

ubuntu@compute-node:~/devstack$ git checkout stable/liberty

Already on 'stable/liberty'

Your branch is up-to-date with 'origin/stable/liberty'.

tried to unstack and clean 2 times with same result

 

 

 

Comments

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

    Hello,

    Did you use the -b stable/liberty entry the first time when you ran git clone... , or is this after having tried it without and having issues? 

    If you pull down the liberty repo after having a newer repo it can have  issues. My suggestion is to either remove the ~/devstack directory in total, edit the local.conf file to reference the -b stable/liberty line, then ./unstack.sh and ./clean.sh commands again. Or you can click on the "Start over" button and just start fresh.

    Regards,

  • lenzandy
    lenzandy Posts: 6
    edited December 2016
    Options

    Yes.  did use -b stable/liberty

    Yes did the "Start over"

    all of the labs are failing...  not just this one.  stack.sh is not successful

     

     

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

    I looked at the last 50 lines of the log file, declared in local.conf. The git location being pulled from openstack.org is throwing an error.  You can see it if you grep for error in the /opt/stack/logs/stack.sh.log file.

    I will investigate why openstack.org, the organization which provides devstack, no longer has that available.

    Regards,

     

Categories

Upcoming Training