[lxc-users] OpenVSwitch compiling on CentOS 6.8
Hi, I don't know what could be the problem. Host is Ubuntu 16.04 64 bit ii lxc 2.0.4-0ubuntu1~ubuntu16.04.2 rattila@fcubi:~$ uname -a Linux fcubi 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Container: [rattila@cos64 ~]$ uname -a Linux cos64 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux I wanted to build OVS 2.5.0 rpm: [root@cos64 openvswitch-2.5.0]# rpmbuild -bb -D 2.6.32-642 rhel/openvswitch.spec ... 1725: ovn-sbctl - testok 1726: ovn-controller - ovn-bridge-mappingsok 1727: ovn-controller-vtep - test chassis skipped ( ovn-controller-vtep.at:113) 1728: ovn-controller-vtep - test binding 1skipped ( ovn-controller-vtep.at:180) 1729: ovn-controller-vtep - test binding 2skipped ( ovn-controller-vtep.at:244) 1730: ovn-controller-vtep - test vtep-lswitch skipped ( ovn-controller-vtep.at:283) 1731: ovn-controller-vtep - test vtep-macs 1 skipped ( ovn-controller-vtep.at:335) 1732: ovn-controller-vtep - test vtep-macs 2 skipped ( ovn-controller-vtep.at:406) Waiting for something since some days. :-( 2700 pts/4S 0:00 -bash 14824 pts/4S+ 0:00 rpmbuild -bb -D 2.6.32-642 rhel/openvswitch.spec 16544 pts/4T 0:00 /bin/sh ./tests/testsuite -C tests AUTOTEST_PATH=util 16549 pts/4T 0:00 /bin/sh ./tests/testsuite -C tests AUTOTEST_PATH=util 16550 pts/4T 0:00 /bin/sh ./tests/testsuite -C tests AUTOTEST_PATH=util 16551 pts/4T 0:00 cat 16553 pts/4T 0:00 /bin/sh ./tests/testsuite -C tests AUTOTEST_PATH=util 16556 pts/4T 0:00 /usr/bin/perl 21876 ?Ss 0:00 sshd: rattila [priv] 21878 ?S 0:00 sshd: rattila@pts/5 21879 pts/5Ss 0:00 -bash 21895 pts/5R+ 0:00 ps ax 25797 pts/4S+ 0:00 /bin/sh -e /var/tmp/rpm-tmp.0qU6e1 25798 pts/4S+ 0:00 make check TESTSUITEFLAGS=-j2 25799 pts/4S+ 0:00 make check-recursive 25800 pts/4S+ 0:00 /bin/sh -c fail=; \?if (target_option=k; case ${targe 26420 pts/4S+ 0:00 make check-am 26522 pts/4S+ 0:00 make check-local 26523 pts/4S+ 0:00 /bin/sh ./tests/testsuite -C tests AUTOTEST_PATH=util I don't know it is an LXC problem or not. TIA, Ruzsi ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] OpenVSwitch compiling on CentOS 6.8
On Thu, Sep 8, 2016 at 5:50 PM, Ruzsinszky Attila < ruzsinszky.att...@gmail.com> wrote: > Hi, > > I don't know what could be the problem. > > Host is Ubuntu 16.04 64 bit > ii lxc > 2.0.4-0ubuntu1~ubuntu16.04.2 > rattila@fcubi:~$ uname -a > Linux fcubi 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 > x86_64 x86_64 x86_64 GNU/Linux > > Container: > [rattila@cos64 ~]$ uname -a > Linux cos64 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 > x86_64 x86_64 x86_64 GNU/Linux > > I wanted to build OVS 2.5.0 rpm: > > [root@cos64 openvswitch-2.5.0]# rpmbuild -bb -D 2.6.32-642 > rhel/openvswitch.spec > ... > 1725: ovn-sbctl - testok > 1726: ovn-controller - ovn-bridge-mappingsok > 1727: ovn-controller-vtep - test chassis skipped ( > ovn-controller-vtep.at:113) > 1728: ovn-controller-vtep - test binding 1skipped ( > ovn-controller-vtep.at:180) > 1729: ovn-controller-vtep - test binding 2skipped ( > ovn-controller-vtep.at:244) > 1730: ovn-controller-vtep - test vtep-lswitch skipped ( > ovn-controller-vtep.at:283) > 1731: ovn-controller-vtep - test vtep-macs 1 skipped ( > ovn-controller-vtep.at:335) > 1732: ovn-controller-vtep - test vtep-macs 2 skipped ( > ovn-controller-vtep.at:406) > > Waiting for something since some days. :-( > > 2700 pts/4S 0:00 -bash > 14824 pts/4S+ 0:00 rpmbuild -bb -D 2.6.32-642 rhel/openvswitch.spec > 16544 pts/4T 0:00 /bin/sh ./tests/testsuite -C tests > AUTOTEST_PATH=util > 16549 pts/4T 0:00 /bin/sh ./tests/testsuite -C tests > AUTOTEST_PATH=util > 16550 pts/4T 0:00 /bin/sh ./tests/testsuite -C tests > AUTOTEST_PATH=util > 16551 pts/4T 0:00 cat > 16553 pts/4T 0:00 /bin/sh ./tests/testsuite -C tests > AUTOTEST_PATH=util > 16556 pts/4T 0:00 /usr/bin/perl > 21876 ?Ss 0:00 sshd: rattila [priv] > 21878 ?S 0:00 sshd: rattila@pts/5 > 21879 pts/5Ss 0:00 -bash > 21895 pts/5R+ 0:00 ps ax > 25797 pts/4S+ 0:00 /bin/sh -e /var/tmp/rpm-tmp.0qU6e1 > 25798 pts/4S+ 0:00 make check TESTSUITEFLAGS=-j2 > 25799 pts/4S+ 0:00 make check-recursive > 25800 pts/4S+ 0:00 /bin/sh -c fail=; \?if (target_option=k; case > ${targe > 26420 pts/4S+ 0:00 make check-am > 26522 pts/4S+ 0:00 make check-local > 26523 pts/4S+ 0:00 /bin/sh ./tests/testsuite -C tests > AUTOTEST_PATH=util > > I don't know it is an LXC problem or not. > > Without knowing what ./tests/testsuite actually do, it's hard to tell. It's possibly that the code is doing something not available in lxc/lxd (e.g. loading kernel module), and doesn't handle failure correctly (e.g. keep waiting instead of saying fail). A workaround is to edit your SRPM (or possible the makefile, by creating an additional patch), and comment-out the test code (there should be "make check" or "make test" somehwere) -- Fajar ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] OpenVSwitch compiling on CentOS 6.8
Hi, Thanks for your prompt answer! My workaround was this: there is a "--without check" parameter. The rpm was built successfully. :-) TIA, Ruzsi ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] inventory / dashboard tool to manage LXD containers' lifecycle
Thank you all for the tips. I wasn't aware Ansible introduced the lxd module. I knew they were working on it, good to know! It is not a full lifecycle solution but probably better than nothing. I'd love to see this integrated into Foreman, eventually. CONFIDENTIALITY NOTICE: This email message (and any attachment) is intended only for the individual or entity to which it is addressed. The information in this email is confidential and may contain information that is legally privileged or exempt from disclosure under applicable law. If you are not the intended recipient, you are strictly prohibited from reading, using, publishing or disseminating such information and upon receipt, must permanently delete the original and destroy any copies. We take steps to protect against viruses and other defects but advise you to carry out your own checks and precautions as Kambi does not accept any liability for any which remain. Thank you for your co-operation. ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] do_dump: 866 dump failed with 1
On Wed, Aug 17, 2016 at 05:09:34PM -0400, Connor Zanin wrote: > Hi all, > > Environment: > ubuntu server 16.04 > kernel 4.4 > both lxc and criu packages downloaded from ubuntu repos > > I am trying to checkpoint a privileged container. After many hours of > banging my head against the internet, I humbly turn to the mailing list. > > Thanks for any and all help! Can you post the logs? There should be a dump.log in the directory you chose to put the images in. The LXC log may also be instructive. Tycho > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Recommended techniques for dynamically provisioning containers using lxd
On Thu, Sep 8, 2016, 01:05 Zach Lanich wrote: Umberto, I’m not 100% sure of what SaltStack uses under the hood lib wise, but it’s written in Python an already does everything that Lib does. We’re talking more of how the creation of the LXD containers themselves, including setting Mounts, Static IP, etc. SaltStack & Chef handle everything else from there once the provisioned container is connected to the master. CloudInit would certainly be an option as the 2nd part of the equation if we weren’t already using a configuration management tool @zach, what configuration management tool are you guys using? ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Wifi in container
On Thu, Sep 8, 2016, 01:05 Claudio Corsi wrote: > Hello, > > I am attempting to get a Linksys AE3000 USB wireless dongle to work within > my container. I am running LXC 2.0 on Ubuntu 16.04 and have an Ubuntu 16.04 > guest up and running. > > In both the host OS and the container the device is detected and is listed > when running lsusb > > Bus 001 Device 004: ID 13b1:003b Linksys AE3000 802.11abgn (3x3) Wireless > Adapter [Ralink RT3573] > > On the host OS i am able to display the device details using both iw and > iwconfig, however in the container i get no output from either command. > > I have added the device to the container with the following command > > lxc config device add wap usb-001-004 unix-char path=/dev/usb/001/004 > > without any change in container. > > Any advice would be greatly appreciated. > > C > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users Was your container stopped when the device was added? ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Wifi in container
I tried a number of scenario, including restarting the container after adding the device to it. On Thu, Sep 8, 2016 at 1:38 PM, Eric wrote: > > > On Thu, Sep 8, 2016, 01:05 Claudio Corsi wrote: > >> Hello, >> >> I am attempting to get a Linksys AE3000 USB wireless dongle to work >> within my container. I am running LXC 2.0 on Ubuntu 16.04 and have an >> Ubuntu 16.04 guest up and running. >> >> In both the host OS and the container the device is detected and is >> listed when running lsusb >> >> Bus 001 Device 004: ID 13b1:003b Linksys AE3000 802.11abgn (3x3) Wireless >> Adapter [Ralink RT3573] >> >> On the host OS i am able to display the device details using both iw and >> iwconfig, however in the container i get no output from either command. >> >> I have added the device to the container with the following command >> >> lxc config device add wap usb-001-004 unix-char path=/dev/usb/001/004 >> >> without any change in container. >> >> Any advice would be greatly appreciated. >> >> C >> ___ >> lxc-users mailing list >> lxc-users@lists.linuxcontainers.org >> http://lists.linuxcontainers.org/listinfo/lxc-users > > > Was your container stopped when the device was added? > > > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users > ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Wifi in container
On September 8, 2016 2:53:38 PM EDT, Claudio Corsi wrote: >I tried a number of scenario, including restarting the container after >adding the device to it. > Sometimes the container needs to be fully stopped, and started again for the changes to take in effect ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users