[CentOS-devel] Fwd: Vagrant boxes (7.2.1511)

On 14/12/16 18:17, Laurentiu Pancescu wrote:
> On 14/12/16 16:57, Carlos Rodrigues wrote:
>> (*) The point here is to be able to destroy a vagrant instance and
>> safely recreate it sometime in the future (maybe the far future). This
>> also means no mandatory system updates inside the VM to be able to
>> build the guest additions.
> 
> You are already able to recreate any older instance of a box and it will
> work perfectly, including networking and shared folders via NFS - just
> not with the VirtualBox Guest Additions or if you have the vbguest
> plugin installed.
> 
> Perhaps I should mention I don't use the GA myself - I never saw them
> being worth the trouble, except for improved video performance on
> desktop installations.  Maybe it just doesn't fit my use case, as they
> seem to be quite popular with other users.
> 
> Best regards,
> Laurențiu
> 

Just as a follow up on that issue (at the builder side) : as we saw that
we needed another builder/hypervisor for that kojid image builder
instance, I deployed today a centos 7.3.1611 node and added it to CBS :
https://cbs.centos.org/koji/hostinfo?hostID=9

It's not the first centos 7 builder (as we have already ppc64/ppc64le
and aarch64 centos 7 builders) but it was the first one on which we
tried the imagefactory image builder task.

Our first test wasn't working, but after some troubleshooting with
Laurentiu in #centos-devel (and analysis from python tracebacks) we
found the issue .
It seems there is a mismatch between koji version installed on the
builders and pykickstart from 7.3.1611 :

koji-builder-1.10.1-1.el7.centos.noarch
pykickstart-1.99.66.10-1.el7.noarch

We'll investigate the koji upgrade later with Thomas, but the priority
was to build those Vagrant images, and so have a builder up and running.
The following "hot patch" seems to have solved the initial issues :

--- /usr/sbin/kojid.orig	2016-12-14 16:16:45.461903827 +0000
+++ /usr/sbin/kojid	2016-12-14 16:23:49.356851809 +0000
@@ -2446,7 +2446,7 @@
         #      may not be a problem if the included kickstarts are present
         #      in the repository we checked out.
         if opts.get('ksversion'):
-            version =
ksparser.version.makeVersion(ksparser.stringToVersion(opts['ksversion']))
+            version =
ksparser.version.makeVersion(ksparser.version.stringToVersion(opts['ksversion']))
         else:
             version = ksparser.version.makeVersion()
         self.ks = ksparser.KickstartParser(version)
@@ -2828,7 +2828,7 @@
         #      We require users to flatten their kickstart file.
         if self.opts.get('ksversion'):
             version = ksparser.version.makeVersion(
-                ksparser.stringToVersion(self.opts['ksversion']))
+                ksparser.version.stringToVersion(self.opts['ksversion']))
         else:
             version = ksparser.version.makeVersion()
         ks = ksparser.KickstartParser(version)

After that, the tasks that were failing were able to run and produce
artifacts (vagrant boxes) :
https://cbs.centos.org/koji/taskinfo?taskID=148368

Hope that it can unblock the situation and we'll discuss the potential
upgrade of the remaining builders to CentOS 7 too (and koji upgrade too,
after other tests)


-- 
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20161214/82e0254f/attachment-0004.sig>