- openstack-discuss - lists.openstack.org

Goodbye for now
by Albert Braden 09 Mar '20

09 Mar '20

My contract at Synopsys ends today, so I will have to continue my efforts to sign up as an Openstack developer at my next role. Thanks to everyone for all of the help and advice. Best wishes! Albert

2 1

[Horizon] Unable to access the dashboard page
by Rahul Sharma 09 Mar '20

09 Mar '20

Hi, I am trying to get OpenStack (Train) up and running on CentOS 7 by following the "OpenStack Installation Guide" provided on OpenStack's website and have completed installation of below components - Keystone - Glance - Placement - Nova - Networking After installing each component, I have also verified its operation and it seems to be working successfully. However, there is a problem I am facing after installing "Horizon" for dashboard services. In order to verify its operation, one is supposed to browse to the URL "http://controller/horizon/" where "controller" could be the hostname or IP address of the Node which is running the controller Browsing to the above URL throws an error "The requested URL /horizon was not found on this server." In the apache access logs, I see below error: " 103.44.50.92 - - [07/Mar/2020:13:14:52 +0000] "GET /horizon/ HTTP/1.1" 404 206 "-" "Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36" 103.44.50.92 - - [07/Mar/2020:13:14:52 +0000] "GET /favicon.ico HTTP/1.1" 404 209 "http://3.21.90.63/horizon/" "Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36" " If I browse to the URL "http://controller/", the default "Testing123" page of apache gets loaded. Please assist. Thanks, Rahul

4 7

[CINDER] Snapshots export
by Alfredo De Luca 09 Mar '20

09 Mar '20

Hi all. We have our env with Openstack (Train) and cinder with CEPH (nautilus) backend. We are creating automatic volumes snapshots and now we'd like to export them as a backup/restore plan. After exporting the snapshots we will use Acronis as backup tool. I couldn't find the right steps/commands to exports the snapshots. Any info? Cheers -- *Alfredo*

5 6

[all][tc] What happened in OpenStack Governance recently
by Jean-Philippe Evrard 09 Mar '20

09 Mar '20

Hello, It's been a while there was no update on "what happened in governance recently?" (February). So here is a summary for you! We had two meetings since the last community update, February [1] and March [2]. We have established our first (business-focused) upstream investment opportunities for 2020, which currently consists of: - Goal champions - Consistent and secure policy defaults - QA developers You can see the latest version in [3]. The timing for the next PTL and TC elections is now determined [4]. We've introduced the ideas framework, allowing you to propose, follow, and track large scale changes of OpenStack, with their conversations history [5]. We are starting to split OpenDev out of OpenStack-infra. Our next release names are Victoria and Wallaby. In terms of community goals [6], we've changed the U goal for documentation, so please have a look if you haven't already [7][8], and/or talk to the goal champion Kendall (diablo_rojo). The 'Switch legacy Zuul jobs to native' goal has been selected for Victoria. Please talk to its champion, Luigi Toscano (tosky)! On the projects' side, we've clarified the guidelines to drop official project teams [9]. We want to retire teams more actively if necessary, to allow us to increase our focus. Some projects have changed: - networking-ovn won't get releases anymore, as it's merged back into neutron in U [10] - neutron-lbaas was retired in Ussuri [11] Have a good day to you all! Regards, Jean-Philippe Evrard (evrardjp) [1]: http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-02-06-14.00.html [2]: http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-03-05-14.00.html [3]: https://governance.openstack.org/tc/reference/upstream-investment-opportuni… [4]: https://review.opendev.org/#/c/708470/3/configuration.yaml [5]: http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012847… [6]: https://governance.openstack.org/tc/goals/selected/index.html [7]: https://review.opendev.org/#/c/708672/ [8]: https://review.opendev.org/#/c/709617/ [9]: https://review.opendev.org/#/c/707421/ [10]: https://review.opendev.org/#/c/705781/ [11]: https://review.opendev.org/#/c/705780/

1 0

[tc] April meeting
by Jean-Philippe Evrard 09 Mar '20

09 Mar '20

Hello everyone, It would be nice if you could update the agenda on the wiki [1] for the April meeting, happening on April, 2nd. Thank you in advance, Jean-Philippe Evrard (evrardjp). [1]: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[tc] March meeting
by Jean-Philippe Evrard 09 Mar '20

09 Mar '20

Hello, Here are the minutes for the march meeting [1]. There are a few action points for you, please have a look! Regards, Jean-Philippe Evrard (evrardjp) [1]: http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-03-05-14.00.html

