Hongbin,
I just wanted to follow-up and let a fresh install of the most recent
release is working with no errors.
Thanks so much for your assistance!
Amy (spotz)
On Sun, Jul 15, 2018 at 10:49 AM, Hongbin Lu wrote:
> Hi Amy,
>
> The wrong Keystone URI might be due to the an issue of the
Hi Amy,
The wrong Keystone URI might be due to the an issue of the devstack
plugins. I have proposed fixes [1] [2] for that. Thanks for the suggestion
about adding a note for uninstalling pip packages. I have created a ticket
[3] for that.
[1] https://review.openstack.org/#/c/582799/
[2]
Hongbin,
Doing the pip uninstall did the trick with the Flask version, when running
another debug I did notice an incorrect IP for the Keystone URI and have
restarted the machines networking and cleaned up the /etc/hosts.
When doing a second stack, I did need to uninstall the pip packages again
Hi Amy,
Today, I created a fresh VM with Ubuntu16.04 and run ./stack.sh with your
local.conf, but I couldn't reproduce the two issues you mentioned (the
Flask version conflict issue and 401 issue). By analyzing the logs you
provided, it seems some python packages in your machine are pretty old.
Hongbin,
This was a fresh install from master this week
commit 6312db47e9141acd33142ae857bdeeb92c59994e
Merge: ef35713 2742875
Author: Zuul
Date: Wed Jul 11 20:36:12 2018 +
Merge "Cleanup keystone's removed config options"
Except for builds with my patching kuryr-libnetwork
Hi Amy,
First, I want to confirm which version of devstack you were using? (go to
the devstack folder and type "git log -1").
If possible, I would suggest to do the following steps:
* Run ./unstack
* Run ./clean
* Pull down the latest version of devstack (if it is too old)
* Pull down the
