=== mup_ is now known as mup
=== Eth1 is now known as Guest53788
=== Guest53788 is now known as enp0s8
[01:47] <enp0s8> I have a node with two network interfaces how can i bring up the second nic when i deploy?
[13:27] <huats> Hi kiko
[13:27] <huats> sorry it took me ages to have a look at the various logs (regarding the issue I have of the out-of-sync image in my cluster)
[13:27] <huats> I have been able to redo the addtion of an image
[13:28] <huats> and I am still stuck with the out-of-sync thing
[13:28] <huats> the image seems to be uploaded well on the region
[13:29] <huats> but it "stops" there and it is never sent to the cluster
[13:29] <huats> there is nothing that seems wrong/special on the logs
[13:30] <huats> just that on syslog after it is sent to the region I can see
[13:30] <huats> [INFO] Updating boot image iSCSI targets.
[13:30] <huats> and I never got any reference to the custom image I have added (it only shows the generated ubuntu image I have already)
[13:31] <huats> if you have any clue :)
[13:31] <huats> It would be really interesting...
[13:31] <huats> I am really stick :(
[13:31] <huats> stuck
[13:49] <roaksoax> huats: what version of maas are you using?
[13:50] <huats> roaksoax: Hi
[13:50] <huats> 1.9.2+bzr4568-0ubuntu1
[13:50] <huats> actually I am guessing if I am providing the right kind of image to maas... since it is the first "custom" image I want to give him
[13:50] <huats> can I give to maas a qcow2 ?
[14:04] <roaksoax> huats: imthinking that the issue will still be there in 1.9.3
[14:04] <roaksoax> but i'd recommend you upgrade
[14:04] <huats> ok
[14:04] <huats> I will try that
[14:04] <huats> and regarding the qcow2 thing ?
[14:04] <roaksoax> huats: also, you can't do qcow, only root tarball
[14:04] <huats> ok
[14:04] <huats> :)
[14:05] <roaksoax> huats: how large is the image?
[14:05] <huats> that might be main issue
[14:05] <huats> not so large
[14:05] <huats> about 300M
[14:05] <roaksoax> huats: yeah so if it is qcow2 that wont work
[14:05] <huats> hum I am wondering how to convert qcow2 to tarball
[14:06] <roaksoax> huats: https://launchpad.net/maas-image-builder
[14:06] <roaksoax> huri'd sugggst you look into that
[14:06] <huats> roaksoax: does it makes that kind of convertion ?
[14:07] <roaksoax> huats: that creates a maas image from a vm. so you can see how the root image is created
[14:07] <huats> oh great
[14:08] <roaksoax> huats: also, if you are creating a third party OS(non-ubuntu) you'll need to look at curtin_hooks being created for that image
[14:08] <huats> ok
[14:08] <huats> (trying to do an opensuse one...)
[20:46] <huats> roaksoax: can you explain me a bit more about the curtin_hook ?
=== HI is now known as Guest54441
[20:47] <huats> I think I have done a tgz from the qcow2 (using a simple tar the same way it is done in maas-image-builder)