April 2019 - openstack-discuss - lists.openstack.org

Nodepool not able to register node to jenkins.
by Aman Kumar Sinha26 08 Apr '19

08 Apr '19

2 1

[networking-ovn] nested virtualization in ovn ci
by Guo, Ruijing 08 Apr '19

08 Apr '19

Hi, Does networking-ovn CI support nested virtualization? does it use OpenStack Infra? Do you have plan to add OVSDPDK in networking-ovn CI? I saw cpu flag vmx in 1) and didn't see vmx in 2). Why that? 1) http://logs.openstack.org/10/637510/2/check/networking-ovn-tempest-dsvm-ovs… 2) http://logs.openstack.org/65/643565/1/check/networking-ovn-tempest-dsvm-ovs… Thanks, -Ruijing

1 0

[release][kayobe] Release job failures
by Mark Goddard 08 Apr '19

08 Apr '19

Hi, We've had a few release job failures in Kayobe [1]. I created some new tags on stable branches last week, and the release jobs failed with the following: Unable to freeze job graph: Unable to modify final job <Job trigger-readthedocs-webhook branches: None source: opendev/base-jobs/zuul.yaml at master#112> attribute variables={'rtd_webhook_id': '74820', 'rtd_project_name': 'kayobe-release-notes'} with variant <Job trigger-readthedocs-webhook branches: None source: openstack/kayobe/zuul.d/project.yaml at master#2> It's not clear from the email which branch, tag or job this affects. The message above references our readthedocs job which aims to publish release notes, although I can't see the expected releases on tarballs.o.o or PyPI. The RTD release note Zuul job is defined here [2], is it causing a problem? We also use the docs-on-readthedocs template to update our docs. [1] http://lists.openstack.org/pipermail/release-job-failures/2019-April/001117… [2] https://github.com/openstack/kayobe/blob/44430a42421a7c59807a58cbbd67f90a15… Thanks, Mark

2 1

[PTL][release][stable] Pike transitioning to Extended Maintenance phase
by Sean McGinnis 08 Apr '19

08 Apr '19

Hey everyone, Thought I should get this out there to make sure folks are aware. We are actually overdue for Pike to have entered extended maintenance. According to the stable policy, that should happen 18 months after the release [0]. That means we should have made the switch in February, if my math is right. We will need to work through the details to actually put that in effect, but for now I wanted to remind teams that we do not do releases after a stable branch enters this phase. So this is a call for action for any teams that have been backporting fixes that time is short to get a final release out while you can. The release dates for each cycle can be found on the releases site [1]. Thanks! Sean [0] https://docs.openstack.org/project-team-guide/stable-branches.html#maintena… [1] https://releases.openstack.org/

4 7

[Magnum] x509: certificate signed by unknown authority
by Anirudh Gupta 08 Apr '19

08 Apr '19

Hi Team, I have deployed K8s cluster using Magnum Openstack Rocky Release. I have one master node and one slave node in my cluster. But when I try to create a POD on master node using the command *kubectl run nginx --image=nginx* My Container remains in ContainerCreating State. When I debugged into the issue, I found the below error *Warning FailedCreatePodSandBox 59s (x24 over 32m) kubelet, kubernetes-cluster-w6csm5uqyspz-minion-0 Failed create pod sandbox: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause:3.0 <http://gcr.io/google_containers/pause:3.0>": x509: certificate signed by unknown authority* However, in */etc/sysconfig/docker* file, I have disabled the gcr.io repository. OPTIONS='--insecure-registry="gcr.io,googleapis.com" --selinux-enabled ' The docker is successfully pulling the *gcr.io/google_containers/pause:3.0 <http://gcr.io/google_containers/pause:3.0> image,* BUT kubernetes is neither able to use local repository nor able to pull the image. Can someone please help me in resolving the *x509: certificate signed by unknown authority issue?* Regards Anirudh Gupta

1 1

fqdn magnum instances
by Ionut Biru 08 Apr '19

08 Apr '19

Hello, I was wondering if there is a way to set up the domain for template to use in order to have a FQDN hostname for all the vms that are part from the cluster Currently the name is: k8s-cluster-coreos-somerandomtext-minion-0 but i want something like k8s-cluster-coreos-somerandomtext-minion-0.mydomain.net I'm trying to resolve this: helm install stable/wordpress Error: forwarding ports: error upgrading connection: error dialing backend: dial tcp: lookup k8s-cluster-coreos-7pctbrnuykc6-minion-0 on 8.8.8.8:53: no such host

4 7

[trove] trove guest agent image building improvement
by Lingxian Kong 08 Apr '19

08 Apr '19