1 0

[queens] [neutron]security_groups_log]
by Ignazio Cassano 08 Mar '20

08 Mar '20

Hello, I have queens installation based on centos7. Before implementing security groups logs, I had the following configuration in /etc/neutron/plugins/ml2/openvswitch_agent.ini: firewall_driver = iptables_hybrid Enabling security groups log I had to change it in : firewall_driver = openvswitch It seems to work end security logs are logged . After restarting kvm nodes and controllers, virtual machines do not live migrate. The firewall driver change could be the cause of my problem ? firewall_driver = openvswitch is mandatory for security groups log ? Please, any help ? I cannot reproduce the problem rebooting all my nodes. I rebooted them because I hat to transfer from a rack to another. Ignazio

2 5

[queens] [neutron]security_groups_log] issues
by Ignazio Cassano 07 Mar '20

07 Mar '20

Hello, I have queens installation based on centos7. Before implementing security groups logs, I had the following configuration in /etc/neutron/plugins/ml2/openvswitch_agent.ini: firewall_driver = iptables_hybrid Enabling security groups log I had to change it in : firewall_driver = openvswitch It seems to work end security logs are logged . After restarting kvm nodes and controllers, virtual machines do not live migrate. I rolled back my configuration without security groups logs feature and now all works fine. The firewall driver change could be the cause of my problem ? firewall_driver = openvswitch is mandatory for security groups log ? Please, any help ? I cannot reproduce the problem rebooting all my nodes. I rebooted them because I hat to transfer from a rack to another. Ignazio

1 0

[nova][qa] When creating a instance using a flavor with "hw:cpu_policy=dedicated" "hw:cpu_realtime=yes" and "hw:cpu_realtime_mask=^0-1" failed.
by Juntingqiu Qiujunting (邱军婷) 06 Mar '20

06 Mar '20

When I create a instance using a flavor with "hw:cpu_policy=dedicated" "hw:cpu_realtime=yes" and "hw:cpu_realtime_mask=^0-1". The error is "libvirtError:Cannot set scheduler parameters for pid 3666:operation not permitted". https://bugs.launchpad.net/starlingx/+bug/1866311 The instance xml as following: <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='11'/> <vcpupin vcpu='2' cpuset='0'/> <vcpupin vcpu='3' cpuset='8'/> <emulatorpin cpuset='3,11'/> <vcpusched vcpus='2' scheduler='fifo' priority='1'/> <vcpusched vcpus='3' scheduler='fifo' priority='1'/> </cputune> The error log as following: ERROR nova.compute.manager [instance: 74dcc0a1-9ed4-4d13-bef7-ac9623bca2d0] File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1099, in createWithFlags ERROR nova.compute.manager [instance: 74dcc0a1-9ed4-4d13-bef7-ac9623bca2d0] if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self) ERROR nova.compute.manager [instance: 74dcc0a1-9ed4-4d13-bef7-ac9623bca2d0] libvirtError: Cannot set scheduler parameters for pid 6504: Operation not permitted ERROR nova.compute.manager [instance: 74dcc0a1-9ed4-4d13-bef7-ac9623bca2d0]

2 1

Re: [sdk][congress][octavia][designate][magnum][senlin][swift] Adding project-specific cores to SDK
by Eric Fried 06 Mar '20

06 Mar '20

Any chance of reusing the “PTL ack” bot that has recently appeared in the releases repo? But as a “SME ack” that would recognize anyone from $project’s core team? (How does the releases bot know which project the patch is for? Might have to be a bit fuzzy on that logic for SDK/OSC.) Then the team could adopt a policy of single core approval if the patch has this SME +1, and no real danger of “abuse”. Eric Fried

4 4

[sdk][congress][octavia][designate][magnum][senlin][swift] Adding project-specific cores to SDK
by Monty Taylor 06 Mar '20

06 Mar '20

