Wednesday, 2017-09-20

ianwpromethenfire: yeah, it's weird, the build is ok but it seems the connection is not up, need to dig into it00:14
ianwpabelanger: ^00:16
ianwoh, not in here00:16
*** owalsh has quit IRC01:11
*** owalsh has joined #openstack-dib01:12
*** Sukhdev has quit IRC02:24
prometheanfireianw: you can ping me in -infra if needed03:18
*** yolanda has quit IRC03:34
*** yolanda has joined #openstack-dib03:34
*** chhavi has joined #openstack-dib03:35
*** chhavi has quit IRC03:38
*** yolanda has quit IRC06:27
*** yolanda has joined #openstack-dib06:29
*** noam_ has joined #openstack-dib07:01
*** hashar has joined #openstack-dib07:40
hwoarangHello. We are facing a strange thing with dib. The following command "disk-image-create --no-tmpfs -o deployment_image.qcow2 -t qcow2 -p "vlan,vim,less,bridge utils,language-pack-en,iputils-ping,rsyslog,curl,iptables,lvm2" ubuntu-minimal vm enable-serial-console simple-init devuser growroot openssh-server" results to the following kernel panic http://paste.openstack.org/show/621517/ We are using 2.8.1 from pip09:16
hwoarangit seems to work if you set root=/dev/sda1 instead of the cloudimg-rootfs label09:46
hwoarangyolanda do you happen to know anything about this^ ?09:46
hwoarangi only found this reference https://www.mail-archive.com/kernel-packages@lists.launchpad.net/msg238540.html09:46
yolandahwoarang, seems as it was not adding the label properly in the partition, that's strange09:48
yolandabecause our default is to set that label09:48
yolandahwoarang, do you have logs from the build?09:49
hwoarangyolanda: i can get you some09:49
yolandathx09:50
yolandahwoarang, also if you inspect the image, i guess that the partition is not labeled properly?09:52
*** hashar is now known as hasharAway09:52
hwoaranghow can i tell?09:53
hwoarangyou mean after i boot the image?09:53
yolandahwoarang, i normally use guestfish for it09:53
hwoarangah ok09:53
hwoarangyolanda: http://dev.gentoo.org/~hwoarang/log.txt09:58
yolandammm, not much useful to see the block device behaviour, but i can try to reproduce locally10:00
yolandait looks as the label is not set10:00
yolandahwoarang, do you use latest dib version?10:01
hwoarangthat's with 2.8.010:01
hwoarang2.8.1 also fails10:01
hwoarang2.7.0 too10:01
hwoarangi guess 2.8.1 is the one from git10:02
yolandaok let me try that10:02
hwoarangat least that's what bifrost pulls anyway10:02
hwoarangyolanda: i also simply launch the image using 'kvm -m 4096 -nographic deployment_image.qcow2'10:11
hwoarangon a xenial host10:12
*** yolanda has quit IRC11:18
*** yolanda has joined #openstack-dib11:24
*** hasharAway is now known as hashar11:39
*** noam_ has quit IRC13:19
*** hashar is now known as hasharAway13:22
*** dmarlin has joined #openstack-dib15:30
*** Sukhdev_ has joined #openstack-dib15:58
*** Sukhdev_ has quit IRC16:52
*** hasharAway has quit IRC16:57
*** hashar has joined #openstack-dib16:57
*** Sukhdev_ has joined #openstack-dib18:20
*** Sukhdev_ has quit IRC18:33
*** Sukhdev has joined #openstack-dib21:34
*** hashar has quit IRC21:50
ianw[    0.944039] VFS: Cannot open root device "sda1" or unknown-block(0,0): error -622:17
ianw[    0.945123] Please append a correct "root=" boot option; here are the available partitions:22:17
ianw[    0.946350] fd00        41943040 vda  driver: virtio_blk22:17
ianw[    0.947188]   fd01         1640384 vda1 b729d3ed-0122:17
ianw[    0.947995] 0b00         1048575 sr0  driver: sr22:17
ianw[    0.948780] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)22:17
*** dmarlin has quit IRC22:35

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!