July 2020 - openstack-discuss - lists.openstack.org

Re: [openstack-community] Octavia :; Unable to create load balancer
by Fabian Zimmermann 31 Jul '20

31 Jul '20

service_auth keystone_authtoken if i read the docs correctly. Maybe you can just paste your config (remove/change passwords) to paste.openstack.org and post the link? Fabian Fabian Zimmermann <dev.faz(a)gmail.com> schrieb am Do., 30. Juli 2020, 21:52: > Hi, > > check your keystone auth settings. > > If i remember correctly there are two different sections to which require > valid keystone settings. > > Fabian > > Monika Samal <monika.samal(a)outlook.com> schrieb am Do., 30. Juli 2020, > 21:43: > >> Hello Michael and Amy, >> >> As suggested I checked and found below error on Octavia-api logs, but not >> sure how to resolve and proceed further with this. >> >> >> Regards, >> Moni >> ------------------------------ >> *From:* Michael Johnson <johnsomor(a)gmail.com> >> *Sent:* Thursday, July 30, 2020 9:41 PM >> *To:* Amy Marrich <amy(a)demarco.com> >> *Cc:* Monika Samal <monika.samal(a)outlook.com>; openstack-discuss < >> openstack-discuss(a)lists.openstack.org>; community(a)lists.openstack.org < >> community(a)lists.openstack.org> >> *Subject:* Re: [openstack-community] Octavia :; Unable to create load >> balancer >> >> Thank you for forwarding this Amy. >> >> Hi Moni, >> >> Can you check the Octavia API process log and the horizon log files to >> see what is causing the "Internal Server Error"? >> >> This sounds like a configuration file problem as Amy mentioned. There >> should be log messages in one of those two locations that will point >> to the problem. >> >> Michael >> >> On Thu, Jul 30, 2020 at 6:10 AM Amy Marrich <amy(a)demarco.com> wrote: >> > >> > Adding the discuss list where you might get more help, but also double >> check your config file for any extra spaces or typos. >> > >> > Thanks, >> > >> > Amy (spotz) >> > >> > On Thu, Jul 30, 2020 at 6:30 AM Monika Samal <monika.samal(a)outlook.com> >> wrote: >> >> >> >> Hello All, >> >> >> >> I have been following >> https://docs.openstack.org/kolla-ansible/latest/reference/networking/octavi… >> to deploy Octavia. I was successful in deployin Octavia but when I go to >> horizon dashboard and create loadbalancer am getting error >> "9876/v2.0/lbaas/loadbalancers, Internal Server Error". I have checked >> worker log at /var/log/kola-ansible/Octavia-worker.log and found oslo >> messaging was refusing connection I fixed it but still getting same error. >> Kindly help >> >> >> >> Regards, >> >> Moni >> >> _______________________________________________ >> >> Community mailing list >> >> Community(a)lists.openstack.org >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/community >> >

2 1

Re: [openstack-community] Octavia :; Unable to create load balancer
by Amy Marrich 31 Jul '20

31 Jul '20

Adding the discuss list where you might get more help, but also double check your config file for any extra spaces or typos. Thanks, Amy (spotz) On Thu, Jul 30, 2020 at 6:30 AM Monika Samal <monika.samal(a)outlook.com> wrote: > Hello All, > > I have been following > https://docs.openstack.org/kolla-ansible/latest/reference/networking/octavi… > to deploy *Octavia. *I was successful in deployin Octavia but when I go > to horizon dashboard and create loadbalancer am getting error *"9876/v2.0/lbaas/loadbalancers, > Internal Server Error". *I have checked worker log* at > /var/log/kola-ansible/Octavia-worker.log *and found oslo messaging was > refusing connection I fixed it but still getting same error. Kindly help > > Regards, > Moni > _______________________________________________ > Community mailing list > Community(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/community >

3 3

[manila] Please delete some branches
by Goutham Pacha Ravi 30 Jul '20

30 Jul '20

Hello, I'd like to request the deletion of some branches in manila that have now transitioned to EOL. These branches can be removed from openstack/manila, openstack/python-manilaclient and openstack/manila-ui: stable/pike stable/ocata I'd also like to request the deletion of "driverfixes" branches from the openstack/manila repository. These branches were created to host vendor fixes to branches that were no longer being tested; however, with our "extended maintenance" stance, we've effectively removed the need for these branches. These branches will no longer be maintained, and so they can be removed as well: driverfixes/mitaka driverfixes/newton driverfixes/ocata Thank you so much for your assistance! Goutham Pacha Ravi

2 3

[tripleo] manual about TripleO core reviewers
by Emilien Macchi 30 Jul '20

30 Jul '20

