July 2021 - openstack-discuss - lists.openstack.org

[nova] Milestone 2 - spec freeze
by Balazs Gibizer 16 Jul '21

16 Jul '21

Hi, Yesterday we hit Xena Milestone 2. This also means nova is now in a state of spec freeze. The Yoga spec directory already exists so specs that are not merged to Xena can be propose to Yoga already. I've updated the bp states in launchpad[1]. Please check your bps and let me know if I missed something or misunderstood the status of the implementation work. We have 20 open bps at the moment which is a lot. Please note that Milestone 3 and therefore feature freeze is 3rd of September, which is 7 weeks from now. I encourage all of you to prioritize reviewing implementation of the bps that are already in NeedsCodeReview state. Cheers, gibi [1] https://launchpad.net/nova/+milestone/xena-3

1 0

Setting bandwidth limit
by Felipe Mogollon 16 Jul '21

16 Jul '21

Hi, I am running openstack victoria installed using packstack. Everything things to be fine except bandwidth limit. I have tried to limit internal traffic between two instances and between instances and "Internet" but I always get maximum data transfer speed. I have set up following rules openstack network qos rule create --type bandwidth-limit --max-kbps 3 --max-burst-kbits 2 --ingress bw-choke openstack network qos rule create --type bandwidth-limit --max-kbps 3 --max-burst-kbits 2 --egress bw-choke and applied bw-choke policy to the internal network where my instances are deployed: openstack network set --qos-policy bw-choke newdeploylab_private_network and to ports where machines connect to subnet: openstack port set --qos-policy bw-choke 503a07b8-2da0-4abe-8251-ede648ba42b4 openstack port set --qos-policy bw-choke 776d5fb3-639c-47cc-9b0f-6ec855397df7 but nothing happens. Each time I try to download something from internet or copy data from an instance to another I always get maximum data transfer speed. I have followed instructions from https://docs.openstack.org/neutron/victoria/admin/config-qos.html Any ideas? -- <https://www.vicomtech.org> Juan Felipe Mogollón Rodríguez Researcher | Investigador fmogollon(a)vicomtech.org +[34] 943 30 92 30 Digital Media <https://www.linkedin.com/company/vicomtech> <https://www.youtube.com/user/VICOMTech> <https://twitter.com/@Vicomtech> member of: <https://graphicsvision.ai/> La información que contiene este mensaje y sus adjuntos son confidenciales y están dirigidos exclusivamente a sus destinatarios. Si recibe este mensaje por error, se ruega nos lo comunique y proceda a su borrado. The information contained in this electronic message is intended only for the personal and confidential use of the recipients designated in the original message. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.

1 0

[all] Proposed Yoga cycle schedule
by Herve Beraud 16 Jul '21

16 Jul '21

