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

Help with kernel panic on cirros image boot process.
by Jorge Luiz Correa 04 Apr '19

04 Apr '19

Hi all! I'm having kernel panic randomically with cirros image. Sometimes the instances boots, sometimes not. I'm using Openstack Queens, Ubuntu Server 18.04 and KVM (following the install guide). The nova/instances directory, where are stored ephemeral disks, is over a GlusterFS system. I've noted that other images, like Ubuntu Cloud Image, do not get this error. It's just with cirros and sometimes. I appreciate any help guiding on where I can look for to identify what is causing these errors. I've analyzed libvirt logs and them show just a launched instance, everything ok. The _base/<ID> file used to launch the instances is the same that is used with cirros instances that worked (it's in a GlusterFS). Something got wrong during the instance boot process. Thank you! [ 1.586076] EDD information not available. [ 1.590261] Freeing unused kernel memory: 1480K (ffffffff81f42000 - ffffffff820b4000) [ 1.594823] Write protecting the kernel read-only data: 14336k [ 1.598951] Freeing unused kernel memory: 1860K (ffff88000182f000 - ffff880001a00000) [ 1.625178] Freeing unused kernel memory: 168K (ffff880001dd6000 - ffff880001e00000) info: initramfs: up at 1.07 modprobe: module virtio_pci not found in modules.dep modprobe: module virtio_blk not found in modules.dep modprobe: module virtio_net not found in modules.dep modprobe: module vfat not found in modules.dep modprobe: module nls_cp437 not found in modules.dep info: copying initramfs to /dev/vda1 [ 2.028648] jbd2_journal_bmap: journal block not found at offset 12 on vda1-8 [ 2.034075] Aborting journal on device vda1-8. mount: mounting /dev on ./dev failed: No such file or directory info: initramfs loading root from /dev/vda1 switch_root: can't execute '/sbin/init': No such file or directory [ 2.692399] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 2.692399] [ 2.696061] CPU: 0 PID: 1 Comm: switch_root Not tainted 4.4.0-28-generic #47-Ubuntu [ 2.699012] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.2-1ubuntu1 04/01/2014 [ 2.702373] 0000000000000086 000000004016d54a ffff88003e2fbe10 ffffffff813eb1a3 [ 2.705849] ffffffff81cb10d8 ffff88003e2fbea8 ffff88003e2fbe98 ffffffff8118bf57 [ 2.709353] ffff880000000010 ffff88003e2fbea8 ffff88003e2fbe40 000000004016d54a [ 2.712875] Call Trace: [ 2.714013] [<ffffffff813eb1a3>] dump_stack+0x63/0x90 [ 2.715995] [<ffffffff8118bf57>] panic+0xd3/0x215 [ 2.717840] [<ffffffff81184e1e>] ? perf_event_exit_task+0xbe/0x350 [ 2.720105] [<ffffffff81084541>] do_exit+0xae1/0xaf0 [ 2.722090] [<ffffffff810845d3>] do_group_exit+0x43/0xb0 [ 2.724150] [<ffffffff81084654>] SyS_exit_group+0x14/0x20 [ 2.726207] [<ffffffff818276b2>] entry_SYSCALL_64_fastpath+0x16/0x71 [ 2.729271] Kernel Offset: disabled [ 2.730741] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 2.730741] - JLC

2 1

[Release-job-failures][freezer] Tag of openstack/freezer-api failed
by Sean McGinnis 04 Apr '19

04 Apr '19

The release of freezer-api failed due to the use of oslosphinx. Sphinx 2.0 was released late last week, and with the major version bump, it has now removed some deprecated things that the oslosphinx theme was using. Projects have been migrating to openstackdocstheme for some time now, with the majority using that instead. Since oslosphinx was going away anyway, it is now being retired and compatibility issues will not be fixed. I have proposed a patch to get freezer-api moved over to openstackdocstheme: https://review.openstack.org/650032 This (or something like it) will need to be merged before we can do a successful release of freezer-api since release notes are generated off of the master branch. Sean ----- Forwarded message from zuul(a)openstack.org ----- Date: Thu, 04 Apr 2019 14:14:59 +0000 From: zuul(a)openstack.org To: release-job-failures(a)lists.openstack.org Subject: [Release-job-failures] Tag of openstack/freezer-api failed Reply-To: openstack-discuss(a)lists.openstack.org Build failed. - publish-openstack-releasenotes-python3 http://logs.openstack.org/59/59a8e662bb73926eb35cd49fbc7371c9dc7170bd/tag/p… : FAILURE in 3m 01s