Hi people, I've started a documentation patch about our core reviewers. Core or not, please be involved in Gerrit directly. https://review.opendev.org/#/c/743999 Hopefully it'll help people to understand about expectations but also give a refresh to current cores. Note: this was inspired by https://wiki.openstack.org/wiki/Ironic/CoreTeam - Thanks a lot to the Ironic team! Thanks, -- Emilien Macchi

1 0

[neutron] Drivers meeting 31.07.2020 - agenda
by Slawek Kaplonski 30 Jul '20

30 Jul '20

Hi, For tomorrow’s drivers meeting we have couple of items to discuss. Full agenda is at https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda but below is short summary also. RFEs: https://bugs.launchpad.net/neutron/+bug/1889431 - [RFE] Add local-ip-prefix to Neutron metering label rules https://bugs.launchpad.net/neutron/+bug/1880532 - [RFE]L3 Router should support ECMP This one was already discussed in the past but now we know it can be done (almost) without changes in existing API https://bugs.launchpad.net/neutron/+bug/1888487 - Change the default value of "propagate_uplink_status" to True We also have 2 items added by Rodolfo to the "On demand” section: • (ralonsoh) https://bugs.launchpad.net/neutron/+bug/1887523: a good proposal to improve the DB performance, that could be done in parallel to https://review.opendev.org/#/c/739139/ • (ralonsoh) https://bugs.launchpad.net/neutron/+bug/1888829: Improve core plugin extension filtering using the mechanism driver information (in other words: if loaded mech drivers do not support any ML2plugin extension, this extension will be gracefully removed). — Slawek Kaplonski Principal software engineer Red Hat

2 1

[ironic] ironic-python-agent failed to lookup node
by Xiaoyu Min 30 Jul '20

30 Jul '20

Hello Experts: I'm new to the openstack and trying to deploy one baremental node but it failed on "wait call-back" stage. I checked IPA log on deploy image and it reports the following error [1]. I aslo manually run the command [2] it gave me the same error "404". I used the devstack to depoly openstack (stable/ussuri). What's the possible problem? Any suggestion is appreciated. -Jack [1]: DEBUG ironic_python_agent.ironic_api_client [-] Looking up node with addresses 'e4:43:4b:93:4c:12,e4:43:4b:93:4c:10,0c:42:a1:56:b8:c5,e4:43:4b:93:4c:13,e4:43:4b:93:4c:11,0c:42:a1:56:b8:c4' and UUID None at http://10.75.205.241/baremetal _do_lookup /usr/lib/python3.6/site-packages/ironic_python_agent/ironic_api_client.py:163[00m ERROR ironic_python_agent.ironic_api_client [-] An error occurred while attempting to discover the available Ironic API versions, falling back to using version 1.31: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) ERROR ironic_python_agent.ironic_api_client Traceback (most recent call last): ERROR ironic_python_agent.ironic_api_client File "/usr/lib/python3.6/site-packages/ironic_python_agent/ironic_api_client.py", line 97, in _get_ironic_api_version ERROR ironic_python_agent.ironic_api_client data = jsonutils.loads(response.content) ERROR ironic_python_agent.ironic_api_client File "/usr/lib/python3.6/site-packages/oslo_serialization/jsonutils.py", line 248, in loads ERROR ironic_python_agent.ironic_api_client return json.loads(encodeutils.safe_decode(s, encoding), **kwargs) ERROR ironic_python_agent.ironic_api_client File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads ERROR ironic_python_agent.ironic_api_client return _default_decoder.decode(s) ERROR ironic_python_agent.ironic_api_client File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode ERROR ironic_python_agent.ironic_api_client obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ERROR ironic_python_agent.ironic_api_client File "/usr/lib64/python3.6/json/decoder.py", line 357, in raw_decode ERROR ironic_python_agent.ironic_api_client raise JSONDecodeError("Expecting value", s, err.value) from None ERROR ironic_python_agent.ironic_api_client json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) ERROR ironic_python_agent.ironic_api_client [00m WARNING ironic_python_agent.ironic_api_client [-] Failed looking up node with addresses 'e4:43:4b:93:4c:12,e4:43:4b:93:4c:10,0c:42:a1:56:b8:c5,e4:43:4b:93:4c:13,e4:43:4b:93:4c:11,0c:42:a1:56:b8:c4' at http://10.75.205.241/baremetal, status code: 404[00m]]] [2]: curl http://10.75.205.241/baremetal [...snip...] <title>404 Not Found</title>

1 0

[cinder] video + IRC meeting survey
by Brian Rosmaita 30 Jul '20

30 Jul '20