Heya, I’d like to try something. I’d like to try adding some project-specific people to the core team so that they can more directly help maintain the support for their service in SDK. In some of these cases the person I’m suggestion has next to no review experience in SDK. I think let’s be fine with that for now - we’re still a 2x +2 in general thing - but I know currently when reviewing neutron or ironic changes I always want to see a +2 from slaweq or dtantsur … so in the spirit of trying new things and trying to move the project forward in a healthy and welcoming way - how about we give this a try? The idea here is that we’re trusting people to use their good judgement and to only use their new +2 powers for good in their project. Over time, if they feel like they’ve gotten a handle on things more widely, there’s nothing stopping them from reviewing other patches - but I think that most of us aren’t looking for additional review work anyway. Specifically this would be: Shogo Saito - congress Adam Harwell - octavia Graham Hayes - designate Bharat Kumar - magnum Erik Olof Gunnar Andersson - senlin Tim Burke - swift I think we should also add a file in the repo that lists “subject matter experts” for each service we’ve got support for, where we have them. My list of current cores who I’d ping for specific service suitability are: Sean McGinnis - cinder Slawek Kaplonski - neutron Dmitry Tantsur - ironic Eric Fried - nova (at least until tomorrow my friend) How does that sound to folks? Monty

4 4

oslo.cache 2.1.0 breaks oslo_cache.memcache_pool
by Radosław Piliszek 06 Mar '20

06 Mar '20

Please be informed that oslo.cache 2.1.0 breaks oslo_cache.memcache_pool Kolla-Ansible gate is already RED and a quick codesearch revealed other deployment methods might be in trouble soon as well. This does not affect devstack/tempest as they use dogpile.cache.memcached instead. The error is TypeError: __init__() got an unexpected keyword argument 'dead_retry' For details see: https://bugs.launchpad.net/oslo.cache/+bug/1866008 -yoctozepto

3 7

Re: [CINDER] Distributed storage alternatives
by Burak Hoban 06 Mar '20

06 Mar '20

Hi guys, We use Dell EMC VxFlex OS, which in its current version allows for free use and commercial (in version 3.5 a licence is needed, but its perpetual). It's similar to Ceph but more geared towards scale and performance etc (it use to be called ScaleIO). Other than that, I know of a couple sites using SAN storage, but a lot of people just seem to use Ceph. Cheers, Burak ------------------------------ Message: 2 Date: Thu, 13 Feb 2020 18:20:29 +0100 From: Ignazio Cassano <ignaziocassano(a)gmail.com> To: Alfredo De Luca <alfredo.deluca(a)gmail.com> Cc: openstack-discuss <openstack-discuss(a)lists.openstack.org> Subject: Re: [CINDER] Distributed storage alternatives Message-ID: <CAB7j8cXLQWh5fx-E9AveUEa6OncDwCL6BOGc-Pm2TX4FKwnUKg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello Alfredo, I think best opensource solution is ceph. As far as commercial solutions are concerned we are working with network appliance (netapp) and emc unity. Regards Ignazio Il Gio 13 Feb 2020, 13:48 Alfredo De Luca <alfredo.deluca(a)gmail.com> ha scritto: > Hi all. > we 'd like to explore storage back end alternatives to CEPH for > Openstack > > I am aware of GlusterFS but what would you recommend for distributed > storage like Ceph and specifically for block device provisioning? > Of course must be: > > 1. *Reliable* > 2. *Fast* > 3. *Capable of good performance over WAN given a good network back > end* > > Both open source and commercial technologies and ideas are welcome. > > Cheers > > -- > *Alfredo* > > _____________________________________________________________________ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses. _____________________________________________________________________

3 3

CPU Topology confusion
by Satish Patel 05 Mar '20

05 Mar '20

Folks, We are running openstack with KVM and i have noticed kvm presenting wrong CPU Tolopoly to VM and because of that we are seeing bad performance to our application. This is openstack compute: # lstopo-no-graphics --no-io Machine (64GB total) NUMANode L#0 (P#0 32GB) + Package L#0 + L3 L#0 (25MB) L2 L#0 (256KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + Core L#0 PU L#0 (P#0) PU L#1 (P#20) L2 L#1 (256KB) + L1d L#1 (32KB) + L1i L#1 (32KB) + Core L#1 PU L#2 (P#1) PU L#3 (P#21) This is VM running on above compute # lstopo-no-graphics --no-io Machine (59GB total) NUMANode L#0 (P#0 29GB) + Package L#0 + L3 L#0 (16MB) L2 L#0 (4096KB) + Core L#0 L1d L#0 (32KB) + L1i L#0 (32KB) + PU L#0 (P#0) L1d L#1 (32KB) + L1i L#1 (32KB) + PU L#1 (P#1) L2 L#1 (4096KB) + Core L#1 L1d L#2 (32KB) + L1i L#2 (32KB) + PU L#2 (P#2) L1d L#3 (32KB) + L1i L#3 (32KB) + PU L#3 (P#3) if you noticed P#0 and P#1 has own (32KB) cache per thread that is wrong presentation if you compare with physical CPU. This is a screenshot of AWS vs Openstack CPU Topology and looking at openstack its presentation is little odd, is that normal? https://imgur.com/a/2sPwJVC I am running CentOS7.6 with kvm 2.12 version.