1 1

tacker 1.0.0.0rc2 (stein)
by no-reply＠openstack.org 04 Apr '19

04 Apr '19

Hello everyone, A new release candidate for tacker for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/tacker/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/tacker/log/?h=stable/stein Release notes for tacker can be found at: https://docs.openstack.org/releasenotes/tacker/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/tacker/+bugs and tag it *stein-rc-potential* to bring it to the tacker release crew's attention.

1 0

[nova][ops] Help with kernel panic on cirros image boot process.
by Jorge Luiz Correa 04 Apr '19

04 Apr '19

Hi all! I'm having kernel panic randomically with cirros image. Sometimes the instances boots, sometimes not. I'm using Openstack Queens, Ubuntu Server 18.04 and KVM (following the install guide). The nova/instances directory, where are stored ephemeral disks, is over a GlusterFS system. I've noted that other images, like Ubuntu Cloud Image, do not get this error. It's just with cirros and sometimes. I appreciate any help guiding on where I can look for to identify what is causing these errors. I've analyzed libvirt logs and them show just a launched instance, everything ok. The _base/<ID> file used to launch the instances is the same that is used with cirros instances that worked (it's in a GlusterFS). Something got wrong during the instance boot process. Boot log: [ 1.586076] EDD information not available. [ 1.590261] Freeing unused kernel memory: 1480K (ffffffff81f42000 - ffffffff820b4000) [ 1.594823] Write protecting the kernel read-only data: 14336k [ 1.598951] Freeing unused kernel memory: 1860K (ffff88000182f000 - ffff880001a00000) [ 1.625178] Freeing unused kernel memory: 168K (ffff880001dd6000 - ffff880001e00000) info: initramfs: up at 1.07 modprobe: module virtio_pci not found in modules.dep modprobe: module virtio_blk not found in modules.dep modprobe: module virtio_net not found in modules.dep modprobe: module vfat not found in modules.dep modprobe: module nls_cp437 not found in modules.dep info: copying initramfs to /dev/vda1 [ 2.028648] jbd2_journal_bmap: journal block not found at offset 12 on vda1-8 [ 2.034075] Aborting journal on device vda1-8. mount: mounting /dev on ./dev failed: No such file or directory info: initramfs loading root from /dev/vda1 switch_root: can't execute '/sbin/init': No such file or directory [ 2.692399] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 2.692399] [ 2.696061] CPU: 0 PID: 1 Comm: switch_root Not tainted 4.4.0-28-generic #47-Ubuntu [ 2.699012] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.2-1ubuntu1 04/01/2014 [ 2.702373] 0000000000000086 000000004016d54a ffff88003e2fbe10 ffffffff813eb1a3 [ 2.705849] ffffffff81cb10d8 ffff88003e2fbea8 ffff88003e2fbe98 ffffffff8118bf57 [ 2.709353] ffff880000000010 ffff88003e2fbea8 ffff88003e2fbe40 000000004016d54a [ 2.712875] Call Trace: [ 2.714013] [<ffffffff813eb1a3>] dump_stack+0x63/0x90 [ 2.715995] [<ffffffff8118bf57>] panic+0xd3/0x215 [ 2.717840] [<ffffffff81184e1e>] ? perf_event_exit_task+0xbe/0x350 [ 2.720105] [<ffffffff81084541>] do_exit+0xae1/0xaf0 [ 2.722090] [<ffffffff810845d3>] do_group_exit+0x43/0xb0 [ 2.724150] [<ffffffff81084654>] SyS_exit_group+0x14/0x20 [ 2.726207] [<ffffffff818276b2>] entry_SYSCALL_64_fastpath+0x16/0x71 [ 2.729271] Kernel Offset: disabled [ 2.730741] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 Thank you!

1 0

[Zun] Address already belongs to a bound Neutron port Error
by Navdeep Uniyal 04 Apr '19

04 Apr '19

