Tuesday, 2018-01-30

*** shoaaaad has joined #openstack-dib00:03
*** dhill_ has quit IRC00:26
*** andreas_s has joined #openstack-dib01:01
openstackgerritIan Wienand proposed openstack/diskimage-builder master: GPT partitioning support  https://review.openstack.org/53349001:04
*** andreas_s has quit IRC01:05
*** mjturek has quit IRC01:05
tonybianw: Do you want the bad news?02:14
prometheanfirelol02:15
prometheanfireianw: don't fall for it02:15
tonybprometheanfire: come on who could resist a ping like that ;P02:16
prometheanfiretonyb: thanks for making my point for me :P02:20
tonybI do what I can02:20
prometheanfiretonyb: you had a script for the freeze to see what projects were out of sync and if we could branch didn't you?02:20
tonybhttps://review.openstack.org/#/c/492382/ ?02:21
prometheanfirewell, guess I keep that tab open02:22
prometheanfireor, todoist item to check every day and work at it02:22
tonybprometheanfire: or a cronjob | mail :)02:23
tonybprometheanfire: I just ran it from time to time02:23
ianwtonyb: yep02:24
prometheanfiresame thing in my case02:24
tonybianw: gdisk doesn't support ppc64{,le} parted does ...02:24
prometheanfiretonyb: why not?02:25
tonybianw: the boot partition type (prep) isn't defined in gdisk02:25
prometheanfire13 KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~mips ~ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~arm-linux ~x86-linux"02:25
prometheanfirewe have gptfdisk keyworded02:26
tonybianw: the parted GUID is http://git.savannah.gnu.org/cgit/parted.git/tree/libparted/labels/gpt.c#n15102:26
tonyband that (and the short hand seem to be missing from gdisk02:26
prometheanfireoh, it doesn't understand the format ppc/ppc64 requires then (but runs fine otherwise)?02:26
tonybprometheanfire: Well it compiles and runs but you can actually build a botoable system with it02:26
prometheanfiregotcha02:26
ianwi thought it was going too well02:27
* tonyb wonders what a botoble system is ... probably aws related ;p02:27
ianwthis doesn't seem like it would be too hard to fix in sgdisk?02:27
prometheanfirelol02:27
prometheanfireor patch gptfdisk?02:27
tonybianw: hard?  probably not but we'd need to wait for that to be released and picke up by $distros02:28
ianwi've got that sinking feeling when the first hit for the source code is a sourceforge(t).net link02:29
tonyb:(02:30
tonybianw: I can keep digging to verify the isn't a fallback from the old MBR values that I missed02:31
prometheanfirelol02:32
ianw Added new type code: 9E1A2D38-C612-4316-AA26-8B49521E5A8B, or gdisk code02:32
ianw  4100, for PowerPC PReP (PowerPC reference platform) boot.02:32
ianwthat's in the NEWS file ...02:32
tonybHuh okay02:32
ianwok, from 2013, so ... maybe it's a config thing here02:33
tonybianw: Or perhaps I looked at the wrong code02:34
tonybianw: what version?02:35
prometheanfiretonyb: random quuestion, you play with gvt (intel)?02:35
ianwtonyb: i'm poking at git clone https://git.code.sf.net/p/gptfdisk/code gptfdisk-code02:35
tonybprometheanfire: I don02:36
tonyb't recognise that acronym so probably not ;p02:36
prometheanfirek02:36
tonybianw: Ahhh so the code merged 2013-10-10, the release after that is 0.8.8 and centos has 0.8.602:39
tonybianw: so it isn't terminal just not great.02:39
prometheanfirethat seems old, but then again, cent02:40
ianwtonyb: https://sourceforge.net/p/gptfdisk/code/ci/0fde58b966f37807260ad0dd8997e3f0c824d39c seems pretty straight forward02:42
ianwit's probably likely we'd get a patch in02:42
ianwto the rh package i mean02:43
tonybianw: I guess we can try.02:43
tonybin thre meantime I can build a patched version to see if that's all there is02:43
tonybokay so the version in el6 is *newer* than el702:44
tonybhttp://mirror.centos.org/centos/7/os/x86_64/Packages/gdisk-0.8.6-5.el7.x86_64.rpm vs http://mirror.centos.org/centos/6/os/x86_64/Packages/gdisk-0.8.10-1.el6.x86_64.rpm02:45
prometheanfireLOL02:45
ianwhmm, i some bugzilla spelunking will show a backport and missing tags or something02:45
ianwhttps://bugzilla.redhat.com/show_bug.cgi?id=101515702:50
openstackianw: Error: Error getting bugzilla.redhat.com bug #1015157: NotPermitted02:50
tonybianw: ack02:50
tonybianw: so .... do you have time to push on that or should I try an do it (or find someone else to do it) ?02:51
ianwtonyb: i can file the bug, i'll cc you02:53
tonybThanks02:53
tonybin the meantime I'll try to build 0.8.10 in CBS and test that.02:53
ianw1015157 is private i guess -- not keeping secrets it's just a request for the package in RHEL6, and through circumstances it seems the version from rhel6 epel, which was 0.8.10 just got pulled in and how we ended up like this02:54
tonybianw: and I can't just build it in cbs :( Oh well time to get more hacky ;P03:20
tonybianw: okay +1'd the GPT change but it'd be super awesome if you'd include the block-device yaml I linked to.03:49
tonybianw: if not I can add it as a follow up03:49
ianwtonyb: line 12 there is a typo?03:50
tonybianw: Yeah, not really sure how I messed that up03:51
* tonyb clearly fails and copy-n-paste03:51
tonybianw: You get the idea, 2 partitions 1 has to be type 0x410003:52
ianwok03:52
*** andreas_s has joined #openstack-dib04:45
*** andreas_s has quit IRC04:49
*** andreas_s has joined #openstack-dib07:17
*** pmannidi has quit IRC07:40
*** pmannidi has joined #openstack-dib07:42
*** andreas_s has quit IRC08:50
*** lennyb has quit IRC08:50
*** andreas_s has joined #openstack-dib08:50
*** hrw has joined #openstack-dib09:29
*** andreas_s_ has joined #openstack-dib09:31
*** lennyb has joined #openstack-dib09:34
*** andreas_s has quit IRC09:35
*** andreas_s has joined #openstack-dib10:33
*** andreas_s_ has quit IRC10:36
*** andreas_s_ has joined #openstack-dib10:55
*** andreas_s has quit IRC10:58
*** andreas_s_ has quit IRC11:19
*** andreas_s has joined #openstack-dib11:20
*** andreas_s has quit IRC11:47
*** andreas_s has joined #openstack-dib11:47
*** brault has quit IRC13:57
*** brault has joined #openstack-dib13:57
*** mjturek has joined #openstack-dib14:00
*** brault has quit IRC14:02
*** andreas_s has quit IRC15:10
*** andreas_s has joined #openstack-dib15:11
*** snasir has joined #openstack-dib15:24
snasirHi is there an existing bug in disk-image-builder to create a fedora-atomic image ?15:24
*** andreas_s has quit IRC15:29
*** andreas_s has joined #openstack-dib15:30
*** andreas_s has quit IRC15:40
*** andreas_s has joined #openstack-dib15:45
*** andreas_s has quit IRC15:59
*** andreas_s has joined #openstack-dib16:01
*** andreas_s has quit IRC16:05
*** andreas_s has joined #openstack-dib16:06
*** dhill_ has joined #openstack-dib16:36
*** andreas_s has quit IRC16:40
*** andreas_s has joined #openstack-dib16:44
*** andreas_s has quit IRC16:53
*** andreas_s has joined #openstack-dib16:54
snasirI keep on running into this error "error: min-free-space-percent '3%' would be exceeded, 401.4 kB more required" when i use the DIB tool to build fedora-atomic image16:56
snasirCan anyone tell me how to resolve this16:56
snasirI was using the instructions here https://github.com/openstack/magnum/tree/master/magnum/drivers/common/image/fedora-atomic16:56
clarkbsnasir: if you can paste the complete dib output to a paste service and share that it would probably help with debugging16:57
snasirclarkb: https://thepasteb.in/p/mwh1Y1Vvmyxc516:58
snasirIn addition, do you know if fedora-27 is supported with DIB ? The magnum instructions even with Pike point to Fedora-25 ? Thanks16:59
*** andreas_s has quit IRC17:00
clarkbthat looks like an error from ostree I think because it wants the loop device to be larger. I'm on a phone so hard to dig in more but I would look to see where the loopback device is created and see about making it larger17:03
snasirclarkb: how do i increase the loopback device?17:04
snasirIs there a parameter with the DIB tool to do so17:04
clarkbI'm not sure, you'll need to grep through that log and see what defines it and then make that bigger.17:05
clarkbwhen I make it to a real computer I can look more closely17:05
greghaynesI *think* whats going on is that where we determine the size of the block device happens before finalise.d, and it looks like in finalise.d youre adding a bunch of data17:20
greghaynesso yes you can force a size but really you cant add much data that late in the build - that phase is after the block device and fs have been created so theres really no way that data can be used in the estimation of how large of a fs you need17:21
greghayneshttps://docs.openstack.org/diskimage-builder/latest/user_guide/building_an_image.html#module-local-loop has some info on setting size17:24
*** brault has joined #openstack-dib17:40
*** brault has quit IRC18:04
*** brault has joined #openstack-dib20:06
*** brault has quit IRC20:11
*** sai is now known as sai-pto20:29
*** andreas_s has joined #openstack-dib22:58
*** andreas_s has quit IRC23:02
*** brault has joined #openstack-dib23:05
*** brault has quit IRC23:09
*** dhill_ has quit IRC23:47

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