August 2020 - openstack-discuss - lists.openstack.org

Re: [openstack-community] Octavia :; Unable to create load balancer
by Monika Samal 03 Aug '20

03 Aug '20

Hey Fabian, Can you please elaborate more about keystone settings, where in need to make changes etc.. I am new to openstack finding it difficult to resolve kind of atuck ________________________________ From: Fabian Zimmermann <dev.faz(a)gmail.com> Sent: Friday, July 31, 2020 1:22 AM To: Monika Samal <monika.samal(a)outlook.com> Cc: Michael Johnson <johnsomor(a)gmail.com>; Amy Marrich <amy(a)demarco.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 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<mailto:monika.samal@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. [cid:a29109eb-08ac-4f9a-92d4-2befba2cc90e] Regards, Moni ________________________________ From: Michael Johnson <johnsomor(a)gmail.com<mailto:johnsomor@gmail.com>> Sent: Thursday, July 30, 2020 9:41 PM To: Amy Marrich <amy(a)demarco.com<mailto:amy@demarco.com>> Cc: Monika Samal <monika.samal(a)outlook.com<mailto:monika.samal@outlook.com>>; openstack-discuss <openstack-discuss(a)lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>>; community(a)lists.openstack.org<mailto:community@lists.openstack.org> <community(a)lists.openstack.org<mailto:community@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<mailto:amy@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<mailto:monika.samal@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<mailto:Community@lists.openstack.org> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/community

3 8

[nova] Victoria Milestone 2 Spec Freeze
by Balázs Gibizer 03 Aug '20

03 Aug '20

Hi, Last Thursday we reached Milestone 2 which means Nova is in Spec Freeze now. If you have a spec close to be approved and you wish to request a spec freeze exception then please send a mail to the ML about it. We will make the final decision on the weekly meeting on Thursday. Cheers, gibi

1 0

[nova] If any spec freeze exception now?
by Rambo 03 Aug '20

03 Aug '20

Hi,all:         I have a spec which is support volume backed server rebuild[0].This spec was accepted in Stein, but some of the work did not finish, so repropose it for Victoria.And this spec is depend on the cinder reimage api [1], now the reimage api is almost all completed. So I sincerely wish this spec will approved in Victoria. If this spec is approved, I will achieve it at once. Ref: [0]:https://blueprints.launchpad.net/nova/+spec/volume-backed-server-rebuild [1]:https://blueprints.launchpad.net/cinder/+spec/add-volume-re-image-api Best Regards Rambo

3 2

Two subnets under same network context.
by Anil Jangam 03 Aug '20

03 Aug '20

Hi, I have observed that one can create two subnets under the same network scope. See below an example of the use case. [image: Screen Shot 2020-08-01 at 2.22.15 PM.png] Upon checking the data structures, I saw that the segment type (vlan) and segment id (55) is associated with the "network" object and not with the "subnet" (I was under impression that the segment type (vlan) and segment id (55) would be allocated to the "subnet"). When I create the VM instances, they always pick the IP address from the SUBNET1-2 IP range. If the segment (vlan 55) is associated with "network" then what is the reason two "subnets" are allowed under it? Does it mean that VM instances from both these subnets would be configured under the same VLAN? /anil.

4 4

[all][tc][goals] Migrate CI/CD jobs to new Ubuntu LTS Focal: Week R-11 Update
by Ghanshyam Mann 03 Aug '20

03 Aug '20

