February 2023 - openstack-discuss

[all][docs] Inconsistencies in api-ref rendering - impacting compute and baremetal api-ref, maybe others
by Jay Faulkner 01 Mar '23

01 Mar '23

Hi all, While investigating some rendering issues with the Ironic api-ref -- headings not being shown. We discovered a strange configuration in openstackdocstheme. We're not really certain how it's broken, but there is a visual problem that needs to be fixed either in the theme or in Ironic's (and others') content. If you look at https://docs.openstack.org/api-ref/baremetal/ -- you'll notice there are no primary headers. This is because they are in a rst construct rendered as an h1, which the CSS in the openstackdocstheme renders to display:none: https://github.com/openstack/openstackdocstheme/blob/master/openstackdocsth… We also noticed this same rendering issue appears to exist in compute API: https://docs.openstack.org/api-ref/compute/ But not for Neutron: https://docs.openstack.org/api-ref/network/v2/index.html. It appears that neutron has added an additional layer of headers which are rendering ( https://raw.githubusercontent.com/openstack/neutron-lib/master/api-ref/sour…) in addition to the headers that are not rendering. This behavior has been in the openstackdocstheme for years, it was introduced in https://github.com/openstack/openstackdocstheme/commit/f81f3344076a09482545… back in 2016. This raises some questions * What's the correct fix? Dmitry is exploring options to do a neutron-style workaround in our Ironic api-ref to make them render properly for us; but given it's (effectively) broken for Nova as well is an interesting data point that might indicate a fix in the theme is needed. * Are other openstack projects/APIs impacted by this? I'm not a documentation or front end html/css expert, so I'm hoping folks with more historical context and front end knowledge can respond here and help us determine which way to go. In lieu of further input, Ironic will fix our api-ref in the same method that Neutron has appeared to be taking and I suggest Nova do the same. Thanks, Jay Faulkner Ironic PTL TC Member

4 6

openstack(train) Nova does not support Cinder API version 2
by zhang yan 01 Mar '23

01 Mar '23

