[Rdo-list] How works CI for https://git.openstack.org/cgit/openstack/magnum/log/?h=stable/mitaka ?

Boris Derzhavets bderzhavets at hotmail.com
Sun Mar 27 20:33:29 UTC 2016


Commits which  causing trouble mentioned in
<https://www.redhat.com/archives/rdo-list/2016-March/msg00157.html>

https://www.redhat.com/archives/rdo-list/2016-March/msg00157.html


<https://www.redhat.com/archives/rdo-list/2016-March/msg00157.html>

  are  following two


https://git.openstack.org/cgit/openstack/magnum/commit/?h=stable/mitaka&id=db676bcde0b301c1cd1a4346687b3cef02390e8c

date 2016-03-09


https://git.openstack.org/cgit/openstack/magnum/commit/?h=stable/mitaka&id=7e58172a60f258f91e74320f7aee05009fbd1554

date 2016-03-11


Testing  openstack-magnum-2.0.1-0.20160324110644.c0c2bdb.el7.centos.src.rpm                                        2016-03-24 11:07 523K  from https://trunk.rdoproject.org/centos7-mitaka/current-passed-ci/


rpm -iv openstack-magnum-2.0.1-0.20160324110644.c0c2bdb.el7.centos.src.rpm

cd ;

cd rpmbuild/SPEC

rpmbuild -bb openstack-magnum.spec ( previously installed all dependencies )

cd ../RPMS/noarch


yum install openstack-magnum-api-2.0.1-0.20160324110644.c0c2bdb.el7.centos.noarch.rpm \
openstack-magnum-common-2.0.1-0.20160324110644.c0c2bdb.el7.centos.noarch.rpm \
openstack-magnum-conductor-2.0.1-0.20160324110644.c0c2bdb.el7.centos.noarch.rpm \
openstack-magnum-doc-2.0.1-0.20160324110644.c0c2bdb.el7.centos.noarch.rpm \
python-magnum-2.0.1-0.20160324110644.c0c2bdb.el7.centos.noarch.rpm \
python-magnum-tests-2.0.1-0.20160324110644.c0c2bdb.el7.centos.noarch.rpm


systemctl start openstack-magnum-api.service ;

systemctl start openstack-magnum-conductor.service ;

systemctl enable openstack-magnum-api.service ;

systemctl enable  openstack-magnum-conductor.service ;


[root at ip-192-169-142-127 noarch]# systemctl | grep magnum
openstack-magnum-api.service         loaded active running   OpenStack Magnum API Service
openstack-magnum-conductor.service  loaded active running   Openstack Magnum Conductor Service


openstack-magnum-2.0.1-0.20160324110644.c0c2bdb.el7.centos.src.rpm  seems to to have no idea

about two commits mentioned above , giving me error :-

Run as admin as suggested in http://egonzalez.org/magnum-in-rdo-openstack-liberty-manual-installation-from-source-code/

# magnum bay-create --name demoswarmbay --baymodel demoswarmbaymodel \
           --master-count 1 --node-count 1

Create for bay swarmbay failed: Failed to create trustee %(username) in domain $(domain_id) (HTTP 500)"


Here I follow explanation done in  http://osdir.com/ml/openstack-dev/2016-02/msg02123.html

<http://osdir.com/ml/openstack-dev/2016-02/msg02123.html>which is advising to fix an error using keystone V3


Script 1

# 1. create the necessary domain and user:

export OS_TOKEN=bf2585734da14520868414d44dbe72c7

export OS_URL=http://127.0.0.1:5000/v3
export OS_IDENTITY_API_VERSION=3
openstack domain create magnum
openstack user create trustee_domain_admin --password=secret --domain=magnum
openstack role add --user=trustee_domain_admin --domain=magnum admin


Script 2 ( just cloned devstack to current folder to source functions )


# 2. populate configs
source /root/devstack/functions
export MAGNUM_CONF=/etc/magnum/magnum.conf
iniset $MAGNUM_CONF trust trustee_domain_id $(openstack domain show magnum | awk '/ id /{print $4}')
iniset $MAGNUM_CONF trust trustee_domain_admin_id $(openstack user show trustee_domain_admin | awk '/ id /{print $4}')
iniset $MAGNUM_CONF trust trustee_domain_admin_password secret


I completed both ( ran with #!/bin/bash -x ).  All done , but having currently running keystone v2.0

it doesn't help. I keep getting same error.


I am not keystone expert, but looks like I need to go through procedure like described here

"Migrate from keystone v2.0 to keystone v3 OpenStack Liberty"

http://egonzalez.org/migrate-from-keystone-v2-0-to-keystone-v3-openstack-liberty/



Thank you.

Boris.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20160327/c38c58ce/attachment.html>


More information about the dev mailing list