3 8

OSC future (formerly [glance] Different checksum between CLI and curl)
by Albert Braden 05 Mar '20

05 Mar '20

As an openstack operator I was pretty ecstatic to hear that the assortment of clients would be replaced by a single client. I would be disappointed to find that a component would not integrate and would continue to use a separate client. This would be a step backward IMO. The discussion about microversions goes over my head, but I would hope to see the developers get together and solve the issue and continue working toward integration. -----Original Message----- From: Radosław Piliszek <radoslaw.piliszek(a)gmail.com> Sent: Monday, March 2, 2020 9:07 AM To: openstack-discuss <openstack-discuss(a)lists.openstack.org> Subject: Re: [glance] Different checksum between CLI and curl Folks, sorry to interrupt but I think we have diverged a bit too much from the subject. Only last Gaetan message is on topic here. Please switch to new subject to discuss OSC future. -yoctozepto pon., 2 mar 2020 o 18:03 Tim Bell <tim.bell(a)cern.ch> napisał(a): > > > > On 2 Mar 2020, at 16:49, Dmitry Tantsur <dtantsur(a)redhat.com> wrote: > > Hi, > > On Mon, Mar 2, 2020 at 4:29 PM Luigi Toscano <ltoscano(a)redhat.com> wrote: >> >> On Monday, 2 March 2020 10:54:03 CET Mark Goddard wrote: >> > On Mon, 2 Mar 2020 at 06:28, Abhishek Kekane <akekane(a)redhat.com> wrote: >> > > Hi Gaëtan, >> > > >> > > Glance team doesn't recommend to use OSC anymore. >> > > I will recommend you to check the same behaviour using >> > > python-glanceclient. >> > >> > That's not cool - everyone has switched to OSC. It's also the first >> > time I've heard of it. >> > >> > > From the end user perspective, we’ve had positive feedback on the convergence to OSC from our cloud consumers. > > There has been great progress with Manila to get shares included (https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23… ) and it would be a pity if we’re asking our end users to understand all of the different project names and inconsistent options/arguments/syntax. > > We had hoped for a project goal to get everyone aligned on OSC but there was not consensus on this, I’d still encourage it to simplify the experience for OpenStack cloud consumers. > > Tim > >

16 25

[osc][sdk] Merging OpenStack SDK and OpenStack Client teams
by Monty Taylor 05 Mar '20

05 Mar '20

Hey everybody, I’d like to propose merging the SDK and OSC teams. We already share an IRC channel, and already share a purpose in life. In OSC we have a current goal of swapping out client implementation for SDK, and we’re Already ensuring that SDK does what it needs to do to facilitate that goal. We also already share PTG space, and have requested a shared set of time at the upcoming Denver PTG. So really the separation is historical not practical, and these days having additional layers of governance is not super useful. I propose that we do a simple merge of the teams. This means the current SDK cores will become cores on OSC, and as most of the OSC cores are already SDK cores, it means the SDK team gains amotoki - which is always a positive. Dean hasn’t had time to spend on OSC quite a bit, sadly, and while we remain hopeful that this will change, we’re slowly coming to terms with the possibility that it might not. With that in mind, I’ll serve as the PTL for the new combined team until the next election. Monty

9 9

[trove][charm] RabbitMQ Connection Error
by tolga＠etom.cloud 05 Mar '20

05 Mar '20

2 1

[ansible-sig][kolla][openstack-ansible][osc][sdk][tripleo] OpenStack modules broken in Ansible 2.8.9
by Mark Goddard 05 Mar '20

05 Mar '20

Hi, The 2.8.9 release of Ansible has a regression [1] which breaks the OpenStack modules. I've proposed a simple fix, hopefully it will be included in a 2.8.10 release soon but in the meantime you may need to blacklist 2.8.9. [1] https://github.com/ansible/ansible/issues/68042 [2] https://github.com/ansible/ansible/pull/68043 Cheers, Mark

3 2

[sdk] Additions and subtractions from core team
by Monty Taylor 05 Mar '20

05 Mar '20