Today we had our first Cinder meeting held simultaneously in videoconference and on IRC. I have posted a quick survey to see if there's support for continuing this monthly experiment. (The next video + IRC meeting would be the last week of August.) https://rosmaita.wufoo.com/forms/r1twmaya13asv1c/ Please respond before 12:00 UTC on Tuesday, 4 August. thanks! brian

1 0

[tripleo] stable/train migration from CentOS-7 to CentOS-8
by Wesley Hayutin 29 Jul '20

29 Jul '20

Greetings, I wanted to give everyone a heads up that the migration of upstream stable/train jobs from CentOS-7 to CentOS-8 [1] is close. CentOS-7 stable/train will continue to be tested in our 3rd party periodic pipeline and builds of CentOS-7 stable/train will be qualified here [2] Please let me know if you have any questions. Thanks! [1] https://review.opendev.org/#/c/738375 [2] https://review.rdoproject.org/zuul/builds?pipeline=openstack-periodic-integ…

1 1

Neutron bandwidth metering based on remote address
by Jonas Schäfer 29 Jul '20

29 Jul '20

Dear list, We are trying to implement tenant bandwidth metering at the neutron router level. Since some of the network spaces connected to the external interface of the neutron router are supposed to be unmetered, we need to match on the remote address. Conveniently, there exists a --remote-ip-prefix option on meter label create; however, since [1], its meaning was changed to the exact opposite: Instead of matching on the *remote* prefix (towards the external interface), it matches on the *local* prefix (towards the OS tenant network). In an ideal world, we would want to revert that change and instead introduce a --local-ip-prefix option which covers that use-case. I suppose this is not a thing we *should* do though, given that this change made it into a few releases already. Instead, we’ll have to create a new option (which whatever name) + associated database schema + iptables rule patterns to implement the feature. The questions associated with this are now: - Does this make absolutely no sense to anyone? - What is the process for this? I suppose since this change was made intentionally and passed review, our desired change needs to go through a feature request process (blueprints maybe?). kind regards, Jonas Schäfer [1]: https://opendev.org/openstack/neutron/commit/ 92db1d4a2c49b1f675b6a9552a8cc5a417973b64 -- Jonas Schäfer DevOps Engineer Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 37 jonas.schaefer(a)cloudandheat.com | www.cloudandheat.com New Service: Managed Kubernetes designed for AI & ML https://managed-kubernetes.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann Authorized signatory: Kristina Rübenkamp

2 4

Re: privsep helper command exited non-zero (1) [openstack-dev][kuryr]
by Michał Dulko 29 Jul '20

29 Jul '20

> Hi Dulko > Thanks for your reply. > > My OS is Centos 7.6 + python 3.7 > Kuryr-daemon --version = 2.1.0 > > I run the kuryr-daemon as root. > I run the kuryr not as pods. > I will show you the conf of kuryr-daemon: > > Waiting for your reply. > > Thanks. > ========================================== <snip!> Please don't remove mailing list from the thread. Hm, I googled some older answer that maybe privsep-helper is not installed where kuryr-daemon is executed? In terms of Kuryr stuff that file has almost nothing set, so it isn't really giving much information, so - what's the Neutron plugin being used? Is the [kubernetes]pod_vif_driver just neutron-vif? I think for that to work you need to set [neutron_defaults]ovs_bridge for the daemon and [neutron_defaults]pod_subnet for controller. Can you enable debug for more logs from the error? On Wed, 2020-07-29 at 02:39 +0000, Niu,Lixin wrote: > > 在 2020/7/29 上午1:15，“Michał Dulko”<mdulko(a)redhat.com> 写入: > > On Tue, 2020-07-28 at 12:28 +0000, Niu,Lixin wrote: > > HI List > > When I run the kuryr, and launch the pods from k8s, I get some > > error like the title. > > Could you please help me to solve this problem? Please give > > some tips. Thanks a lot. > > > > 2020-07-28 16:35:22.084 27610 ERROR os_vif [-] Failed to plug vif VIFBridge(active=False,address=fa:16:3e:f2:ff:e6,bridge_name='qbradfc2b63-47',has_traffic_filtering=True,id=adfc2b63-471e-4fc6-b7be-72af56ee1f27,network=Network(652fdbae-281d-4475-b883-dcfecb821cbd),plugin='ovs',port_profile=VIFPortProfileOpenVSwitch,preserve_on_delete=False,vif_name='tapadfc2b63-47'): oslo_privsep.daemon.FailedToDropPrivileges: privsep helper command exited non-zero (1) > > > > Hi, > > This seems pretty vague, but my first bet would be that kuryr-daemon is > not running as root? What's the exact configuration you use - i.e. > Neutron plugin, Kuryr binding plugin (nested vs neutron), are you > running Kuryr services as pods? > > Thanks, > Michał > > >

1 0