Hi team, I've proposed a patch https://review.openstack.org/#/c/650608/ for the image building improvement. The most significant change is introducing one more param `dev_mode` to the command so that users could choose to build image for non-dev environment. BTW, I've also submitted some other patches for CI improvement which need your review as well. Any suggestion or feedback are welcomed. --- Lingxian Kong Catalyst Cloud

1 0

[neutron] Bug deputy report (week starting on 2019-04-01)
by Bernard Cafarelli 08 Apr '19

08 Apr '19

Hello Neutrinos, I was the bug deputy for April Fools' week. All Critical/High bugs already have fixes merged, except https://review.openstack.org/#/c/650599/ (close to merge) Both Medium bugs would benefit from a second look (details below) A few invalid bugs, filled on LP while they should now be created on StoryBoard. This includes neutron-lbaas ( https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas) and os-ken (https://storyboard.openstack.org/#!/project/openstack/os-ken not sure why it does not appear when searching for os-ken) Proposed RFE: * [RFE] L3 - netfilter Contrack Helper Support - https://bugs.launchpad.net/neutron/+bug/1823633 Suggested in L3 meeting Critical: * ml2 create_port_bulk produces incompatible port context to drivers - https://bugs.launchpad.net/networking-midonet/+bug/1822999 Midonet tests failing after bulk ports optimization merged Fixed with: https://review.openstack.org/#/c/649615 <https://review.openstack.org/#/c/649615/3> and https://review.openstack.org/649623 as added check * test_update_provider_net_unsupported failure - https://bugs.launchpad.net/networking-midonet/+bug/1823294 Another Midonet gate failure caused by https://review.openstack.org/#/c/648522/ Proposed fix: https://review.openstack.org/#/c/650599/ * neutron-fullstack fails on stable/rocky at ovs compilation - https://bugs.launchpad.net/neutron/+bug/1823155 Latest Xenial kernels break OVS compilation for fullstack tests Fixed with newer OVS snapshot: https://review.openstack.org/#/c/650022/ High: * Neutron-keepalived-state-change fails to check initial router state - https://bugs.launchpad.net/neutron/+bug/1823038 New functional failure as a result of bug #1818614 Fixed with: https://review.openstack.org/#/c/649991/ backports in progress * Specify FROM clause to join from in test_floatingip_via_router_interface_returns_201 - https://bugs.launchpad.net/neutron/+bug/1823059 Blocking upper-constraints update Fix merged: https://review.openstack.org/#/c/649681 Medium: * Bulk IPv6 subnet create error - https://bugs.launchpad.net/neutron/+bug/1822582 "RuntimeError: Method <function update_port at 0x7fde0e9280c8> cannot be called within a transaction." Has a reproducer * neutron-keepalived-state-change doesnt reap zombies if rootwrap-daemon is used - https://bugs.launchpad.net/neutron/+bug/1822591 Reproduced on current, and need additional eyes/opinion here: were there sudo zombies appearing before? (when the child process gets killed) Low: * [VPNaaS]: Skip check process status for HA backup routers - https://bugs.launchpad.net/neutron/+bug/1822921 In progress * create of segment range for vlan network type fails with error 500 - https://bugs.launchpad.net/neutron/+bug/1823297 Proposed fix: https://review.openstack.org/650245 * ha router sometime goes in standby mode in all controllers - https://bugs.launchpad.net/neutron/+bug/1823314 Rare race condition when creating HA routers, in progress Invalid: * "delete l7 rule" Parameter Passing Error - https://bugs.launchpad.net/bugs/1822960 * "lbaas delete l7 rule & policy" could leave dirty data - https://bugs.launchpad.net/bugs/1822968 2 neutron-lbaas bugs filled, I pointed author to storyboard * Error in os_kenbgp import in tests - https://bugs.launchpad.net/neutron/+bug/1822649 To move to storyboard Probably caused in mass rename, one filename does not match the module name in imports Proposed fix: https://review.openstack.org/#/c/649140/ Incomplete: * legacy router namespaces absence or error run exec - https://bugs.launchpad.net/neutron/+bug/1823023 ip netns commands failing on an OSA deployment, out of scope for neutron for now Regards, -- Bernard Cafarelli

1 0

Call For Proposals: KVM Forum 2019 (30-Oct to 01-Nov – Lyon, France)
by Kashyap Chamarthy 08 Apr '19

08 Apr '19

