| *** EugenMayer9 is now known as EugenMayer | 00:56 | |
| *** queria is now known as Guest6731 | 03:26 | |
| *** queria is now known as Guest6732 | 03:31 | |
| *** tkajinam is now known as Guest6741 | 06:15 | |
| *** arxcruz is now known as arxcruz|rover | 08:52 | |
| manuvakery1 | Hi . It is noticed that in case of ubuntu18 instance when created with --config-drive true option, the vendor data file /var/lib/cloud/instance/vendor-data.txt was found empty .. once i restarts the instance the vendor data is present in the file .. Am i missing something here? | 11:08 |
|---|---|---|
| frickler | manuvakery1: that sounds like a bug, is this really only happening with that specific ubuntu version (I'm assuming you are talking about Ubuntu 18.04 LTS) for you or with any cloud image? | 11:24 |
| manuvakery1 | frickler: yes its happening only with Ubuntu 18.04 LTS | 11:25 |
| manuvakery1 | other distributions working as expected | 11:26 |
| frickler | manuvakery1: might be an issue with cloud-init then. can you check whether the file is present on the config-drive? maybe check the cloud-init log for possible issues | 11:27 |
| manuvakery1 | did not see any issue in the cloud-init log https://www.irccloud.com/pastebin/ZLDsTi3t/cloud-init-log | 11:34 |
| frickler | manuvakery1: I tried to reproduce, but it seems I'm failing completely, can you share how your vendordata look like? I'm seeing data in the sources but not in the instance data no matter what I try | 14:52 |
| jpic | hi all, i'm facing a really weird situation, it all starts with : Failed to attach 6f96dc86-3648-4125-8d5c-fce114cd2813 at /dev/vdg: libvirt.libvirtError: Requested operation is not valid: target vdg already exists | 17:07 |
| jpic | fine, but vdg is not in virsh domblklist, nor in virsh dumpxml ... it is however, still in virsh edit!! | 17:07 |
| jpic | a ceph rbd disk is present in virsh edit <instance>, at the same time it is not visible in virsh domblklist <instance> nor in virsh dumpxml <instance>, any idea what is going on? | 17:09 |
| jpic | that same volume is at the same time attached to another libvirt domain: the one that corresponds to it's actual attachment in openstack database | 17:11 |
| jpic | removed it with virsh edit: openstack could attach. I'm guessing it's definitely not an openstack bug, because if openstack is basing its opinion of free devices on the same code that virsh dumpxml executes: it's normal it doesn't see the volume | 17:31 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!