Hello Everyone, Please find the week R-11 updates on 'Ubuntu Focal migration' community goal. Tracking: https://storyboard.openstack.org/#!/story/2007865 Progress: ======= * We passed the first deadline which I planned initially but looking at the failure happing it will definitely will take more time. My first goal is "zero downtime in gate", so if we finish it little late (with all repos tested) is ok. * ~80 repos gate have been tested/fixed till now. ** https://review.opendev.org/#/q/topic:migrate-to-focal+(status:abandoned+OR+… * 115 repos are under test and failing. Debugging and fixing are in progress (If you would like to help, please check your project repos if I am late to fix them): ** https://review.opendev.org/#/q/topic:migrate-to-focal+status:open * Patches ready to merge: ** https://review.opendev.org/#/q/topic:migrate-to-focal+status:open+label%3AV… Bugs Report: ========== Summary: Total 4 (1 fixed, 3 in-progress). 1. Bug#1882521. (IN-PROGRESS) There is open bug for nova/cinder where three tempest tests are failing for volume detach operation. There is no clear root cause found yet -https://bugs.launchpad.net/cinder/+bug/1882521 We have skipped the tests in tempest base patch to proceed with the other projects testing but this is blocking things for the migration. 2. We encountered the nodeset name conflict with x/tobiko. (FIXED) nodeset conflict is resolved now and devstack provides all focal nodes now. 3. Bug#1886296. (IN-PROGRESS) pyflakes till 2.1.0 is not compatible with python 3.8 which is the default python version on ubuntu focal[1]. With pep8 job running on focal faces the issue and fail. We need to bump the pyflakes to 2.1.1 as min version to run pep8 jobs on py3.8. As of now, many projects are using old hacking version so I am explicitly adding pyflakes>=2.1.1 on the project side[2] but for the long term easy maintenance, I am doing it in 'hacking' requirements.txt[3] nd will release a new hacking version. After that project can move to new hacking and do not need to maintain pyflakes version compatibility. 4. Bug#1886298. (IN-PROGRESS) 'Markupsafe' 1.0 is not compatible with the latest version of setuptools[4], We need to bump the lower-constraint for Markupsafe to 1.1.1 to make it work. There are a few more issues[5] with lower-constraint jobs which I am debugging. What work to be done on the project side: ================================ This goal is more of testing the jobs on focal and fixing bugs if any otherwise migrate jobs by switching the nodeset to focal node sets defined in devstack. 1. Start a patch in your repo by making depends-on on either of below: devstack base patch if you are using only devstack base jobs not tempest: Depends-on: https://review.opendev.org/#/c/731207/ OR tempest base patch if you are using the tempest base job (like devstack-tempest): Depends-on: https://review.opendev.org/#/c/734700/ Both have depends-on on the series where I am moving unit/functional/doc/cover/nodejs tox jobs to focal. So you can test the complete gate jobs(unit/functional/doc/integration) together. This and its base patches - https://review.opendev.org/#/c/738328/ Example: https://review.opendev.org/#/c/738126/ 2. If none of your project jobs override the nodeset then above patch will be testing patch(do not merge) otherwise change the nodeset to focal. Example: https://review.opendev.org/#/c/737370/ 3. If the jobs are defined in branchless repo and override the nodeset then you need to override the branches variant to adjust the nodeset so that those jobs run on Focal on victoria onwards only. If no nodeset is overridden then devstack being branched and stable base job using bionic/xenial will take care of this. Example: https://review.opendev.org/#/c/744056/2 4. If no updates need you can abandon the testing patch (https://review.opendev.org/#/c/744341/). If it need updates then modify the same patch with proper commit msg, once it pass the gate then remove the Depends-On so that you can merge your patch before base jobs are switched to focal. This way we make sure no gate downtime in this migration. Example: https://review.opendev.org/#/c/744056/1..2//COMMIT_MSG Once we finish the testing on projects side and no failure then we will merge the devstack and tempest base patches. Important things to note: =================== * Do not forgot to add the story and task link to your patch so that we can track it smoothly. * Use gerrit topic 'migrate-to-focal' * Do not backport any of the patches. References: ========= Goal doc: https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-j… Storyboard tracking: https://storyboard.openstack.org/#!/story/2007865 [1] https://github.com/PyCQA/pyflakes/issues/367 [2] https://review.opendev.org/#/c/739315/ [3] https://review.opendev.org/#/c/739334/ [4] https://github.com/pallets/markupsafe/issues/116 [5] https://zuul.opendev.org/t/openstack/build/7ecd9cf100194bc99b3b70fa1e6de032 -gmann

1 0

[Openstack-Interop] Friday 31 - Updates and Questions for future of Interop?
by prakash RAMCHANDRAN 01 Aug '20

01 Aug '20

Hi all, We looked at OSF and Open-Infra initiatives and for sustaining and enhancing the Interop activity need your support. The current meeting notes are available on the site and will be meeting alternate Fridays Aug 14, 28,... 10 AM PST / 17 UTC - going forward on meetpad: Lnink: https://meetpad.opendev.org/Interop-WG-weekly-meeting Details in therpadhttps://etherpad.opendev.org/p/interop Do you have suggestions for Branding efforts? Few Question: 1. Interop WG being an OSF or Board Driven, how can Interop work with Projects to ensure Branding Integrated Logo Programs and other Cloud Providers can leverage OpenStack Logo Program? a. We do have role to guide & reviewing refstack reports for Branding. We have decided to decouple Marketplace & Branding programs.Seeking feedback from community on proposed add-on programs for Bare metal(Ironic, MaaS,...) & "Kubernetes-ready OpenStack" b. Refstack hosting / Refstack-client are currently not maintained due to lack of volunteers to support. (seeking volunteers for updates - please reach out to @gmann in TC. c. Await user & operator survey annual reports, but if you have any Branding innovation like to propose or contribute please brainstorm your ideas here and bring it to midweek community meetings next week. ThanksFor Interop WGPrakash

1 0