Devstack checkouts wrong branch of openstack-requirements at install

[Vadym Markov]

Default devstack installation described in https://docs.openstack.org/devstack/latest/ clones several Openstack components like Nova, Keystone, etc. Branch of every component should correspond to branch of devstack, e.g. stable/pike. Instead of it, openstack-requirements checkouted as master. It leads to fail of Keystone startup: Pike Keystone needs pysaml2 from 2.4.0 to 4.0.2, but master requirements override it and installs pysaml2==4.5.0.

[Dr. Jens Harbott (j-harbott)]

Can you please describe how you could reproduce this? If I run on a fresh machine, devstack does checkout the proper branch of requirements for me. Maybe you did have that repo pre-existing for some reason? Please include your local.conf and attach a full log of your failing stack.sh run.

[Shihta Kuan (shihta)]

I have a similar bug, please refer to:

https://github.com/openstack-dev/devstack/blob/stable/rocky/lib/tempest#L579-L581

I use the branch stable/rocky of devstack for installation.
So by default, devstack is going to checkout the branch stable/rocky of requirements.
And then it failed on:

++lib/tempest:configure_tempest:580 cd /opt/stack/requirements
++lib/tempest:configure_tempest:580 git show master:upper-constraints.txt
fatal: Invalid object name 'master'.

It seems like there are 2 issues:

1. There is no active "master" branch on the folder requirements,
   the instruction might be changed to "git show origin/master:upper-constraints.txt" to avoid error.

2. The version of python package of upper-constraints.txt will be different in each branch.
   It causes conflict as Vadym Markov mentioned.

Is it necessary to use master branch?

[Vadym Markov (vmarkov)]

Yes, it seems to be related

[Launchpad Janitor (janitor)]

[Expired for devstack because there has been no activity for 60 days.]