Heya, With the previous email about merging OSC and SDK teams, I’d also like to propose the following changes to the SDK core team (keeping in mind that likely means the core team of both OSC and SDK real soon now) Adds: Akihiro Motoki - The only OSC core not in sdk-core. amotoki should really be a core in all projects anyway Sean McGinnis - Sean has been reviewing things as a stable branch maint in both SDK and OSC, and as such has shown a good tendency to help things along when needed and to not approve things when he doesn’t know what’s up. Subtractions: All of these people are awesome, but they’re all long gone: Brian Curtin Clint Byrum Everett Toews Jamie Lennox Jesse Noller Ricardo Carillo Cruz Richard Theis Rosario Di Somma Sam Yaple Terry Howe Monty

5 5

[training-labs] Current training lab for Rocky not working on Windows
by Mike Manning 05 Mar '20

05 Mar '20

Hello, I've attempted to install the training-labs for the Rocky release onto my Windows 10 laptop on VirtualBox 6.0, but it is not working properly. The windows batch files are not functioning properly, and at least one reason is that the shell scripts that the batch files are copying are using "ifup" and "ifdown" which are not supported in Ubuntu 18.04. This one issue seems to imply that the scripts and batch files may need some review. Also, after install the ifupdown package on the system, the batch files and shell scripts still get hung up often on the existence of a file named "done" that never gets created. Can someone help me with this installation of the training-labs software in preparation for the COA exam? Mike Manning mike243512(a)gmail.com

1 0

[neutron][drivers team] Meeting 06.03.2020 cancelled
by Slawek Kaplonski 05 Mar '20

05 Mar '20

Hi Neutrinos, Due to lack of agenda lets cancel tomorrow’s drivers meeting. Lets meet as usually next week on Friday 13.03.2020. But, as You have now one hour of “free” time tomorrow (:D) I would like to ask You to take a look and help triaging one new RFE: https://bugs.launchpad.net/neutron/+bug/1865889 I’m not the best expert in routed networks, so I would really like if Miguel, Brian and others could take a look at this :) Thx in advance. — Slawek Kaplonski Senior software engineer Red Hat

1 0

[MicroStack] Beta updates and strict (devmode) confinement on edge
by Pete Vander Giessen 05 Mar '20

05 Mar '20

Hi all, It has been a little while since I’ve posted any MicroStack news. MicroStack is a base set of OpenStack services, bundled into a snap. It’s intended for OpenStack workload development (as opposed to development of OpenStack itself), and also contains some experimental features geared toward edge clouds. We’ve just released a new MicroStack beta, with preview support for clustering (e.g., running a control plane node along with several compute nodes). You can install it with: sudo snap install --classic --beta microstack There are some known issues with refreshes from the current beta version of the snap to the new version. You may need to reinstall MicroStack if you’re running the current beta. To address some issues running MicroStack on non LTS Ubuntu distros, as well as lay the groundwork for a smoother refresh/upgrade process going forward, we’re working on making MicroStack into a strictly confined snap! If you’re feeling brave, you can try the (almost) strictly confined snap in developer mode with the following invocation: sudo snap install --devmode --edge microstack Work to put together a completely confined version of the snap, with no need for the devmode flag, is ongoing. You can find more information about MicroStack at https://microstack.run, and talk to the devs either on this mailing list, or on IRC: freenode #openstack-snaps .

1 0

NovaVMware - vCenter / DevStack - ERROR
by Kevin Puusild 04 Mar '20

04 Mar '20

