devel

devel@lists.centos.org

10 participants
4617 discussions

testing vagrant and the vagrant box's
by Karanbir Singh 10 Aug '16

10 Aug '16

hi guys Lala brought up a good point - we should validate all the various vagrant box's we build from cbs, and we should ideally validate them against the vagrant shipped from the sclo-vagratn1 stack. Ideally get to a point where we can block release either way. Ie. dont release vagrant box's that dont work with our vagrant, and dont release vagrant if it breaks any of the vagrant box's that we build and ship. I'll send a PR through shortly that should fix the problem here : https://ci.centos.org/view/SCLo/job/SCLo-sclo-vagrant1-sclo-C7-x86_64/ from there on, whats the best to get this 2way testing setup ? Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

Problem with vagrant box (ssh-ing during ``vagrant up`` doesn't work)
by Rafal Skolasinski 10 Aug '16

10 Aug '16

Hi, I wanted to try vagrant box of Centos7 for my vm but I encounter problems during setting up a vm. I did very basic setup, in empty folder I did ``` vagrant init centos/7 vagrant up ``` In a result it repetitively promts ``` default: Warning: Authentication failure. Retrying... ``` Full output here: http://pastebin.com/JrQHER6L I am using Linux Mint 17.3 with VirtualBox 5 and Vagrant 1.8.5. Any clues what's going on wrong here? Best, Rafal P.S. I am sorry if I doubled the email, I don't know if it get through on the first time before I registered to the mailing list.

5 9

[Opstools][poll] weekly meeting time
by Matthias Runge 06 Aug '16

06 Aug '16

Hello, to make further progress, we should schedule weekly meetings for the newly founded and approved SIG Opstools The link to the poll is here: http://doodle.com/poll/etgeynq7x3w5t9pr If you're interested in opstools and would like to participate, your feedback is appreciated! Even if you can't make it and we need to change the poll/add times. Best, Matthias

4 4

CentOS PaaS SIG meeting (2016-08-03)
by Troy Dawson 03 Aug '16

03 Aug '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 3 August 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated testing -- images / image building - Open Floor

1 0

role based builder capability
by Karanbir Singh 28 Jul '16

28 Jul '16

hi, we've spoken about this in the past a few times, and I've gone ahead to setup the rdobuilder account for building against koji. what this means is that its now possible to have a role based koji account, with some level of limited credentials, that allows a robot like process to build, tag, request-test from koji content. Ofcouse, we need to ensure this bot is unable to tag to release any content, or to promote internally. Anyone else needing this functionality, you will need to get in touch and come through to the CBS meeting to talk through the requirements and justifications. Haikel: this should unblock your work here. Brian: Can we get this included in the SIGGuide content as well, thanks, -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

1 0

How to test CentOS Origin images
by Troy Dawson 28 Jul '16

28 Jul '16

Hi, This email is to get a discussion started. I don't have the answers, so feel free to add to the discussion. The PaaS SIG (through the hard work of Mohammed Ahmed, mzee1000) is now producing OpenShift Origin images. They are currently for origin 1.2. We need some tests so that we can say "These are good images" and then release them. What are some tests that we can run on the images to verify they are good? Troy

4 4

CentOS PaaS SIG meeting (2016-07-27)
by Troy Dawson 27 Jul '16

27 Jul '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 27 July 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated testing -- images / image building - OpsTools SIG ? - Open Floor

1 0

Testing Vagrant images on ci.centos.org?
by Laurentiu Pancescu 26 Jul '16

26 Jul '16

Currently, the development of the Vagrant images relies on manual testing (I create scratch builds containing my changes and test them locally - due to hardware limitations, this means only testing with VirtualBox on an OS X host). Is it technically possible to automatically test the Vagrant images on ci.centos.org, using e.g. KVM via vagrant-libvirt? Perhaps we could add some sort of trigger on cbs.centos.org to trigger the tests, once a scratch build is successful? Regards, Laurențiu

2 1

/etc/sysconfig/network-scripts/network-functions max limit is 255
by Donatas Abraitis 22 Jul '16

22 Jul '16

Hi folks, what do you think of introducing new variable which could define max value for index iterating over PREFIX/NETMASK pair? Problem: Now it's hardcoded value of 255 in /etc/sysconfig/network-scripts/network-functions: expand_config () { local i=0 val for idx in '' {0..255} ; do ipaddr[$i]=$(eval echo '$'IPADDR$idx) if [ -z "${ipaddr[$i]}" ]; then [ "$idx" ] && [ $idx -ge 2 ] && break continue fi prefix[$i]=$(eval echo '$'PREFIX$idx) netmask[$i]=$(eval echo '$'NETMASK$idx) broadcast[$i]=$(eval echo '$'BROADCAST$idx) arpcheck[$i]=$(eval echo '$'ARPCHECK$idx) We are running plenty of addresses (over 500) under loopback interface and announcing them as /32 for upstream hosts. With IPv6 everything is OK, because it has already native secondary option. I suggest to add additional variable like MAXALIAS to define this '255' inside ifcfg-lo. Any thoughts? Thank you! -- Donatas

1 0

glibc build fails on disk >2TB
by Captain Wiggum 21 Jul '16

21 Jul '16

We are rebuilding the centos 6.8 src.rpm's for both 64-bit (.x86_64.rpm) and also 32-bit-compat (.i686.rpm) When making 32-bit compatible build on a disk >2TB, the build will fail because or large inodes: /home/mlos/WORK/os/PACKAGES/glibc/WORK/BUILD/glibc-2.12-2-gc4ccff1/build-i686-linuxnptl/elf/sln /home/mlos/WORK/os/PACKAGES/glibc/WORK/BUILD/glibc-2.12-2-gc4ccff1/build-i686-linuxnptl/elf/symlink.list /home/mlos/WORK/os/PACKAGES/glibc/WORK/glibc-root/lib/ld-linux.so.2: invalid destination: Value too large for defined data type The solution is to add "-D_FILE_OFFSET_BITS=64" and this has fixed the issue on glibc and all our other i686 RPM builds. However, with the latest update glibc-2.12-1.192.el6.src.rpm we find adding the above flag will cause the following error: In file included from ftello.c:29: ../include/stdio.h:151: warning: asm declaration ignored due to conflict with previous rename ftello.c:66: error: '__EI_ftello' aliased to undefined symbol '__GI_ftello' make[3]: *** [/home/mlos/WORK/os/PACKAGES/glibc/WORK/BUILD/glibc-2.12-2-gc4ccff1/build-i686-linuxnptl/libio/ftello.os] Error 1 Has anyone else hit this issue? Any tips appreciated.

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel