December 2018 - openstack-discuss

[openlab] Maintenance Notification
by Melvin Hillsman 15 Dec '18

15 Dec '18

Hi everyone, Maintenance will be happening 12/19/2018 and 12/20/2018 so if you experience any issues we do apologize. Not everyone will be affected but it is just good to know these things even if you are not. Additionally we will not be able to onboard any new requests/projects/individuals during this time more than likely but please do fill out any requests and we will proceed as normal. If there is an issue we will work through as much as we can to fulfill requests. Kind regards, OpenLab

1 0

bug openstack queens magnum
by Ignazio Cassano 15 Dec '18

15 Dec '18

Hi All, I am facing the same issue wrote at this link: https://ask.openstack.org/en/question/116465/magnum-kubernetes-cluster-stuc… It happens for swarm and kubernets but works in swarm-mode. Please, help me Regards Ignazio

1 0

Re: Nova live migration fails - InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have compatibility.
by Torin Woltjer 15 Dec '18

15 Dec '18

Looks like putting the same option on the other compute nodes did the trick. Originally I did that and it made no difference, but that must've been me not rebooting the test instances that were on that node during the change. Doing a cold migrate correctly updates the XML, so I'll have to cold migrate all of the production instances before I can live migrate them.

1 0

[neutron][stadium] Switch from ryu to os-ken
by Hongbin Lu 15 Dec '18

15 Dec '18

Hi all, Due to the advice that Ryu library won't be maintained at the end of 2018, the neutron team decided to fork the Ryu library and maintain the fork, which is called os-ken [1], from now on. Right now, both neutron [2] and neutron-dynamic-routing [3] is switching over to os-ken. If other projects want to do the same, please feel free to handout to the openstack-neutron channel for helps or information. You can also find more in here: https://blueprints.launchpad.net/neutron/+spec/ryu-framework-maintenace-tra… . [1] https://github.com/openstack/os-ken [2] https://review.openstack.org/#/c/607008/ [3] https://review.openstack.org/#/c/608357/ Best regards, Hongbin

2 1

Open Infrastructure Summit Denver Contributor Discount Information
by Kendall Waters 15 Dec '18

15 Dec '18

Hi everyone, There have been a lot of questions about discounts for the upcoming Open Infrastructure Summit so I have outlined the contributor discounts that we will be giving out below. Contributor Discount (formally known as ATC or AUC discount) 50% off any 1 ticket type until online sales close (please note ticket prices are tiered so the earlier you use your discount code, the cheaper the ticket will be) - To qualify for this discount, you will need to either have contributed at least one commit which merged to an official governed OSF project or pilot project in the last 6 months as of January 1, 2019 or qualify as an AUC: http://superuser.openstack.org/articles/auc-community/ <http://superuser.openstack.org/articles/auc-community/> - Discount codes will be sent by the end of January Denver 2018 PTG Attendees 82% off the early bird price of the Summit + PTG combo ticket until early bird ends - To qualify for this discount, you must have attended the Denver PTG in September 2018 - Discount codes will be sent by the end of January Please let me know if you have any questions. Cheers, Kendall Kendall Waters OpenStack Marketing & Events kendall(a)openstack.org

2 2

[TripleO] OVB 2.0 Update
by Ben Nemec 15 Dec '18

15 Dec '18

Just wanted to give everyone a heads up that there's a 2.0 development branch for OVB available. I wrote up a blog post about it http://blog.nemebean.com/content/openstack-virtual-baremetal-20-update that covers the details of what changed and where you can find it. We definitely need to make sure TripleO CI will be happy with the changes, but if anyone else is using it please also give the new branch a try and let me know how it works. -Ben

1 0

[glance] functional-py35 job fails due to subunit.praser error
by Abhishek Kekane 15 Dec '18

15 Dec '18

Hi All, >From 7th December 2018, all of sudden functional-py35 check job is failing on current master. Earlier this job was failing intermittently (2-3 times from 100). I have tried to dig into the issue and find out that it is failing obly for ubuntu and working fine with Fedora, centos etc. Below are some of the findings: 1. Even if I add failure tests [1] in black-list file every time other tests reported as failure. 2. When I compared failed tests results [1] with passed tests results [2] I have found that passing tests shows 'Pass 741 Skip 7' whereas failing tests shows 'Pass 627 Failure 9 Skip 5' (it does not execute all the tests in case of failure) 3. I have compared version of subunit, oslo.service, oslo.log, tox with failed [3] and passed [4] logs and they are same. 4. I came across a bug in cinder [5] which talks about excessive logs might cause this error and I have tried to ignore the deprecation warning in tox.ini by adding 'PYTHONWARNINGS=ignore::DeprecationWarning' but it still shows DeprecationWarning in the logs. 5. I have tried executing tests by setting '--concurrency' to 1 but still the error persists. 6. Whenver subunit.parser error occurs the tests remains 'inprogress' state and sometimes time-outs. I have no clues so far to tackle this issue, kindly provide your inputs for the same. [1] http://logs.openstack.org/89/617889/4/check/openstack-tox-functional-py35/4… [2] http://logs.openstack.org/89/617889/4/check/openstack-tox-functional-py35/3… [3] http://logs.openstack.org/89/617889/4/check/openstack-tox-functional-py35/4… [4] http://logs.openstack.org/89/617889/4/check/openstack-tox-functional-py35/3… [5] https://bugs.launchpad.net/cinder/+bug/1728640 Thanks & Best Regards, Abhishek Kekane

6 6

[goals][upgrade-checkers] Week R-17 Update
by Matt Riedemann 15 Dec '18

15 Dec '18

A few updates this week. * Some more projects have merged the base framework patch (tricircle, vitrage and zaqar). Open changes are here [1]. * Neutron has a change up to add support for loading upgrade checkers via extension point for stadium projects [2]. * There are two projects for which it may or may not make sense to add the upgrade check CLI: 1. mistral [3] - there seems to be concern about how useful the upgrade checker tool could be for mistral. I can't say I know enough about mistral or how it works, but if it is more like horizon and is stateless then maybe it's not a good fit, but I assume mistral has state (it tracks workflows right? So if it gets a start event, presumably it's tracking that to wait for an end event). When I looked over the mistral release notes I had a hard time finding anything worth adding automated checks during an upgrade. However, there is a deprecation note from queens which says, "The YAQL/jinja2 expression function json_pp has been deprecated and will be removed in the S cycle. json_dump should be used instead." I would think that when removing that function, if it's possible to determine it is being used somehow (can that be determined from the database?), then an upgrade check would be useful for that. 2. swift [4] - John has concerns that adding this to swift will expand the scope of the project to provide management functionality which the project has avoided thus far. Again, when I was looking over swift release notes for this goal I never found anything that looked like an obvious upgrade impact so if it's not useful and would set a bad precedent for the project, then I'd be OK with omitting this goal for swift. [1] https://review.openstack.org/#/q/topic:upgrade-checkers+status:open [2] https://review.openstack.org/#/c/615196/ [3] https://review.openstack.org/#/c/611513/ [4] https://review.openstack.org/#/c/611634/ -- Thanks, Matt

1 0

Nova live migration fails - InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have compatibility.
by Torin Woltjer 15 Dec '18

15 Dec '18

Having issues getting live migrations to functions between two compute nodes. One is an Opteron G4 and the other is an Opteron G5. I can migrate from the G4 to the G5 just fine. When I try to migrate an instance from the G5 node to the G4 node I get an error message: InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have compatibility. This is despite having the following setting in my /etc/nova/nova.conf on the G5 machine. [libvirt] cpu_mode = custom cpu_model = Opteron_G4 Is this not the setting I'm looking for? What can I do to make this work? Torin Woltjer Grand Dial Communications - A ZK Tech Inc. Company 616.776.1066 ext. 2006 www.granddial.com

5 4

Re: Nova live migration fails - InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have compatibility.
by Torin Woltjer 15 Dec '18

15 Dec '18

I've restarted the instances that I'm using to test but no luck. I have the setting set on just the highest compute node; I tried setting it on one of my older gen compute nodes as well but because there is production load on it, I am anxious about restarting services; I did restart the nova-compute service after making the change and there was no change in behavior. Should the setting also be set on the controllers? When I look at virsh capabilities there is certainly a difference between the two 7c7 < <model>Opteron_G5</model> --- > <model>Opteron_G4</model> 9c9 < <microcode version='100665426'/> --- > <microcode version='100664894'/> 15d14 < <feature name='bmi1'/> 25c24 < <feature name='tce'/> --- > <feature name='lwp'/> I look at the test instance on the compute node with the G5 opteron and this is in the XML <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Opteron_G4</model> <topology sockets='1' cores='1' threads='1'/> <feature policy='require' name='vme'/> <feature policy='require' name='x2apic'/> <feature policy='require' name='hypervisor'/> <feature policy='disable' name='rdtscp'/> </cpu> This looks like it is correctly taking the CPU model that I have specified in nova.conf, yet it does not want to migrate to the Opteron_G4 node.

3 2