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] https://review.openstack.org/#/c/582800/ [3] https://bugs.launchpad.net/zun/+bug/1781807 Best regards, Hongbin On Sun, Jul 15, 2018 at 10:16 AM Amy Marrich <[email protected]> wrote: > 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 > for the second stack.sh to complete, might be worth adding this to the docs > as a note if people have issues. Second install still had the wrong IP > showing as the Keystone URI, I'll try s fresh machine install next. > > Thanks for all your help! > > Amy (spotz) > > On Sat, Jul 14, 2018 at 9:42 PM, Hongbin Lu <[email protected]> wrote: > >> 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. >> First, could you paste me the output of "pip freeze". Second, if possible, >> I would suggest to remove all the python packages and re-stack again as >> following: >> >> * Run ./unstack >> * Run ./clean.sh >> * Run pip freeze | grep -v '^\-e' | xargs sudo pip uninstall -y >> * Run ./stack >> >> Please let us know if above steps still don't work. >> >> Best regards, >> Hongbin >> >> On Sat, Jul 14, 2018 at 5:15 PM Amy Marrich <[email protected]> wrote: >> >>> Hongbin, >>> >>> This was a fresh install from master this week >>> >>> commit 6312db47e9141acd33142ae857bdeeb92c59994e >>> >>> Merge: ef35713 2742875 >>> >>> Author: Zuul <[email protected]> >>> >>> Date: Wed Jul 11 20:36:12 2018 +0000 >>> >>> >>> Merge "Cleanup keystone's removed config options" >>> >>> Except for builds with my patching kuryr-libnetwork locally builds have >>> been done with reclone and fresh /opt/stack directories. Patch has been >>> submitted for the Flask issue >>> >>> https://review.openstack.org/582634 but hasn't passed the gates yet. >>> >>> >>> Following the instructions above on a new pull of devstack: >>> >>> commit 3b5477d6356a62d7d64a519a4b1ac99309d251c0 >>> >>> Author: OpenStack Proposal Bot <[email protected]> >>> >>> Date: Thu Jul 12 06:17:32 2018 +0000 >>> >>> Updated from generate-devstack-plugins-list >>> >>> Change-Id: I8f702373c76953a0a29285f410d368c975ba4024 >>> >>> >>> I'm still able to use the openstack CLI for non-Zun commands but 401 on >>> Zun >>> >>> root@zunui:~# openstack service list >>> >>> >>> +----------------------------------+------------------+------------------+ >>> >>> | ID | Name | Type >>> | >>> >>> >>> +----------------------------------+------------------+------------------+ >>> >>> | 06be414af2fd4d59af8de0ccff78149e | placement | placement >>> | >>> >>> | 0df1832d6f8c4a5aa7b5e8bacf7339f8 | nova | compute >>> | >>> >>> | 3f1b2692a184443c85b631fa7acf714d | heat-cfn | cloudformation >>> | >>> >>> | 3f6bcbb75f684041bf6eeaaf5ab4c14b | cinder | block-storage >>> | >>> >>> | 6e06ac1394ee4872aa134081d190f18e | neutron | network >>> | >>> >>> | 76afda8ecd18474ba382dbb4dc22b4bb | kuryr-libnetwork | kuryr-libnetwork >>> | >>> >>> | 7b336b8b9b9c4f6bbcc5fa6b9400ccaf | cinderv3 | volumev3 >>> | >>> >>> | a0f83f30276d45e2bd5fd14ff8410380 | nova_legacy | compute_legacy >>> | >>> >>> | a12600a2467141ff89a406ec3b50bacb | cinderv2 | volumev2 >>> | >>> >>> | d5bfb92a244b4e7888cae28ca6b2bbac | keystone | identity >>> | >>> >>> | d9ea196e9cae4b0691f6c4b619eb47c9 | zun | container >>> | >>> >>> | e528282e291f4ddbaaac6d6c82a0036e | cinder | volume >>> | >>> >>> | e6078b2c01184f88a784b390f0b28263 | glance | image >>> | >>> >>> | e650be6c67ac4e5c812f2a4e4cca2544 | heat | orchestration >>> | >>> >>> >>> +----------------------------------+------------------+------------------+ >>> >>> root@zunui:~# openstack appcontainer list >>> >>> Unauthorized (HTTP 401) (Request-ID: >>> req-e44f5caf-642c-4435-ab1d-98feae1fada9) >>> >>> root@zunui:~# zun list >>> >>> ERROR: Unauthorized (HTTP 401) (Request-ID: >>> req-587e39d6-463f-4921-b45b-29576a00c242) >>> >>> >>> Thanks, >>> >>> >>> Amy (spotz) >>> >>> >>> >>> On Fri, Jul 13, 2018 at 10:34 PM, Hongbin Lu <[email protected]> >>> wrote: >>> >>>> 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 latest version of all the projects under /opt/stack/ >>>> * Run ./stack >>>> >>>> If above steps couldn't resolve the problem, please let me know. >>>> >>>> Best regards, >>>> Hongbin >>>> >>>> >>>> On Fri, Jul 13, 2018 at 10:33 AM Amy Marrich <[email protected]> wrote: >>>> >>>>> Hongbin, >>>>> >>>>> Let me know if you still want me to mail the dev list, but here are >>>>> the gists for the installations and the broken CLI I mentioned >>>>> >>>>> local.conf - which is basically the developer quickstart instructions >>>>> for Zun >>>>> >>>>> https://gist.github.com/spotz/69c5cfa958b233b4c3d232bbfcc451ea >>>>> >>>>> >>>>> This is the failure with a fresh devstack installation >>>>> >>>>> https://gist.github.com/spotz/14e19b8a3e0b68b7db2f96bff7fdf4a8 >>>>> >>>>> >>>>> Requirements repo change a few weeks ago >>>>> >>>>> >>>>> http://git.openstack.org/cgit/openstack/requirements/commit/?id=cb6c00c01f82537a38bd0c5a560183735cefe2f9 >>>>> >>>>> >>>>> Changed local Flask version for curry-libnetwork and set local.conf to >>>>> reclone=no and then installed and tried to use the CLI. >>>>> >>>>> https://gist.github.com/spotz/b53d729fc72d24b4454ee55519e72c07 >>>>> >>>>> >>>>> It makes sense that Flask would cause an issue on the UI installation >>>>> even though it's enabled even for a non-enabled build according to the >>>>> quickstart doc. I don't mind doing a patch to fix kuryr-libnetwork to >>>>> bring >>>>> it up to the current requirements. I don't however know where to start >>>>> troubleshooting the 401 issue. On a different machine I have decstack with >>>>> Zun but no zun-ui and the CLI responds correctly. >>>>> >>>>> >>>>> Thanks, >>>>> >>>>> Amy (spotz) >>>>> >>>>> >>>>> On Thu, Jul 12, 2018 at 11:21 PM, Hongbin Lu <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Amy, >>>>>> >>>>>> I am also in doubts about the Flask version issue. Perhaps you can >>>>>> provide more details about this issue? Do you see any error message? >>>>>> >>>>>> Best regards, >>>>>> Hongbin >>>>>> >>>>>> On Thu, Jul 12, 2018 at 10:49 PM Shu M. <[email protected]> wrote: >>>>>> >>>>>>> >>>>>>> Hi Amy, >>>>>>> >>>>>>> Thank you for sharing the issues. Zun UI does not require >>>>>>> kuryr-libnetwork directly, and keystone seems to have same requirements >>>>>>> for >>>>>>> Flask. So I wonder why install failure occurred by Zun UI. >>>>>>> >>>>>>> Could you share your correction for requrements. >>>>>>> >>>>>>> Unfortunately, I'm in trouble on my development environment since >>>>>>> yesterday. So I can not investigate the issues quickly. >>>>>>> I added Hongbin to this topic, he would help us. >>>>>>> >>>>>>> Best regards, >>>>>>> Shu Muto >>>>>>> >>>>>>> 2018年7月13日(金) 9:29 Amy Marrich <[email protected]>: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I was given your email on the #openstack-zun channel as a source >>>>>>>> for questions for the UI. I've found a few issues installing the Master >>>>>>>> branch on devstack and not sure if they should be bugged. >>>>>>>> >>>>>>>> kuryr-libnetwork has incorrect versions for Flask in both >>>>>>>> lower-constraints.txt and requirements.txt, this only affects >>>>>>>> installation >>>>>>>> when enabling zun-ui, I'll be more then happy to bug and patch it, if >>>>>>>> confirmed as an issue. >>>>>>>> >>>>>>>> Once correcting the requirements locally to complete the devstack >>>>>>>> installation, I'm receiving 401s when using both the OpenStack CLI and >>>>>>>> Zun >>>>>>>> client. I'm also unable to create a container within Horizon. The same >>>>>>>> credentials work fine for other OpenStack commands. >>>>>>>> >>>>>>>> On another server without the ui enabled I can use both the CLI and >>>>>>>> client no issues. I'm not sure if there's something missing on >>>>>>>> https://docs.openstack.org/zun/latest/contributor/quickstart.html >>>>>>>> or some other underlying issue. >>>>>>>> >>>>>>>> Any help or thoughts appreciated! >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> Amy (spotz) >>>>>>>> >>>>>>>> >>>>> >>> >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
