)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":31857,"name":"Ayumu Ueha","email":"ueha.ayumu@fujitsu.com","username":"ueha"},"change_message_id":"3e81221f37b754c21a0255db6ddf836230879672","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a4540b4d_d771044c","updated":"2022-08-03 04:45:46.000000000","message":"[memo]\nFT error occur during initializing ceilometer.\nThe following error appears in gnocchi-api:\n```\nJul 29 05:20:41.105688 ubuntu-focal-ovh-bhs1-0030564625\ndevstack@gnocchi-api.service[61040]:   File\n\"/usr/local/lib/python3.8/dist-packages/google/protobuf/descriptor.py\",\nline 755, in __new__\nJul 29 05:20:41.105688 ubuntu-focal-ovh-bhs1-0030564625\ndevstack@gnocchi-api.service[61040]:\n_message.Message._CheckCalledFromGeneratedFile()\nJul 29 05:20:41.105688 ubuntu-focal-ovh-bhs1-0030564625\ndevstack@gnocchi-api.service[61040]: TypeError: Descriptors cannot not be created directly.\nJul 29 05:20:41.105688 ubuntu-focal-ovh-bhs1-0030564625\ndevstack@gnocchi-api.service[61040]: If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc \u003e\u003d 3.19.0.\n```\n\nAnd I found the description about Workaround for the error.\n```\nIf you cannot immediately regenerate your protos, some other possible workarounds are:\n 1. Downgrade the protobuf package to 3.20.x or lower.\n 2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION\u003dpython (but this will use pure-Python parsing and will be much slower).\nMore information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates\n```\n\nPS1 trying to fix temporary with Workaround 2.\nBut it doesn\u0027t seem to be working well..","commit_id":"d3c36a3302e7aa52f8484d937326559162e820a7"},{"author":{"_account_id":31857,"name":"Ayumu Ueha","email":"ueha.ayumu@fujitsu.com","username":"ueha"},"change_message_id":"43f03a2909f611d2646c7f6e2611ef5bd0f69c09","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"458391a3_268ac776","updated":"2022-08-03 14:12:17.000000000","message":"[memo]\nIn PS2~4, I tried downgrading the protobuf version, but it didn\u0027t work..\n```\nThe conflict is caused by:\n    The user requested protobuf\u003c4.0\n    The user requested (constraint) protobuf\u003d\u003d\u003d4.21.3\n```","commit_id":"0bd4bd12cb7d7c7b673c22e87ca8a2c837a7b669"},{"author":{"_account_id":31857,"name":"Ayumu Ueha","email":"ueha.ayumu@fujitsu.com","username":"ueha"},"change_message_id":"ce554f3cb8ee8be9e8ccda62ef7812681196c282","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":5,"id":"74829845_c34ffd00","updated":"2022-08-05 01:15:22.000000000","message":"As we talked at IRC this week, I have confirmed about diss issue to the telemetry team in disscuss ML.\nhttps://meetings.opendev.org/meetings/tacker/2022/tacker.2022-08-02-08.00.log.html#l-34\n\nThere seems to be an error in gnocchi-api, there was Workaround output.\n\u003e If you cannot immediately regenerate your protos, some other possible workarounds are:\n\u003e  1. Downgrade the protobuf package to 3.20.x or lower.\n\u003e  2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION\u003dpython (but this will use pure-Python parsing and will be much slower).\n\u003e More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates\nThere are two, and I tried both but it didn\u0027t work.\n\nI will suggest that you stop using Zuul\u0027s ceilometer until the ceilometer fixes it.\nWhat do you think?","commit_id":"23765d7bdcdbfd832f9c1744e8d9b8e740d161f4"},{"author":{"_account_id":25701,"name":"Yasufumi Ogawa","email":"yasufum.o@gmail.com","username":"yasufum"},"change_message_id":"27bc7bd61982d228840f4fa3c5e7078c0b392062","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"aba93878_3457c143","updated":"2022-08-05 01:24:47.000000000","message":"Oops, the second option looked feasible... Anyway, it\u0027s fine as a quick fix because we\u0027ve not used ceilometer actually. Thanks!","commit_id":"23765d7bdcdbfd832f9c1744e8d9b8e740d161f4"},{"author":{"_account_id":31857,"name":"Ayumu Ueha","email":"ueha.ayumu@fujitsu.com","username":"ueha"},"change_message_id":"2156943fdee55a7a36c5a31411f0eeeefa6c18de","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"c388149b_5321dce9","updated":"2022-08-04 03:48:57.000000000","message":"This patch has patch below as its parent.\n\n851478: Fix IPv4 check failure in UT | https://review.opendev.org/c/openstack/tacker/+/851478","commit_id":"23765d7bdcdbfd832f9c1744e8d9b8e740d161f4"},{"author":{"_account_id":31857,"name":"Ayumu Ueha","email":"ueha.ayumu@fujitsu.com","username":"ueha"},"change_message_id":"f479ea31d9da27ad693b542caba275b2b1d421b9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"671f904f_b0fd2b3f","updated":"2022-08-04 03:06:19.000000000","message":"[memo]\nIn PS5, I removed items related with ceilometer from .zuul.yaml to not use ceilometer during Tacker FT.\nIt is succeeded without any problems.\n\nI think this is a good temporary fix.","commit_id":"23765d7bdcdbfd832f9c1744e8d9b8e740d161f4"},{"author":{"_account_id":31857,"name":"Ayumu Ueha","email":"ueha.ayumu@fujitsu.com","username":"ueha"},"change_message_id":"cfacc8f66cea60c714c98b78f5198e85dfc2ad74","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"5e0f757f_a6829339","in_reply_to":"aba93878_3457c143","updated":"2022-08-05 01:54:18.000000000","message":"Thanks for your comment!\nI tried the second option on the PS1, but it may just be the wrong configuration..\nI wonder that it is the way to set the environment variable correct with the content of PS1?\n\nBut anyway, I think so too it is no problem because ceilometer is not used actually.\nThe contents of this patch must be merged with the patch fixing in UT.\n\n851478: Fix IPv4 check failure in UT | https://review.opendev.org/c/openstack/tacker/+/851478","commit_id":"23765d7bdcdbfd832f9c1744e8d9b8e740d161f4"}]}