Tuesday, 2018-04-24

ianwhmm the gentoo build is timing out again00:22
ianw2018-04-23 19:42:57.073 | /tmp/in_target.d/install.d/01-nodepool-setup: line 3: sudo: command not found00:22
*** dhill_ has joined #openstack-dib00:27
*** tonyb has quit IRC00:33
*** tonyb has joined #openstack-dib00:35
*** phuongnh has joined #openstack-dib01:07
*** phuongnh has quit IRC01:55
*** phuongnh has joined #openstack-dib01:56
*** hwoarang has quit IRC03:37
*** hwoarang has joined #openstack-dib03:43
*** mvpnitesh has joined #openstack-dib05:01
*** dhill_ has quit IRC05:15
*** rajinir has quit IRC05:18
*** yolanda_ has joined #openstack-dib05:27
*** yolanda has quit IRC05:28
*** dhill_ has joined #openstack-dib05:29
*** dhill_ has quit IRC05:35
*** dhill_ has joined #openstack-dib05:36
openstackgerritAndreas Florath proposed openstack/diskimage-builder master: WIP: Docker matrix build  https://review.openstack.org/41434706:57
*** eshas has joined #openstack-dib07:04
eshasHi07:04
eshasI am facing a disk not sufficient error while working on xenial with DIB07:04
eshaswhere can I paste the trace?07:05
eshas2018-04-24 06:57:17.321 | > Unpacking make (4.1-6) ... 2018-04-24 06:57:17.321 | > Selecting previously unselected package dkms. 2018-04-24 06:57:17.321 | > Preparing to unpack .../dkms_2.2.0.3-2ubuntu11.5_all.deb ... 2018-04-24 06:57:17.321 | > Unpacking dkms (2.2.0.3-2ubuntu11.5) ... 2018-04-24 06:57:17.321 | > Selecting previously unselected package linux-firmware. 2018-04-24 06:57:17.321 | > Preparing to unpack .../linux-firmw07:06
eshasthis error keeps repeating and disk-image-create Exits with 107:06
eshas2018-04-24 06:57:17.321 | > dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.157.17_all.deb (--unpack): 2018-04-24 06:57:17.321 | >  cannot copy extracted data for './lib/firmware/ti-connectivity/wl127x-fw-4-sr.bin' to '/lib/firmware/ti-connectivity/wl127x-fw-4-sr.bin.dpkg-new': failed to write (No space left on device) 2018-04-24 06:57:17.321 | > No apport report written because the error message indicates07:07
*** pavel_V has joined #openstack-dib07:13
*** eshas has quit IRC07:30
ianweshas: try using DIB_NO_TMPFS=1 as an environment variable07:36
*** yolanda_ has quit IRC07:49
*** yolanda_ has joined #openstack-dib08:02
*** yolanda_ is now known as yolanda08:02
odyssey4megreghaynes clarkb ianw yeah, after looking through what was possible with what's already there, I came up with those three patches - any other approach would require adding new facilities to what dib does08:15
odyssey4meis the current approach preferred less?08:16
*** hashar has joined #openstack-dib08:20
*** mvpnitesh has quit IRC08:23
openstackgerritIan Wienand proposed openstack/diskimage-builder master: Bail on common devuser usernames  https://review.openstack.org/56386008:45
ianwodyssey4me: i haven't reviewed yet, sorry.  i feel like they're probably on the right track08:45
ianweshas: ^^ i finally got my consoles working, and I think the problem is that cloud-init has come along and wiped out the password.  proposed ^^08:46
*** mvpnitesh has joined #openstack-dib08:47
*** yolanda has quit IRC08:48
*** ianw is now known as ianw_pto08:54
*** yolanda has joined #openstack-dib09:01
*** eshas has joined #openstack-dib09:48
eshashttps://bugs.launchpad.net/diskimage-builder/+bug/176654009:48
openstackLaunchpad bug 1766540 in diskimage-builder "failed to write (No space left on device) error in image creation via DIB " [Undecided,New]09:48
eshasIssue with DIB in non-KVM environment after running the install_dep_test to install all dependency needed for DIB in this ppc64le openstack based env09:49
eshas@ianw_pto, @tonyb, @clarkb, @prometheanfire anyone could you take a quick look?09:59
*** mvpnitesh has quit IRC10:08
*** pmannidi has joined #openstack-dib10:11
*** mvpnitesh has joined #openstack-dib10:21
*** pmannidi has quit IRC10:47
*** phuongnh has quit IRC10:49
eshasTo export a DIB env variable, shouldit be added to environment.d for that particualr element before running ./disk_image_create For eg: DIB_DEV_USER_USERNAME=<value> should be added to a file in environment.d directory for devuser element and then ./disk_image_create be calledwith dev_user element10:50
eshasThis is to be done per element wise like DIB_RELEASE in ubuntu environemet.d etc or can all the variables beput in one script somewhere for running one ./disk_image_create command10:51
eshasany clue?10:52
ianw_ptoeshas: no, they are just regular environment variables for the program.  if that's not making sense, maybe run through something like https://www.digitalocean.com/community/tutorials/how-to-read-and-set-environmental-and-shell-variables-on-a-linux-vps11:11
eshas@ianw ok, soI canmakea .sh file with export DIB_var=value pairs and run it before running ./disk_image_create with elements11:21
eshasinstead of a very long list of DIB key-value vars with ./disk_image_create command11:23
ianw_ptoyes11:33
eshasok,i will try that, the disk space issue is still not working, i used the -no-tmps also, updated defect11:34
*** mjturek has joined #openstack-dib11:37
*** mjturek has quit IRC11:39
*** eshas has quit IRC12:26
*** mjturek has joined #openstack-dib12:38
*** vmlinuz has joined #openstack-dib12:48
*** vmlinuz has joined #openstack-dib12:48
*** mvpnitesh has quit IRC13:05
*** rajinir has joined #openstack-dib14:14
*** dhill_ has quit IRC14:18
*** dhill_ has joined #openstack-dib14:25
*** yolanda_ has joined #openstack-dib14:55
*** yolanda has quit IRC14:58
*** hashar is now known as hasharAway15:55
openstackgerritMatthew Thode proposed openstack/diskimage-builder master: Install sudo on Gentoo images by deault  https://review.openstack.org/56402816:45
*** dhill_ has quit IRC17:27
*** dhill_ has joined #openstack-dib17:34
*** dhill_ has quit IRC18:04
*** dhill_ has joined #openstack-dib18:11
*** jabadia has joined #openstack-dib18:46
*** yuvaladar has joined #openstack-dib18:46
jabadiaon OSP10 we got this - Using network interface(s): ens4f0 {'ip': u'172.31.255.207', 'mac': u'54:ab:3a:cc:48:16'}18:46
yuvaladarhe is talking about introspection image for ironic :)18:47
jabadiaon latest, we got this - "Using network interface(s): eth0 {'ip': u'172.31.4.9', 'mac': u'38:ea:a7:31:b0... ) "18:47
jabadiaduring introspection18:47
jabadiaWhy we're seeing ethX and not ENS's18:47
jabadiain addition, during the introspection , we notice-   biosdevname not found , sounds related, but i'm not aure ..18:48
clarkbbiosdevname is what produces the ens vs eth device names aiui18:49
clarkbhow are you building the image? what elements, etc18:49
*** EBD has joined #openstack-dib18:49
yuvaladarwe are using images built by rdo folks18:50
EBDbiosdevname is missing fro mthe image18:50
EBDbut even after adding it and the appropriate udev rule18:50
EBDthe name we get is still not we get from overcloud18:50
EBDwe tried passing biosdevname=1 explicitly in the pxe command, to no avail18:51
EBD  "name": "eth1",  "has_carrier": true,18:52
EBD  "ipv4_address": "172.31.4.7",18:52
EBD  "biosdevname": em2,18:52
EBDthis is what we get18:52
clarkbis rdo using dib? (trying to figure out how this relates back to dib now)18:52
EBD"name": "ens4f1",18:52
yuvaladarthey use dib, yes18:52
EBDthis is what we get from ospd1018:52
clarkbis the problem the mismatch between biosdevname: em2 and name: ens4f1? where are these values coming from?18:55
EBDno, its that we're not seeing ens4 at all18:55
EBDthat is the new proper naming, but not for the 7.4 centos introspection image18:55
EBDcouldnt make biosdevname return ens4f0 with any flag, on the osp10 system either, so doubt that it it's responsibility18:56
EBDthe eth1 and ens4f1 come from kernel iguess - /sys/class18:57
EBDthe em2 is the output from biosdevname that we tried to use to atl east have ironic report anything resembling18:57
clarkbhttps://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-consistent_network_device_naming_using_biosdevname that seems to imply installing the package and setting the boot parameter flag are the things that are required to make it work18:58
clarkband em* would be correct for an embedded device according to that document18:58
EBDdidnt yum install, but copied over the installed executable18:59
EBDno change18:59
clarkbif you have it reporting em4 or similar I would say it is working?18:59
EBDwell, that;s how we got the em2 for the biosdevname, but not expected result and should be set as the name attribute, no bios devnmae19:00
clarkbI've got a meeting to run now, but seems like this would be a support question for redhat centos if biosdevname isn't doing what you expect it to?19:00
EBDem naming (nor pXpY) is not what we need19:00
clarkbI understand but according to the docs that is correct19:01
EBDwe need the naming as will apear on onvercloud19:01
clarkbso you'd need to take it up with the platform?19:01
EBDthat's what we read too, and yet we get diff results on operating system19:01
EBDok, thanks19:02
*** yolanda__ has joined #openstack-dib19:15
*** yolanda_ has quit IRC19:18
*** vmlinuz has quit IRC19:18
*** vmlinuz has joined #openstack-dib19:20
*** vmlinuz has joined #openstack-dib19:20
*** vmlinuz has quit IRC19:34
clarkbEBD: yuvaladar thinking about it a littlemore is the ironic introspection image a different kernel/distro than the host itself?19:44
clarkbis that the issue? different behavior between those?19:44
EBDno, both 693-2119:55
*** vmlinuz has joined #openstack-dib19:59
*** vmlinuz has joined #openstack-dib19:59
*** dhill_ has quit IRC20:17
yuvaladarso we found the solution20:20
yuvaladarsort of :)20:20
yuvaladarthe way tripleo builds their introspection initramfs image is awkward, and there is a faux udev rule in place20:20
yuvaladarso i guess it's not a dib problem at all20:21
*** dhill_ has joined #openstack-dib20:25
*** yuvaladar has quit IRC20:43
*** rajinir has quit IRC21:12
*** vmlinuz has quit IRC21:19
*** jabadia has quit IRC21:31
*** EBD has quit IRC22:12
*** hasharAway has quit IRC22:13
*** dhill_ has quit IRC23:18
*** mjturek has quit IRC23:42

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