Dear All, I have just installed Zun and tried creating a container following the instructions as per the following webpage: https://docs.openstack.org/zun/rocky/install/index.html I am getting following error while starting my test container using 'openstack appcontainer run --name container2 --net network=$NET_ID cirros ping 8.8.8.8': status_reason | Docker internal error: 500 Server Error: Internal Server Error ("IpamDriver.RequestAddress: Requested ip address {'subnet_id': u'e684a17b-6b17-4ea2-bbc9-752a21304dcc', 'ip_address': u'10.68.48.147'} already belongs to a bound Neutron port: f0d6153a-7408-4cd5-82c3-9abed48ad056"). The network I selected is a flat network on openstack with external flag true. Please advise me how to solve the issue or if there is a specific requirement for this. Thank you, Kind Regards, Navdeep

2 2

cloudkitty 9.0.0.0rc2 (stein)
by no-reply＠openstack.org 04 Apr '19

04 Apr '19

Hello everyone, A new release candidate for cloudkitty for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/cloudkitty/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/cloudkitty/log/?h=stable/stein Release notes for cloudkitty can be found at: https://docs.openstack.org/releasenotes/cloudkitty/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/cloudkitty/+bugs and tag it *stein-rc-potential* to bring it to the cloudkitty release crew's attention.

1 0

[Magnum] Unable to create Kubernetes cluster
by Anirudh Gupta 04 Apr '19

04 Apr '19

Hi Team, I am trying to create kubernetes cluster using Magnum Openstack. My External Network configuration is as follows: neutron net-create MGMT_NET --shared --router:external --provider:physical_network provider1 --provider:network_type flat neutron subnet-create MGMT_NET 10.0.61.0/24 --name MGMT_SUBNET --allocation-pool start=10.0.61.10,end=10.0.61.250 --disable-dhcp --gateway 10.0.61.1 Then I am creating a template with docker storage driver as "Overlay" openstack coe cluster template create kubernetes-cluster-template --image fedora-atomic-latest --docker-storage-driver overlay --external-network public --dns-nameserver 8.8.8.8 --master-flavor m1.small --flavor m1.small --coe kubernetes Creating a cluster with 1 master node openstack coe cluster create kubernetes-cluster --cluster-template kubernetes-cluster-template --master-count 1 --node-count 1 --keypair key-pair When I look into my stack, it shows the event kube_masters <http://192.168.121.118/horizon/project/stacks/stack/58ddd64a-8779-495d-8d31…> Create in Progress and eventaully after 1 hr, it gets failed. I have checked the Troubleshooting Guide as well, but found nothing that could help me resolving the issue. https://docs.openstack.org/magnum/rocky/admin/troubleshooting-guide.html Can you please suggest some pointers in order to resolve the issue. Regards Anirudh Gupta

1 0

RE: [charms] Enabling Neutron DVR & ovs
by James Page 04 Apr '19

04 Apr '19

Hi Emil On Sat, Mar 30, 2019 at 1:55 PM Emil Larsson <Emil.Larsson(a)zetup.se> wrote: > Hi guys, > > I have been experimenting with the enable-dvr option in neutron-api. I > cannot find a clear guide on how to configure this. > However I have ran into some issues trying to figure out the configuration > to enable dvr. > > This is where juju stops: > unit-neutron-openvswitch-1: 11:45:35 INFO > unit.neutron-openvswitch/1.juju-log Creating bridge br-int > unit-neutron-openvswitch-1: 11:45:35 INFO > unit.neutron-openvswitch/1.juju-log Creating bridge br-ex > unit-neutron-openvswitch-1: 11:45:36 DEBUG > unit.neutron-openvswitch/1.juju-log Replacing iface 'eno1' with bond master > 'os' > unit-neutron-openvswitch-1: 11:45:36 DEBUG > unit.neutron-openvswitch/1.juju-log Replacing iface 'eno2' with bond master > 'os' > unit-neutron-openvswitch-1: 11:45:36 DEBUG > unit.neutron-openvswitch/1.juju-log Replacing iface 'eno3' with bond master > 'stor' > unit-neutron-openvswitch-1: 11:45:36 DEBUG > unit.neutron-openvswitch/1.juju-log Replacing iface 'eno4' with bond master > 'stor' > unit-neutron-openvswitch-1: 11:45:37 INFO > unit.neutron-openvswitch/1.juju-log Creating bridge br-data > unit-neutron-openvswitch-1: 11:45:37 DEBUG > unit.neutron-openvswitch/1.juju-log Interface os.392 is not a Linux bridge > unit-neutron-openvswitch-1: 11:45:37 INFO > unit.neutron-openvswitch/1.juju-log Adding port os.392 to bridge br-data > unit-neutron-openvswitch-1: 11:45:37 DEBUG > unit.neutron-openvswitch/1.config-changed Failed to restart > os-charm-phy-nic-mtu.service: Unit os-charm-phy-nic-mtu.service not found. > That restart failure is a bit of a red-herring (and needs tidying) - it relates to a tactical fix for MTU configuration of interfaces in Trusty (for which we are due to drop support this year). snip [...] > > Any help appreciated :) > The current release of OpenStack Charms still requires use of the neutron-gateway charm for snat traffic routing; that said we have gateway-less features currently in development which allow the agents managed by the neutron-openvswitch charm to be configured for snat routing as well, removing the need for the gateway. Here is a bundle based on the openstack-base bundle which I've been testing with: http://paste.ubuntu.com/p/nsx86snZpb/ Obviously the network space binding, storage configuration and maas tags are all specific to my testing environment - but it demonstrates how to get this working. HTH Regards James