Hello i have written here before but i didn't get any help so i try again. Current Setup: Ubuntu 18.04 Server with 1 vCenter + 1 ESXi i am trying to setup DevStack with vCenter as a hypervisor (not ESXI) following this wiki article: https://wiki.openstack.org/wiki/NovaVMware/DeveloperGuide to prepare to setup my devstack and following this wiki articel https://docs.openstack.org/devstack/latest/ too (compaining these two articles) *localrc* file is containing below information: ENABLED_SERVICES=g-api,g-reg,key,n-api,n-crt,n-cpu,n-net,n-cond,n-sch,n-novnc,n-cauth,rabbit,mysql,horizon VIRT_DRIVER=vsphere VMWAREAPI_IP=#MY_VCENTER_IP VMWAREAPI_USER=#MY_VCENTER_ADMINISTRATOR_USER VMWAREAPI_PASSWORD=#MY_VCENTER_ADMINISTRATOR_PASSWORD VMWAREAPI_CLUSTER=#MY_VCENTER_CLUSTER_NAME DATABASE_PASSWORD=nova RABBIT_PASSWORD=nova SERVICE_TOKEN=nova SERVICE_PASSWORD=nova ADMIN_PASSWORD=nova HOST_IP=#MY_DEVSTACK_MACHINE_IP after running *stack.sh* script i get following error: ++functions:wait_for_compute:448 hostname +functions:wait_for_compute:448 compute_hostname=devstack +functions:wait_for_compute:450 timeout 60 bash -x ++functions:wait_for_compute:450 hostname +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +:: ID= +:: [[ '' == '' ]] +:: sleep 1 +:: [[ vsphere = \f\a\k\e ]] ++:: openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host devstack --service nova-compute -c ID -f value +functions:wait_for_compute:450 rval=124 +functions:wait_for_compute:462 time_stop wait_for_service +functions-common:time_stop:2330 local name +functions-common:time_stop:2331 local end_time +functions-common:time_stop:2332 local elapsed_time +functions-common:time_stop:2333 local total +functions-common:time_stop:2334 local start_time +functions-common:time_stop:2336 name=wait_for_service +functions-common:time_stop:2337 start_time=1582790249013 +functions-common:time_stop:2339 [[ -z 1582790249013 ]] ++functions-common:time_stop:2342 date +%s%3N +functions-common:time_stop:2342 end_time=1582790309198 +functions-common:time_stop:2343 elapsed_time=60185 +functions-common:time_stop:2344 total=7679 +functions-common:time_stop:2346 _TIME_START[$name]= +functions-common:time_stop:2347 _TIME_TOTAL[$name]=67864 +functions:wait_for_compute:464 [[ 124 != 0 ]] +functions:wait_for_compute:465 echo 'Didn'\''t find service registered by hostname after 60 seconds' Didn't find service registered by hostname after 60 seconds +functions:wait_for_compute:466 openstack --os-cloud devstack-admin --os-region RegionOne compute service list +functions:wait_for_compute:468 return 124 +lib/nova:is_nova_ready:1 exit_trap +./stack.sh:exit_trap:533 local r=124 ++./stack.sh:exit_trap:534 jobs -p +./stack.sh:exit_trap:534 jobs= +./stack.sh:exit_trap:537 [[ -n '' ]] +./stack.sh:exit_trap:543 '[' -f /tmp/tmp.8iR1neh89b ']' +./stack.sh:exit_trap:544 rm /tmp/tmp.8iR1neh89b +./stack.sh:exit_trap:548 kill_spinner +./stack.sh:kill_spinner:443 '[' '!' -z '' ']' +./stack.sh:exit_trap:550 [[ 124 -ne 0 ]] +./stack.sh:exit_trap:551 echo 'Error on exit' Error on exit +./stack.sh:exit_trap:553 type -p generate-subunit +./stack.sh:exit_trap:554 generate-subunit 1582789174 1136 fail +./stack.sh:exit_trap:556 [[ -z /opt/stack/logs ]] +./stack.sh:exit_trap:559 /usr/bin/python3.6 /devstack/devstack/tools/worlddump.py -d /opt/stack/logs World dumping... see /opt/stack/logs/worlddump-2020-02-27-075831.txt for details +./stack.sh:exit_trap:568 exit 124 -- Kevin Puusild

1 0

[stable][heat] Nominating Rabi Mishra for heat-stable-maint
by Zane Bitter 04 Mar '20

04 Mar '20

Rabi has been a core reviewer on Heat for more than 4 years, and is a former PTL. In that time he's done hundreds of backports: https://review.opendev.org/#/q/owner:ramishra%2540redhat.com+branch:%22%255… (Only two of which we ended up deciding not to merge, the last of which was in 2016.) As well as a good number of reviews: https://review.opendev.org/#/q/reviewedby:ramishra%2540redhat.com+branch:%2… Rabi also maintains a downstream distribution of Heat, so he is fully aware of the pain that backporting inappropriate changes can cause. He is well aware of the stable branch guidelines and is, if anything, more conservative than I am in applying them. I'm 100% confident he will not be approving any feature backports. I'll be spending some extended time away from a keyboard in the near future, so it's important that we increase the bus factor (from 1) of heat-stable-maint team members. thanks, Zane.

3 2

[oslo][infra] OpenDev git repo for oslo.policy missing commit
by Ben Nemec 04 Mar '20

04 Mar '20

Found a weird thing today. The OpenDev oslo.policy repo[0] is missing [1]. Even stranger, I see it on the Github mirror[2]. Any idea what happened here? -Ben 0: https://opendev.org/openstack/oslo.policy/commits/branch/master 1: https://review.opendev.org/#/c/708212/ 2: https://github.com/openstack/oslo.policy/commits/master

2 2