================================================================ KVM Forum 2019: Call For Participation October 30-November 1, 2019 - Lyon Convention Center - Lyon, France (All submissions must be received before June 15, 2019 at 23:59 PST) ================================================================= KVM Forum is an annual event that presents a rare opportunity for developers and users to meet, discuss the state of Linux virtualization technology, and plan for the challenges ahead. We invite you to lead part of the discussion by submitting a speaking proposal for KVM Forum 2019. At this highly technical conference, developers driving innovation in the KVM virtualization stack (Linux, KVM, QEMU, libvirt) can meet users who depend on KVM as part of their offerings, or to power their data centers and clouds. KVM Forum will include sessions on the state of the KVM virtualization stack, planning for the future, and many opportunities for attendees to collaborate. As we celebrate ten years of KVM development in the Linux kernel, KVM continues to be a critical part of the FOSS cloud infrastructure. This year, KVM Forum is joining Open Source Summit in Lyon, France. Selected talks from KVM Forum will be presented on Wednesday October 30 to the full audience of the Open Source Summit. Also, attendees of KVM Forum will have access to all of the talks from Open Source Summit on Wednesday. https://events.linuxfoundation.org/events/kvm-forum-2019/program/call-for-p… Suggested topics: * Scaling, latency optimizations, performance tuning, real-time guests * Hardening and security * New features * Testing KVM and the Linux kernel: * Nested virtualization * Resource management (CPU, I/O, memory) and scheduling * VFIO: IOMMU, SR-IOV, virtual GPU, etc. * Networking: Open vSwitch, XDP, etc. * virtio and vhost * Architecture ports and new processor features QEMU: * Management interfaces: QOM and QMP * New devices, new boards, new architectures * Graphics, desktop virtualization and virtual GPU * New storage features * High availability, live migration and fault tolerance * Emulation and TCG * Firmware: ACPI, UEFI, coreboot, U-Boot, etc. Management and infrastructure * Managing KVM: Libvirt, OpenStack, oVirt, etc. * Storage: Ceph, Gluster, SPDK, etc. * Network Function Virtualization: DPDK, OPNFV, OVN, etc. * Provisioning ======================== SUBMITTING YOUR PROPOSAL ======================== Abstracts due: June 15, 2019 Please submit a short abstract (~150 words) describing your presentation proposal. Slots vary in length up to 45 minutes. Submit your proposal here: https://events.linuxfoundation.org/events/kvm-forum-2019/program/call-for-p… Please only use the categories "presentation" and "panel discussion" You will receive a notification whether or not your presentation proposal was accepted by August 12, 2019. Speakers will receive a complimentary pass for the event. In case your submission has multiple presenters, only the primary speaker for a proposal will receive a complimentary event pass. For panel discussions, all panelists will receive a complimentary event pass. TECHNICAL TALKS A good technical talk should not just report on what has happened over the last year; it should present a concrete problem and how it impacts the user and/or developer community. Whenever applicable, focus on work that needs to be done, difficulties that haven't yet been solved, and on decisions that other developers should be aware of. Summarizing recent developments is okay but it should not be more than a small portion of the overall talk. END-USER TALKS One of the big challenges as developers is to know what, where and how people actually use our software. We will reserve a few slots for end users talking about their deployment challenges and achievements. If you are using KVM in production you are encouraged submit a speaking proposal. Simply mark it as an end-user talk. As an end user, this is a unique opportunity to get your input to developers. HANDS-ON / BOF SESSIONS We will reserve some time for people to get together and discuss strategic decisions as well as other topics that are best solved within smaller groups. These sessions will be announced during the event. If you are interested in organizing such a session, please add it to the list at http://www.linux-kvm.org/page/KVM_Forum_2019_BOF Let people you think who might be interested know about your BOF, and encourage them to add their names to the wiki page as well. Please add your ideas to the list before KVM Forum starts. PANEL DISCUSSIONS If you are proposing a panel discussion, please make sure that you list all of your potential panelists in your the abstract. We will request full biographies if a panel is accepted. ============== HOTEL / TRAVEL ============== This year's event will take place at the Lyon Conference Center. For information on hotels close to the conference, please visit https://events.linuxfoundation.org/events/kvm-forum-2019/attend/venue-trave…. Information on conference hotel blocks will be available later in Spring 2019. ================= DATES TO REMEMBER ================= Submission deadline: Saturday, June 15 at 23:59 PST Notification: Monday, August 12 Schedule announced: Friday, August 16 Slides due date: Wednesday, October 23 Event dates: Wednesday, October 30 - Friday, November 1 Thank you for your interest in KVM. We're looking forward to your submissions and seeing you at the KVM Forum 2019 in October! For questions and comments, please contact the KVM Forum 2019 Program Committee at: kvm-forum-2019-pc(a)redhat.com -- /kashyap

1 0

[TC] PTG Lunch Talks
by Kendall Nelson 08 Apr '19

08 Apr '19

Hello! I think you all have already started to discuss this, but if you haven't, here's the lowdown: You can have 15 min or 30 min on Thursday (we will also have lightning talks from the othe projects attending the PTG after you complete your time) and basically however much time you want on Saturday during lunch (keeping in mind that a lot of people are planning to leave Friday night). Friday is going to be the feedback session so there's not time available lunch that day. tldr; Do you want 15min or 30 min on Thursday? :) -Kendall Nelson

5 6