1 0

[dev] [nova] API updates week 19-14
by Ghanshyam Mann 04 Apr '19

04 Apr '19

Hi All, After a long break, I am continuing nova API updates over email. Please find the Nova API highlights of this week. Weekly Office Hour: =============== API office hour is on hold as of now. We can continue it if people are intrested. I am asking the feedback on this ML thread- http://lists.openstack.org/pipermail/openstack-discuss/2019-March/004336.ht… Planned Features : ============== Now we are in Train developement cycle, so I am adding the Train proposed spec first and second part includes all previously approved BP but not completed . Code Ready for Review: ------------------------------ - None Spec Ready for Review: ----------------------------- 1. Support adding description while locking an instance: - Spec: https://review.openstack.org/#/c/638629/ - Weekly Progress: Spec is in review. 2. Nova API policy improvement - Spec: https://review.openstack.org/#/c/547850/ - PoC: https://review.openstack.org/#/q/topic:bp/policy-default-refresh+(status:op… - Weekly Progress: Spec is ready to review, pushed the PoC patches for each proposed changed 3. Support deleting data volume when destroy instance - Spec: https://review.openstack.org/#/c/580336/ - Weekly Progress: Proposed for Train. Ready to review. 4. Nova API cleanup - Spec: https://review.openstack.org/#/c/603969/ - Weekly Progress: Proposed for Train. Ready to review. 5. Add host and hypervisor_hostname flag to create server - Spec: https://review.openstack.org/#/c/645458/ - Weekly Progress: Spec under review 6. Specifying az when restore shelved server - Spec: https://review.openstack.org/#/c/624689/ - Weekly Progress: Spec under review 7. default value of swap in the show flavor details API - Spec: https://review.openstack.org/#/c/648919/ - Weekly Progress: New spec, ready for review. 8. Support for changing deleted_on_termination after boot -Spec: https://review.openstack.org/#/c/580336/ - Weekly Progress: Ready for review. 9. Support delete_on_termination in volume attach api\ -Spec: https://review.openstack.org/#/c/612949/ - Weekly Progress: Ready for review. 10. Add API ref guideline for body text - ~8 api-ref are left to fix. Previously approved Spec needs to be re-proposed for Train: --------------------------------------------------------------------------- 1. Detach and attach boot volumes: - https://blueprints.launchpad.net/nova/+spec/detach-boot-volume - https://review.openstack.org/#/q/topic:bp/detach-boot-volume+(status:open+O… 2. Servers Ips non-unique network names : - https://blueprints.launchpad.net/nova/+spec/servers-ips-non-unique-network-… - https://review.openstack.org/#/q/topic:bp/servers-ips-non-unique-network-na… 3. Volume multiattach enhancements: - https://blueprints.launchpad.net/nova/+spec/volume-multiattach-enhancements - https://review.openstack.org/#/q/topic:bp/volume-multiattach-enhancements+(… BP Completed: ------------------- - None Bugs: ==== No progress report in this week. NOTE- There might be some bug which are not tagged as 'api' or 'api-ref', those are not in above list. Tag such bugs so that we can keep our eyes. -gmann

1 0

[tc] next meeting
by Mohammed Naser 04 Apr '19

04 Apr '19

Hi everyone: It's quite a busy time but our monthly meeting is due. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting I left the list of past agenda topics in order to leave it for anyone to reference back if they'd like. Please add topics by most Wednesday so we can send out an agenda before the meeting. Thanks, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 1