Re: [openstack-dev] [Zun] Zun UI questions
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 wrote: > 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 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 > > Date: Thu Jul 12 06:17:32 2018 + > > 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 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 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
Re: [openstack-dev] [tripleo] Mistral workflow cannot establish connection
It is a bad line in one of your yaml file. I would check them.
Sent from my iPad
> On Jul 14, 2018, at 2:25 PM, Samuel Monderer
> wrote:
>
> Hi,
>
> I'm trying to deploy redhat OSP13 but I get the following error.
> (undercloud) [root@staging-director stack]# ./templates/deploy.sh
> Started Mistral Workflow
> tripleo.validations.v1.check_pre_deployment_validations. Execution ID:
> 3ba53aa3-56c5-4024-8d62-bafad967f7c2
> Waiting for messages on queue 'tripleo' with no timeout.
> Removing the current plan files
> Uploading new plan files
> Started Mistral Workflow tripleo.plan_management.v1.update_deployment_plan.
> Execution ID: ff359b14-78d7-4b64-8b09-6ec3c4697d71
> Plan updated.
> Processing templates in the directory
> /tmp/tripleoclient-ae4yIf/tripleo-heat-templates
> Unable to establish connection to
> https://192.168.50.30:13989/v2/action_executions: ('Connection aborted.',
> BadStatusLine("''",))
> (undercloud) [root@staging-director stack]#
>
> Couldn't find any info in the logs of what causes the error.
>
> Samuel
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [tripleo] Mistral workflow cannot establish connection
Hi,
I'm trying to deploy redhat OSP13 but I get the following error.
(undercloud) [root@staging-director stack]# ./templates/deploy.sh
Started Mistral Workflow
tripleo.validations.v1.check_pre_deployment_validations. Execution ID:
3ba53aa3-56c5-4024-8d62-bafad967f7c2
Waiting for messages on queue 'tripleo' with no timeout.
Removing the current plan files
Uploading new plan files
Started Mistral Workflow tripleo.plan_management.v1.update_deployment_plan.
Execution ID: ff359b14-78d7-4b64-8b09-6ec3c4697d71
Plan updated.
Processing templates in the directory
/tmp/tripleoclient-ae4yIf/tripleo-heat-templates
Unable to establish connection to
https://192.168.50.30:13989/v2/action_executions: ('Connection aborted.',
BadStatusLine("''",))
(undercloud) [root@staging-director stack]#
Couldn't find any info in the logs of what causes the error.
Samuel
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Zun] Zun UI questions
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 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 Date: Thu Jul 12 06:17:32 2018 + 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 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 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 >> 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. 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
Re: [openstack-dev] [kolla-ansible] how do I unify log data format
On 07/14/2018 07:29 AM, Sergey Glazyrin wrote: Hello guys! We are migrating our product to kolla-ansible and as far as probably you know, it uses fluentd to control logs, etc. In non containerized openstack we use rsyslog to send data to logstash. Why not use rsyslog in containerized openstack too? Why not use rsyslog to mutate/unify the records? Why use logstash? Note that rsyslog can send records to elasticsearch, and the latest rsyslog 8.36 has enhanced the elasticsearch plugin to do client cert auth as well as handle bulk index retries more efficiently. We get data from syslog events. It looks like it's impossible to use syslog in kolla-ansible. Unfortunately external_syslog_server option doesn't work. Is there anyone who was able to use it ? But, nevermind, we may use fluentd BUT.. we have one problem - different data format for each service/container. So, probably the most optimal solution is to use default logging idea in kolla-ansible. (to be honest, I am not sure... but I've no found better option). But even with default logging idea in kolla - ansible we have one serious problem. Fluentd has different data format for each service, for instance, you may see this link with explanation how its designed in kolla-ansible https://github.com/openstack/kolla-ansible/commit/3026cef7cfd1828a27e565d4211692f0ab0ce22e there are grok patterns which parses log messages, etc so, we managed to put data to elasticsearch but we need to solve two problems: 1. unify data format for log events. We may solve it using logstash to unify it before putting it to elasticsearch (or should we change fluentd configs in our own version of kolla-ansible repository ? ) For instance, we may do it using this logstash plugin https://www.elastic.co/guide/en/logstash/2.4/plugins-filters-mutate.html#plugins-filters-mutate-rename What's your suggestion ? -- Best, Sergey __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [kolla-ansible] how do I unify log data format
Hello guys! We are migrating our product to kolla-ansible and as far as probably you know, it uses fluentd to control logs, etc. In non containerized openstack we use rsyslog to send data to logstash. We get data from syslog events. It looks like it's impossible to use syslog in kolla-ansible. Unfortunately external_syslog_server option doesn't work. Is there anyone who was able to use it ? But, nevermind, we may use fluentd BUT.. we have one problem - different data format for each service/container. So, probably the most optimal solution is to use default logging idea in kolla-ansible. (to be honest, I am not sure... but I've no found better option). But even with default logging idea in kolla - ansible we have one serious problem. Fluentd has different data format for each service, for instance, you may see this link with explanation how its designed in kolla-ansible https://github.com/openstack/kolla-ansible/commit/3026cef7cfd1828a27e565d4211692f0ab0ce22e there are grok patterns which parses log messages, etc so, we managed to put data to elasticsearch but we need to solve two problems: 1. unify data format for log events. We may solve it using logstash to unify it before putting it to elasticsearch (or should we change fluentd configs in our own version of kolla-ansible repository ? ) For instance, we may do it using this logstash plugin https://www.elastic.co/guide/en/logstash/2.4/plugins-filters-mutate.html#plugins-filters-mutate-rename What's your suggestion ? -- Best, Sergey __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
