Thursday, 2018-05-31

*** dlw has joined #kata-general00:18
*** dlw has quit IRC00:36
*** LinuxMe has joined #kata-general01:08
*** dlw has joined #kata-general01:12
*** LinuxMe has quit IRC01:12
*** dlw has quit IRC01:23
*** dlw has joined #kata-general01:25
*** LinuxMe has joined #kata-general02:09
*** LinuxMe has quit IRC02:13
*** LinuxMe has joined #kata-general04:10
*** LinuxMe has quit IRC04:14
*** LinuxMe has joined #kata-general04:45
*** LinuxMe has quit IRC04:50
*** LinuxMe has joined #kata-general06:46
*** LinuxMe has quit IRC06:51
*** jodh has joined #kata-general07:25
kata-dev-irc-bot<shlallen1990> Why not come to KubeCon Shanghai? :-)07:39
*** gwhaley has joined #kata-general07:54
*** GonZo2000 has joined #kata-general08:17
*** GonZo2000 has quit IRC08:36
kata-dev-irc-bot<digambarpat> Hello everyone09:20
kata-dev-irc-bot<digambarpat> I am installing kata through developer guide09:20
kata-dev-irc-bot<digambarpat> Getting below error in "Install guest kernel images" section09:20
kata-dev-irc-bot<digambarpat> Need help - openstack@openstack:/tmp/tmp.kWhL5tTYPF/linux-4.14.22$ sudo install -o root -g root -m 0755 -D "$(realpath arch/${kernel_arch}/boot/bzImage)" "${kata_vmlinuz}" realpath: arch/x86_64/boot/bzImage: No such file or directory09:21
kata-dev-irc-bot<digambarpat> I debugged issue and foind there is not x86_64 folder under arch09:26
gwhaley@digambarpat - really - most odd! That path is part of the kernel source, so should exist. Even if you built a non-x86 kernel arch, that path should exist (even if the bzImage file was not there).09:28
gwhaleyCan you check the logs for the kernel build phase and see if there is anything obvious?09:28
kata-dev-irc-bot<digambarpat> Yes09:32
kata-dev-irc-bot<digambarpat> I will go through it09:32
kata-dev-irc-bot<digambarpat> I need to check09:33
kata-dev-irc-bot<digambarpat> ubuntu system is x86_6409:41
kata-dev-irc-bot<digambarpat> openstack@openstack:/tmp/tmp.kWhL5tTYPF/linux-4.14.22/arch$ uname -a Linux openstack 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux09:41
kata-dev-irc-bot<digambarpat> @graham.whaley Here is it09:44
kata-dev-irc-bot<digambarpat> openstack@openstack:/tmp/tmp.kWhL5tTYPF/linux-4.14.22/arch$ cat /proc/version Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 201809:44
kata-dev-irc-bot<digambarpat> looks like my system has amd6409:44
kata-dev-irc-bot<digambarpat> but amd64 and x86_64 are names for the same processor types09:45
kata-dev-irc-bot<vizard561> Hi kata-team why do you use insecure opensuse repo?10:19
kata-dev-irc-bot<digambarpat> Hey, OS and system have x86_64 architecture10:25
kata-dev-irc-bot<digambarpat> but when we download openstack@openstack:/tmp/tmp.34jvwWtjAA/linux-4.14.22/arch$ ls alpha  arm    blackfin  cris  h8300    ia64     m32r  metag       mips     nios2     parisc   s390   sh     tile  unicore32  xtensa arc    arm64  c6x       frv   hexagon  Kconfig  m68k  microblaze  mn10300  openrisc  powerpc  score  sparc  um    x86 openstack@openstack:/tmp/tmp.34jvwWtjAA/linux-4.14.22/arch$10:25
kata-dev-irc-botopenstack@openstack:/tmp/tmp.34jvwWtjAA/linux-4.14.22/arch$ pwd /tmp/tmp.34jvwWtjAA/linux-4.14.22/arch10:25
kata-dev-irc-bot<digambarpat> when we download linux-4.14.22, it doesn't have x86_64 under /arch directory10:26
kata-dev-irc-bot<digambarpat> openstack@openstack:/tmp/tmp.34jvwWtjAA/linux-4.14.22/arch$ ls alpha  arm    blackfin  cris  h8300    ia64     m32r  metag       mips     nios2     parisc   s390   sh     tile  unicore32  xtensa arc    arm64  c6x       frv   hexagon  Kconfig  m68k  microblaze  mn10300  openrisc  powerpc  score  sparc  um    x86 openstack@openstack:/tmp/tmp.34jvwWtjAA/linux-4.14.22/arch$10:26
kata-dev-irc-botopenstack@openstack:/tmp/tmp.34jvwWtjAA/linux-4.14.22/arch$ pwd /tmp/tmp.34jvwWtjAA/linux-4.14.22/arch10:26
gwhaleyhi @digambarpat - most strange. I'm not familiar enough with the osbuilder internals to know where it is pulling that kernel from etc. - can you either open a github issue with the details, or wait for @jcvenega to come online in a few hours?10:32
kata-dev-irc-bot<james.o.hunt> @vizard561 - we use OBS as it's the best facility we've found so far to build binaries for different distros. We have had to add warnings into the install guides about OBS since although it *does* appear to allow https downloads, we noticed that certain https OBS links silently redirect to http. We suspect an OBS web server misconfiguration and have tried to raise this with SuSE. See:10:36
kata-dev-irc-bothttps://github.com/kata-containers/documentation/pull/83#issuecomment-38947482810:36
kata-dev-irc-bot<vizard561> @james.o.hunt thanks for your describe10:38
kata-dev-irc-bot<james.o.hunt> @vizard561 - It's very frustrating, but until either SuSE change the way OBS works or we can find a good alternative, we are rather stuck :(10:40
kata-dev-irc-bot<james.o.hunt> So if anyone can help us out with this, please let us know! :slightly_smiling_face:10:41
kata-dev-irc-bot<vizard561> @james.o.hunt Suse dont'have any comments about this?10:43
kata-dev-irc-bot<james.o.hunt> I believe we've tried to contact the right people, but I wasn't party to the discussions. @eric.ernst can provide further details I suspect.10:44
kata-dev-irc-bot<vizard561> @james.o.hunt i''be wait a good news about this situation10:46
*** LinuxMe has joined #kata-general10:47
kata-dev-irc-bot<digambarpat> @graham.whaley I will open a bug for this and also will discuss with @jose.carlos.venegas.m10:51
*** LinuxMe has quit IRC10:52
gwhaley@digambarpat - thx! - can you give the steps you took - as @jodh noted to me we were not sure if you were doing this through osbuilder or trying to build a kernel by hand - please add details to the Issue ;-)10:53
kata-dev-irc-bot<digambarpat> @graham.whaley I am following this section - https://github.com/kata-containers/documentation/blob/master/Developer-Guide.md#install-guest-kernel-images10:56
kata-dev-irc-bot<digambarpat> Its failing @ install-guest-kernel-images10:56
kata-dev-irc-bot<digambarpat> step - sudo install -o root -g root -m 0755 -D "$(realpath arch/${kernel_arch}/boot/bzImage)" "${kata_vmlinuz}"10:56
kata-dev-irc-bot<digambarpat> Above command is giving below error10:57
*** dlw has quit IRC10:57
kata-dev-irc-bot<digambarpat> Error - "realpath: arch/x86_64/boot/bzImage: No such file or directory"10:58
*** gwhaley has quit IRC11:05
kata-dev-irc-bot<vizard561> @eric.ernst And again confuse:) Manual: https://github.com/kata-containers/documentation/blob/master/how-to/how-to-use-k8s-with-cri-containerd-and-kata.md told me "install containerd", and here: https://github.com/kata-containers/documentation/blob/master/how-to/how-to-use-k8s-with-cri-containerd-and-kata.md#start-kubernetes-with-kubeadm script told me "Prevent docker iptables". Again my question is - docker need to install or11:52
kata-dev-irc-botnot need?:D11:52
kata-dev-irc-bot<vizard561> Docker and Containerd it's an different projects now, or i'm wrong?:slightly_smiling_face:11:54
*** LinuxMe has joined #kata-general12:13
*** gwhaley has joined #kata-general12:15
*** LinuxMe has quit IRC12:26
kata-dev-irc-bot<eric.ernst> No docker needed @vizard56112:32
kata-dev-irc-bot<vizard561> @eric.ernst thanks!12:33
*** LinuxMe_ has joined #kata-general12:53
gwhaley@digambarpat @jose.carlos.venegas.m - I will see if I can re-create the kernel image doc build issue here whilst I'm waiting for some other stuff to complete. If I do I will13:18
gwhaleyopen an Issue and do some diagnosis13:18
gwhaleyheh - after running the script, sure, the kernel arch/xxx dir for x86_64 is called x86 - so using $(arch) will not map.... I suspect a little bit of shell magic for s/x86_64/x86/ is going to be needed here. I suspect it is fine for the other arch's13:30
gwhaley^^ @digambarpat13:30
gwhaleyI'll open an Issue13:30
* gwhaley steps back one step.. ah, not quite that simple...13:31
gwhaleyHi @digambarpat - OK, those build instructions worked for me, and I do have a file in arch/x86_64/boot/bzImage - and that is a symlink to arch/x86/boot/bzImage - which is what the 'realpath'13:41
gwhaleyfixes in the scripts (turns the x86_64 into x86 etc.).13:41
gwhaleyI suspect your kernel build may not have completed successfully. What I did was copied the shell commands from the doc into a script file and set -x and -e in that file - that should then halt execution at the kernel13:42
gwhaleybuild if it fails...13:42
gwhaleyIf that does not help - please run with the -x in the shell script and post the last piece of the log with the tail of the kernel build and the following commands.13:44
gwhaleyI've had a peek on github to see if I can find your user @digambarpat - but I see 7 potential users there who could be you ;-) If you let me know your github ID (presuming you have one), then I'll /cc you13:45
gwhaleyon the ticket I'm about to open...13:45
kata-dev-irc-bot<digambarpat> @graham.whaley I will try that13:53
kata-dev-irc-bot<digambarpat> @graham.whaley My github id - digambar1513:53
gwhaleythx - just writing up the Issue now :-)13:54
kata-dev-irc-bot<digambarpat> cool13:54
kata-dev-irc-bot<vizard561> sudo kubeadm init --skip-preflight-checks --cri-socket /run/containerd/containerd.sock --pod-network-cidr=10.244.0.0/16 Flag --skip-preflight-checks has been deprecated, it is now equivalent to --ignore-preflight-errors=all Team, can you change flags on the docs? Or it isn't need?)14:21
kata-dev-irc-bot<eric.ernst> What kubeadm version you using?14:25
kata-dev-irc-bot<eric.ernst> Sounds like a good suggestion regardless. Can you send a PR?14:26
kata-dev-irc-bot<vizard561> @eric.ernst kubeadm version: &version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:05:37Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}14:27
kata-dev-irc-bot<vizard561> old?)14:27
kata-dev-irc-bot<james.o.hunt> @vizard561 - I'll let @eric.ernst respond, but you'll find details of versions of things like k8s/golang we test with in the versions database: https://github.com/kata-containers/runtime/blob/master/versions.yaml14:53
kata-dev-irc-bot<vizard561> @james.o.hunt so PR isn't need?:slightly_smiling_face:14:54
kata-dev-irc-bot<eric.ernst> We should probably be at 1.10.3 at this point. Assuming =all works on 1.10.0, we should update the docs.14:57
kata-dev-irc-bot<vizard561> @eric.ernst i'll be watching you:yum:15:01
*** LinuxMe_ has quit IRC15:56
kata-dev-irc-bot<anne> From today's working-committee meeting, here's a community etherpad to keep track of who's submitted talks where (or intends to) and on what topics. Intention here is to make sure we don't overlap topics, and keep track of who's speaking where so we can promote it! https://etherpad.openstack.org/p/KataTalks15:58
kata-dev-irc-bot<anne> also feel free to add other events--this was just to get the list started16:00
*** LinuxMe has joined #kata-general16:02
*** gwhaley has quit IRC16:59
*** jodh has quit IRC17:00
*** LinuxMe has quit IRC17:18
*** LinuxMe has joined #kata-general18:53
*** LinuxMe has quit IRC20:25
*** LinuxMe has joined #kata-general20:31
*** LinuxMe has quit IRC22:20
*** LinuxMe has joined #kata-general23:16
*** LinuxMe has quit IRC23:21

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