Hey everyone, The Xena cycle is going by fast, and it's already time to start planning some of the early things for the Yoga release. One of the first steps for that is actually deciding on the release schedule. Typically we have done this based on when the next Summit event was planned to take place. Due to several reasons, we don't have a date yet for the first 2022 event. The current thinking is it will likely take place in May (nothing is set, just an educated guess, so please don't use that for any other planning). So for the sake of figuring out the release schedule, we are proposing one schedule targeting a release date at the end of March. Hopefully this will then align well with event plans. Here is the proposed schedule: https://review.opendev.org/c/openstack/releases/+/800663 Please feel free to comment on the patch if you see any major issues that we may have not considered. Thanks for your reading -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

[neutron][vpnaas] Ok with V. not working with W.
by Franck VEDEL 16 Jul '21

16 Jul '21

Hello, i have been trying to fix a problem for over 2 weeks with no success so am looking for some help as my openstack is due to work in september (for my students). I need the vpnaas service. I'm doing a lab with centos / kolla-ansible / victoria ... vpnaas works, exactly what I need. I replace V with Wallaby. Exactly the same server, the same Centos, I just change V to W in the configuation file. Everything works except Vpnaas. I have a new server, and for some reason I can't have Victoria (issue with horizon that I don't understand). I'm trying Wallaby. Everything works perfectly except Vpnaas. Why ? It's incomprehensible. A bug ? The error message (neutron-l3-agent.log): Command: ['mount', '--bind', '/var/lib/neutron/ipsec/8b987595-47be-45cc-95f5-3b70d24f4976/var/run', '/var/run'] Exit code: 0 Stdout: Stderr: 2021-07-16 12:03:57.089 281941 INFO neutron_vpnaas.services.vpn.common.netns_wrapper [-] /var/lib/neutron/ipsec/8b987595-47be-45cc-95f5-3b70d24f4976/var/run has been bind-mounted in /var/run Command: ['ipsec', 'whack', '--status'] Exit code: 33 Stdout: Stderr: whack: Pluto is not running (no "/run/pluto/pluto.ctl ») Can this be a bug? I do exactly the same things, the same configurations? How to find the problem? Does anyone have a working Oopenstack Wallaby with Centos and Vpnaas? Meci in advance for your help. Franck http://www.rtgrenoble.fr <http://www.rtgrenoble.fr/>

1 0

[kolla] Ceph client version in Kolla 12.0.0 Wallaby and ubuntu containers
by J-P Methot 16 Jul '21

16 Jul '21

Hi, We've been using Kolla to provision a production cluster and we've noticed that the ceph-client version provided in the Kolla images is severely outdated as it doesn't support the fix to CVE-2021-20288 that was added in Pacific 16.2.1 (installed version in image is 16.2.0). As a result, the installed ceph-client can't connect to ceph clusters where the patch is active. Is there any Kolla image where more recent versions of ceph-client is installed? How would I be able to get them? -- Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc.

4 4

[nova] [magnum] Flavor names vs IDs
by Krzysztof Klimonda 16 Jul '21

16 Jul '21

Hi, Flavors have both names ands IDs and both can be set during creation - what is the background for having both being separate from each other? I'm asking this because magnum uses flavor id for it's "instance-type" node annotation (which is understandable) and by default flavor ID is an autogenerated UUID. Would there be any downside to always matching flavor id and name when creating flavors? Best Regards, Krzysztof -- Krzysztof Klimonda kklimonda(a)syntaxhighlighted.com

1 0

[kolla] multiple ceph backends
by J-P Methot 15 Jul '21

15 Jul '21

Hi, I'm progressing in figuring out Kolla and I've hit another issue. On our regular setups, we happen to be using multiple Ceph backends in cinder. Each of those backend uses a differently named ceph config file (like ceph.conf and ceph-rep.conf). While adding a custom configuration to cinder.conf is pretty easy, what's the best way to ensure that my second ceph config file ends up in my containers at the correct path? I've considered using ansible to add the file after kolla has deployed but I doubt this would be permanent. -- Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc.

2 1

[TripleO] next irc meeting Tuesday 20 July @ 1400 UTC in OFTC #tripleo
by Marios Andreou 15 Jul '21

15 Jul '21

Reminder the next TripleO irc meeting is this coming Tuesday 20 July 1400 UTC in OFTC irc channel #tripleo. agenda: https://wiki.openstack.org/wiki/Meetings/TripleO one-off items: https://etherpad.opendev.org/p/tripleo-meeting-items (feel free to add any tripleo status/ongoing work etc to the etherpad). Our last meeting was on Jul 6 - you can find logs @ http://eavesdrop.openstack.org/meetings/tripleo/2021/tripleo.2021-07-06-14.… Hope you can make it on Tuesday, regards, marios

1 0

[horizon] [plugins] [heat-dashboard] [murano-dashboard] Drop nodejs10 Support
by vishal manchanda 15 Jul '21

15 Jul '21

Hello Everyone, As you may have noticed I have pushed a series of patches[1] in the last few months to drop nodejs10 support from our gate job because nodejs10 is already EOL. All horizon plugins and horizon moved to nodejs14 which is the current LTS version also runtime for the Xena release[2]. Next Step is to drop nodejs10 support, only two horizon plugins left that still run nodejs10 job i.e openstack/heat-dashboard and opensatck/murano-dashboard. So I would request to heat and murano core team to approve open patches for the same [3], [4] and then we can finally drop it from the horizon. Thanks to all for taking this as the priority and quick approvals on the patches. In case of any issue, please feel free to reach out to Horizon channel #openstack-horizon. Regards, Vishal Manchanda(irc: vishalmanchanda) [1] https://review.opendev.org/q/topic:%22drop-nodejs10%22+(status:open%20OR%20… [2] https://governance.openstack.org/tc/reference/runtimes/xena.html#node-js-ru… [3] https://review.opendev.org/c/openstack/heat-dashboard/+/792201 [4] https://review.opendev.org/c/openstack/murano-dashboard/+/792207

1 0

Re: Cinder error while creating Volumes in Openstack
by Adivya Singh 15 Jul '21

15 Jul '21

Hello Team, I am getting the above error, while attaching volumes, My volume service list are up and running. also my rabbitmq services are fine, any other suggestion we can check, we use qnap as storage Regards Adivya Singh On Wed, Jul 14, 2021 at 7:30 PM Adivya Singh <adivya1.singh(a)gmail.com> wrote: > Hi Eugen, > > Please find the error logs which i am getting, particular during attaching > a instance to a Instance > > Jul 14 13:54:17 c1w-cinder-volumes-container-aa023a91 > cinder-volume[38100]: 2021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server [req-7ec417bc-0692-4766-8513-86a979c23e07 > 4441034aeea2551710631bc8fe381b1094c260e64501c736bfa51987aaefd7cc > 4e1398294816433bab5f3cebb2210788 - f7834cb0083b4f8f81184b6595b46b34 > f7834cb0083b4f8f81184b6595b46b34] Exception during message handling: > ParseError: no element found: line 20, column 0#0122021-07-14 13:54:17.246 > 38100 ERROR oslo_messaging.rpc.server Traceback (most recent call > last):#0122021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", > line 166, in _process_incoming#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server res = > self.dispatcher.dispatch(message)#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", > line 265, in dispatch#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, > ctxt, args)#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", > line 194, in _do_dispatch#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server result = func(ctxt, **new_args)#0122021-07-14 > 13:54:17.246 38100 ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/manager.py", > line 4420, in attachment_update#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server connector)#0122021-07-14 13:54:17.246 38100 > ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/manager.py", > line 4348, in _connection_create#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server volume, connector)#0122021-07-14 13:54:17.246 > 38100 ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", > line 274, in inner#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server return f(*args, **kwargs)#0122021-07-14 > 13:54:17.246 38100 ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/drivers/qnap.py", > line 853, in create_export#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server self._get_portal_info(volume, connector, > lun_slot_id, lun_owner))#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/drivers/qnap.py", > line 706, in _get_portal_info#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server ret = > self.api_executor.get_iscsi_portal_info()#0122021-07-14 13:54:17.246 38100 > ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/drivers/qnap.py", > line 1109, in inner_connection_checker#0122021-07-14 13:54:17.246 38100 > ERROR oslo_messaging.rpc.server return func(self, *args, > **kwargs)#0122021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/drivers/qnap.py", > line 1520, in get_iscsi_portal_info#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server root = > ET.fromstring(res_details['data'])#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/defusedxml/common.py", > line 118, in fromstring#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server return parser.close()#0122021-07-14 > 13:54:17.246 38100 ERROR oslo_messaging.rpc.server File > "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1671, in > close#0122021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > self._raiseerror(v)#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1523, in > _raiseerror#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server raise err#0122021-07-14 13:54:17.246 38100 > ERROR oslo_messaging.rpc.server ParseError: no element found: line 20, > column 0#0122021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > > Regards > Adivya Singh > 9590986094 > > On Wed, Jul 14, 2021 at 1:29 PM Eugen Block <eblock(a)nde.ag> wrote: > >> Hi, >> >> those are only INFO logs, they don't show anything related to errors >> you're experiencing. >> >> >> Zitat von Adivya Singh <adivya1.singh(a)gmail.com>: >> >> > Hi Team, >> > >> > any input on this, Logs are attached >> > >> > Regards >> > Adivya Singh >> > >> > >> > ---------- Forwarded message --------- >> > From: Adivya Singh <adivya1.singh(a)gmail.com> >> > Date: Mon, Jul 12, 2021 at 9:58 PM >> > Subject: Re: Cinder error while creating Volumes in Openstack >> > To: Brian Rosmaita <rosmaita.fossdev(a)gmail.com> >> > >> > >> > hi Brian, >> > >> > Thanks for your response, I am attaching the logs hereby. >> > >> > Earlier we were able to create the cinder volumes and delete , but >> unable >> > to attach, but now even create and delete not working >> > >> > Regards >> > Adivya Singh >> > >> > On Mon, Jul 12, 2021 at 9:31 PM Brian Rosmaita < >> rosmaita.fossdev(a)gmail.com> >> > wrote: >> > >> >> On 7/12/21 11:20 AM, Adivya Singh wrote: >> >> > Hello Team, >> >> > >> >> > i am seeing the below error, while creating volumes in cinder log, >> Any >> >> > solution or fix for these error, as of now i am not able to create >> >> > volumes, neither i am unable to delete, it just sits in hung state >> >> > >> >> > DISTRIB_RELEASE="18.1.9" >> >> > DISTRIB_CODENAME="Rocky" >> >> > DISTRIB_DESCRIPTION="OpenStack-Ansible" >> >> >> >> Hello Adivya, >> >> >> >> I think you forgot to include the error? If your log extracts are >> long, >> >> you can post them in http://paste.openstack.org/ and send the links to >> >> this mailing list. (Don't forget to scrub any sensitive info first.) >> >> >> >> > >> >> > Regards >> >> > Adivya Singh >> >> > >> >> >> >> >> >> >> >> >> >> >>

4 3