Ask Your Question
0

Devstack installation fails on Debian 8

asked 2017-08-09 08:57:10 -0600

m34567890 gravatar image

updated 2017-08-11 03:09:47 -0600

Below the output of stack.sh

++functions-common:is_service_enabled:2155  set +o
++functions-common:is_service_enabled:2155  grep xtrace
+functions-common:is_service_enabled:2155  xtrace='set -o xtrace'
+functions-common:is_service_enabled:2156  set +o xtrace
+functions-common:is_service_enabled:2184  return 1
+lib/keystone:start_keystone:575           restart_service memcached
+functions-common:restart_service:2393     '[' -x /bin/systemctl ']'
+functions-common:restart_service:2394     sudo /bin/systemctl restart memcached
+./stack.sh:main:1125                      bootstrap_keystone
+lib/keystone:bootstrap_keystone:604       /usr/local/bin/keystone-manage bootstrap --bootstrap-username admin --bootstrap-password secret --bootstrap-project-name admin --bootstrap-role-name admin --bootstrap-service-name keystone --bootstrap-region-id RegionOne --bootstrap-admin-url http://192.168.3.20/identity --bootstrap-public-url http://192.168.3.20/identity
DEBUG keystone.notifications [-] Callback: `keystone.assignment.core.Manager._delete_domain_assignments` subscribed to event `identity.domain.deleted`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.identity.core.Manager._unset_default_project` subscribed to event `identity.project.deleted`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.identity.core.Manager._domain_deleted` subscribed to event `identity.domain.deleted`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.revoke.core.Manager._trust_callback` subscribed to event `identity.OS-TRUST:trust.deleted`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.revoke.core.Manager._consumer_callback` subscribed to event `identity.OS-OAUTH1:consumer.deleted`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.revoke.core.Manager._user_callback` subscribed to event `identity.user.deleted`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.revoke.core.Manager._project_callback` subscribed to event `identity.project.deleted`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.revoke.core.Manager._user_callback` subscribed to event `identity.user.disabled`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.revoke.core.Manager._project_callback` subscribed to event `identity.project.disabled`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.revoke.core.Manager._domain_callback` subscribed to event `identity.domain.disabled`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.revoke.core.Manager._user_callback` subscribed to event `identity.invalidate_user_tokens.internal`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.trust.core.Manager._on_user_delete` subscribed to event `identity.user.deleted`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.token.provider.Manager._trust_deleted_event_callback` subscribed to event `identity.OS-TRUST:trust.deleted`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.token.provider.Manager._delete_user_tokens_callback` subscribed to event `identity.user.deleted`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.token.provider.Manager._delete_domain_tokens_callback` subscribed to event `identity.domain.deleted`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications [-] Callback: `keystone.token.provider.Manager._delete_user_tokens_callback` subscribed to event `identity.user.disabled`. {{(pid=6598) register_event_callback /opt/stack/keystone/keystone/notifications.py:235}}
DEBUG keystone.notifications ...
(more)
edit retag flag offensive close merge delete

Comments

Apache or the Apache Keystone module are not running. Is 192.168.3.20 the correct address? Do you find errors related to Keystone or Apache further up in the log? What is your local.conf file? What about systemctl status apache2?

Bernd Bausch gravatar imageBernd Bausch ( 2017-08-09 19:12:03 -0600 )edit

I added the information to the question, thank you for taking your time looking at my problem!!!!

m34567890 gravatar imagem34567890 ( 2017-08-11 03:10:11 -0600 )edit

systemctl says

Active: inactive (dead) since Fri 2017-08-11

You need to find out why.

Admittedly I don't know milestone-proposed. To me, it sounds like "bleeding edge, might not work". Did you try different branches?

Bernd Bausch gravatar imageBernd Bausch ( 2017-08-11 11:51:57 -0600 )edit

Perhaps you have to set the IP address in local.conf. I faintly remember that DevStack takes the first interface by default, which is eth0 in your case.

Bernd Bausch gravatar imageBernd Bausch ( 2017-08-11 11:55:33 -0600 )edit

Thank you very much, I will try to use the normal branch and set the IP-Adress manually.

m34567890 gravatar imagem34567890 ( 2017-08-14 00:50:12 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-08-14 01:07:44 -0600

m34567890 gravatar image

I moved to a freshly installed Ubuntu Server 17.04, where the normal Setup script works flawlessly.

But as soon as I add the lines for OpenDaylight installation according to their setup guide to the local.conf it stops working again.. https://ask.openstack.org/en/question/109609/opendaylight-netvirt-installation-via-devstack-fails/ (https://ask.openstack.org/en/question...)

Anyway, thanks for your help!

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-08-09 08:57:10 -0600

Seen: 60 times

Last updated: Aug 14