hi i setup a study environment refer to the Minimal deployment for Train( https://docs.openstack.org/install-guide/openstack-services.html) . when i finish the Block Storage service install, and create a volume successfully. then i attach the volume to a compute instance, but the nova-compute log hint： 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server [req-24fde26d-3665-492c-8ce6-067bd793b864 bf6dc19622da48e59a272fc3daa292e5 b99ceef1d97c4aac89d15c732a5e1b0a - default default] Exception during message handling: UnsupportedCinderAPIVersion: Nova does not support Cinder API version 2 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 274, in dispatch 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 79, in wrapped 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server function_name, call_dict, binary, tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 69, in wrapped 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return f(self, context, *args, **kw) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/utils.py", line 1372, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 219, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server kwargs['instance'], e, sys.exc_info()) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 207, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6126, in attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server do_attach_volume(context, instance, driver_bdm) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", line 328, in inner 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6124, in do_attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server bdm.destroy() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6121, in do_attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return self._attach_volume(context, instance, driver_bdm) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6156, in _attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server context, bdm['attachment_id']) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 399, in wrapper 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = method(self, ctx, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 450, in wrapper 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = method(self, ctx, attachment_id, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 68, in wrapped_f 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return Retrying(*dargs, **dkw).call(f, *args, **kw) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 223, in call 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return attempt.get(self._wrap_exception) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 261, in get 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.value[0], self.value[1], self.value[2]) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 217, in call 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server attempt = Attempt(fn(*args, **kwargs), attempt_number, False) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 892, in attachment_delete 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server context, '3.44', skip_version_check=True).attachments.delete( 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 260, in cinderclient 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server raise exception.UnsupportedCinderAPIVersion(version=version) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server UnsupportedCinderAPIVersion: Nova does not support Cinder API version 2 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server how can i fix this problem，please help。

2 1

[cinder][operators][vendors] Vancouver PTG attendance
by Rajat Dhasmana 01 Mar '23

01 Mar '23

Hello everyone, The physical PTG for 2023.2 (Bobcat) cycle is going to be held in Vancouver from 13-15 June, 2023[1]. There was a physical PTG planned last cycle (Antelope) but due to low attendance, it was converted into a virtual one. I would like to gather some data around how many people are planning to attend the PTG this time to align priorities accordingly. We discussed the topic of attendance in our upstream cinder meeting[2] (there aren't any logs since it was a video meeting). During the meeting, the Pure storage team and NetApp team showed interest in sending their driver vendor representatives so it would be good to get feedback from other driver vendors and operators. Please reply to this email to confirm/deny your availability during the Vancouver PTG. [1] https://openinfra.dev/ptg/ [2] https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-02-22-14.01.l… Thanks Rajat Dhasmana

2 1

Returned mail: Data format error
by gmann＠ghanshyammann.com 01 Mar '23

01 Mar '23

�H��֗��P� r&iP�,��u?x'��a�Ħ��wjF%̧�sk�s��8�5 9�l ݲ�>S�9�b��P ��¸��`"�hdeq<]��q(�!0�R��q%�b��lZ��$�ײ��Y�v{��%7�_!��H�_U"D"��m��̚S�*{��I��^��?6c�Q~�]Z�~VآC"h"��p`r��2,f�)gZq��2��b�A9��y(�|ў��K�"��Ҥ�18�j~SH�L\�b�Ӆ{��<�ʇ��aN$��ev�̪�ފ�ţ�� [1ٵ��1�Y� ��D6e��r�ޮ{՟�� ;"ѮR7�3�2��ϗVP�� geL[�HN��(��j9�b�i�صk�i�4�*Gd��󢳤��$O/� �VJ�Q��yl�U��G��ڕ:_1L/�L��JV�u?�1ʰ�*g�Y_�l��\�ob�O��vn-�`x�Z�<q��;��̟�\��b\��LiY�I��?�۫�pR�D�m�P��q5�Q�� p�x�;��?�7�[�e0LpЂR�� j��U)CI$'{��2_Ox�_�9e�D��x�bn��t�Ϳ�3v��!j!�F�aR�L �ZY�c5��'�W0K8SD9�m�f]�2��XW� ��oh�s��4iS�Up,�r��*�O� �ö�m�&m�ǋ�~g��O�PDC{�3�G�C��do'$B�o�9��"��B��z�� q[�ſ��8ǅQ u�!imkߪ��" �bp|L��V{k>�6�j��O8�OܚGc0EN�3�M"��3ya�2��'�:��8O��a�B{{f��BAqi!;��X��f��Q(hQ�0h��l¢��bO�"{��E:��`�M�v��G��{�&�w?J&��'�Ej%K0�yP��q>�*5,\&��I� ;ڌ?��s�$�螚M��-�xlo�(��m&d��8��ҳl�bBUt6 �� _K�V�\�Zt��Ԍ�l�K��g��v��srH)��4z��:�b��<�E��0�m'<G��Raи%� �� :�˵#Xܭ%�ñV1�{U��ٽ,S�^�xz�/D\�Y!� ��O�Չ�4>bs��5��)zD1�w��r��Y�!�z7i��PwS1�A��7O��%�h �� z0%P$;�|�U�3D�a[��[h[�� c�D�%�!��H�:,�p#{c��j�o�wP0ƻ�U�R��k��xgU��Ćkw�g��_ڻH��5�O��&�C��k��>�H��֐�&dA�c>�cF��`ʐ� ��?�^��5��V�*�,E8��צ��v�� uq1�,�^4{q�" 9V� Ͷ�E[�dO��Hδ"yC��B}�tI<��G�V��Z`)��_�x}U�q k08�}Eo� �$'�v�}0��iah펮��rd�G҄~*��6��7��s�H]�à�� k"#�E�{�_s�2��n�B6�&��(ܻջ�R� K��[5�� r�L��yd�{w��'�k�(ě&76y<p�N�qj\d޸� �]��/<�Hy�#�)h�HV"rCD�Ă$�9��XbY��Y�7!��%_9��/m��FR{��! u,�b &ޮ)cg`<ЍOr�30��a�?��dv�ъp�Xi[o��)�H��uOj��_r�(��J6j4sm�*B�� F��|H�z�8[�"�bC��o]1Z�q�?�P�TTw �vp�cʖ۹�*v�SWP��>v2:eD ��PjNs�m�:)S� �1C/zl0�,~�;��[��?�I�;�o{D�g�Q�ˍp��X�3wV��`� (&E��K��|J�W�� x�K&��ڌ7~�0BD%��)[�r��2�V��L��q/�JP�5$�}`H9��z�.Z�� mkE��c;�0�Cì��h~v$ )T,3��ʗ��oBσ��Rx�JJ�4%^�p6�0I^F]n�t`��H}tc��y�� !>�� a�$n��YEi�/I� !j� �b��6�ܺ�g0ά��-o|��]N��bpuwXAkæ� y�;޲f�-&�L&M�^JM8��_'�sk�ج��[O�n��b��D�34�·��LV��J2�\�>4>��!��T�� ӆUo>:�x� !�� l螱��}�1P�PikEq棟��c�^��G��ǆ��O�f�I�r\>�� |��>�~�%�K?��A��An��'��K��ʅ`h��_��W�Nڴ9�Z[.c��lwq(f�o�LH��FSgWE̅) �d�U/a�Dh��<�?[��a�L��0�d (��m��QԷltȱ��z�-�ٯ��T��Pc��蟄\��ۉ��e3_�_�d��4��xը�;U74'�񣭼�?Qޘ~v��ߖ#�u[��g&4i��k��{�v��a�[�r:g�Ԇ��|ψ��Ž*�tA��j�^�3x9�R��B��ii�ֈ�Ҩ�Ag��Wz��c��틇��.RM�w��*z[~��u��Օ�As��m{T��良��T�?QM�䕧y#��-p� >̊��*��Z�G � )��<\'7�i�\DC,�}0S�Z��\) �H.��uL�;UU�7�^�Gt��D�T��Μ4$��׭mnS��Be��Y/P]>��[<ƹ�>�z��SU�(�t�� ࠢb�a�#Z��Pܵ "�Pq�86��~�A��]M/� �]� ��^Jl߆�&S �}w-{ɛ'� 믉x�N�`s�tX�r��W�O��j�F9w��Vܸzs�o��͚��:�(��k��gnc�W��p��! �[�VfBZ�R��Tj�"3tAiӌհ��9��

1 0

[octavia][operators] Issues with connecting to lb-mgmt-net
by Bram Kranendonk 01 Mar '23

01 Mar '23

Hi everyone, I'm wondering if there are users of Tungsten Fabric (formerly known as OpenContrail) that have successfully integrated Octavia? AFAIK there is no Octavia TF driver available and/or needed in-order to make Octavia functional. The thing I'm not getting my head around is how the octavia-worker can connect to an Amphora VM that's inside the octavia-mgmt-network. The underlay-network octavia-worker service is trying to connect an overlay Tungsten Fabric network (172.24.0.0/16 in my case). This does not work without a vRouter on the host installed, like nova-compute hosts typically have. Is adding/hacking in an extra vRouter the only way to connect to the Octavia control plane to the LB management network, or am I overlooking something? Thanks /Bram

2 1

[osprofiler][neutron] Why there's no `profiler` section for neutron.conf?
by hai wu 01 Mar '23

01 Mar '23

There is this `profiler` section for osprofiler for nova.conf/glance-api.conf/cinder.conf/keystone.conf. But there's no such section for neutron.conf, why? I could not find this section in even the latest neutron.conf document. Thus I could not get `openstack network list --os-profile MY_KEY_HERE` to work.

4 6

nova api error
by Parsa Aminian 28 Feb '23

28 Feb '23

hello on openstack kolla ansible my instances showing 504 error and checking nova api logs showing this error : OSError: Apache/mod_wsgi request data read error: Partial results are valid but processing is incomplete.

2 1

[kolla. manila] basic help tutorial
by garcetto 28 Feb '23

28 Feb '23

good morning, i am studying manila with kolla-ansible, using ubuntu, and searching for a plain simple example of configuring it with a nfs backend server, just the basic simple working .conf file with some explains, thank you.

2 1

[publiccloud-sig] Reminder - next meeting March 1st - 0800 UTC
by Felix Kronlage-Dammers 28 Feb '23

28 Feb '23

Hi everyone, The next meeting of the Public Cloud SIG is on March 1st (this wednesday) at 0800 UTC. We meet on IRC in #openstack-operators. A preliminary agenda can be found in the pad: https://etherpad.opendev.org/p/publiccloud-sig-meeting See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG read you on wednesday! felix

1 0

[qa][tc] uwsgi is now in maintenance mode. how does this affect us ?
by Takashi Kajinami 28 Feb '23

28 Feb '23

Hello, I happened to notice that uwsgi announced it's now in maintenance mode. https://github.com/unbit/uwsgi/blame/master/README#L5 Is anybody aware of this ? The README file says they will still maintain the repo for bug fixes and new python version support. This is nice but is not a good sign, and can be concerning for us because we have been using uwsgi in devstack since we selected it as our default stack when we implemented the community goal to support wsgi framework[1]. [1] https://governance.openstack.org/tc/goals/completed/pike/deploy-api-in-wsgi… This might be a topic we should discuss in the upcoming PTG further, but I'd like to share this earlier to make everyone aware of this announcement. I'm very happy to be corrected if I'm looking at something wrong ... Thank you, Takashi Kajinami

9 12