Hide Forgot
Description of problem: Cirros 0.5.1 image does not boot on an OSP VM Version-Release number of selected component (if applicable): 13, 16.1 How reproducible: 100% Steps to Reproduce: try to boot a VM with a 0.5.1 cirros image using tobiko http://pastebin.test.redhat.com/885987 or using manual cmd: http://pastebin.test.redhat.com/885989 then ssh to compute and try virsh console from the nova_libvirt container Actual results: vm console hangs because instance failed to boot no prompt Expected results: see the vm user login prompt, ability to ssh into instance Additional info:
sosreports, stack home,all overcloud /var/log, are at : http://rhos-release.virt.bos.redhat.com/log/pkomarov_sosreports/BZ_1858972/
sample tobiko log from a failure : http://pastebin.test.redhat.com/885994
0.5.0 introduced a requirement for at least 128MB of RAM [1], AFAICT that's why 0.5.1 isn't able to boot with the 64MB you've assigned in the flavor. We recently had to bump this upstream [2] ahead of introducing 0.5.1 [3] FWIW. Closing this out as NOTABUG, feel free to reopen if you still have issues after bumping the available RAM in your flavor. [1] https://github.com/cirros-dev/cirros/releases/tag/0.5.0 [2] https://review.opendev.org/#/c/730307/ [3] https://review.opendev.org/#/c/711492/
Thanks Lee , 128 of ram is what we're using for the flavor (overcloud) [stack@undercloud-0 ~]$ openstack flavor list +--------------------------------------+------------------+-----+------+-----------+-------+-----------+ | ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public | +--------------------------------------+------------------+-----+------+-----------+-------+-----------+ | f2e8a382-72dd-4889-b0bc-f720a7ee5019 | hbPetiFCz3mTucVH | 128 | 0 | 0 | 1 | True | +--------------------------------------+------------------+-----+------+-----------+-------+-----------+ So is this still closed ?
(In reply to pkomarov from comment #4) > Thanks Lee , 128 of ram is what we're using for the flavor > > (overcloud) [stack@undercloud-0 ~]$ openstack flavor list > +--------------------------------------+------------------+-----+------+----- > ------+-------+-----------+ > | ID | Name | RAM | Disk | > Ephemeral | VCPUs | Is Public | > +--------------------------------------+------------------+-----+------+----- > ------+-------+-----------+ > | f2e8a382-72dd-4889-b0bc-f720a7ee5019 | hbPetiFCz3mTucVH | 128 | 0 | > 0 | 1 | True | > +--------------------------------------+------------------+-----+------+----- > ------+-------+-----------+ > > So is this still closed ? Apologies but http://pastebin.test.redhat.com/885989 listed 64MB. Feel free to reopen if you're still not able to run instances with 128MB. Can you also provide the following: $ openstack server show $instance $ openstack console log show $instance Thanks
still does not reproduce , I'll reopen if it does..
Eliad suggested the cause could be we where creating the image with the wrong image format (raw instead of qcow2). I created a patch [1] that should fix it and restore the Cirros image to version 5.1 as specified on OpenStack documentation page [2] [1] https://review.opendev.org/#/c/753970/ [2] https://docs.openstack.org/image-guide/obtain-images.html#cirros-test
This isn't an openstack-nova issue, closing again as NOTABUG.