764933 - Add a CentOS-6.2-x86 (32bit) kickstart option for scl1

Status: RESOLVED FIXED

(Infrastructure & Operations :: RelOps: General, task)

Description

[Jake Watkins [:dividehex]]

Currently, there is only an option to kickstart a CentOS-6.2-x86_64 (64bit) version.  We will need a 32bit version setup for possible talos nodes on IX 4-node systems.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

This means mirroring 32-bit repositories, too.  We're going to need more gigs.

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

Repos are mirrored, thanks to catlee.

I *think* we can point kickstart to these repos to do the install, meaning the admin hosts don't have to have more space.  I'll need to experiment with that.

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

I added images/ to the mirror for i386 CentOS-6.2 that catlee did in bug 773379.  Then I edited up a new kickstart config pointing --url to the root of this repository.   I had to mirror the vmlinuz and initrd.img from images/pxeboot to mvadm01, then the kickstart worked!  It failed because it couldn't find EPEL and puppet in the post-install.

I'm also mirroring a current version of epel6 for i386, and will mirror puppet from puppetlabs as well.  With that in place, this should be able to do an install.

I don't think we'll be able to get this trick to work with x86_64 until we upgrade to 6.3, sadly - I did that bad a job of mirroring centos!

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

This successfully installed CentOS-6.2 i386 on relabs07.  However, it doesn't puppetize:

Jul 16 14:46:00 relabs07 puppet-agent[3742]: (/File[/var/lib/puppet/lib]) Failed to generate additional resources using 'eval_generate: Certname "puppetagain base ca/emailaddress=[e-mail]/ou=release engineering/o=mozilla, inc." must not contain unprintable or non-ASCII characters
Jul 16 14:46:00 relabs07 puppet-agent[3742]: (/File[/var/lib/puppet/lib]) Could not evaluate: Certname "puppetagain base ca/emailaddress=[e-mail]/ou=release engineering/o=mozilla, inc." must not contain unprintable or non-ASCII characters Could not retrieve file metadata for puppet://puppet/plugins: Certname "puppetagain base ca/emailaddress=[e-mail]/ou=release engineering/o=mozilla, inc." must not contain unprintable or non-ASCII characters
Jul 16 14:46:00 relabs07 puppet-agent[3742]: Could not retrieve catalog from remote server: Certname "puppetagain base ca/emailaddress=[e-mail]/ou=release engineering/o=mozilla, inc." must not contain unprintable or non-ASCII characters
Jul 16 14:46:00 relabs07 puppet-agent[3742]: Using cached catalog
Jul 16 14:46:00 relabs07 puppet-agent[3742]: Could not retrieve catalog; skipping run
Jul 16 14:46:00 relabs07 puppet-agent[3742]: Could not send report: Certname "puppetagain base ca/emailaddress=[e-mail]/ou=release engineering/o=mozilla, inc." must not contain unprintable or non-ASCII characters
[root@relabs07 ~]# puppet --version
2.7.18

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

So, C was awesome enough to point out the release notes that caused this error - it was a security fix.  I've filed https://projects.puppetlabs.com/issues/15561 for the overly-broad regexp.  In the interim, I think we need to pin the Puppet version we're using in the manifests.  We also need to note that the puppetlabs repo is a snapshot.

Having done that manually, I came to another problem: packages::setup uses url paths like
  url_path => "repos/yum/mirrors/puppetlabs/el/6/products/$hardwaremodel"
which evaluate to
  repos/yum/mirrors/puppetlabs/el/6/products/i686
rather than the expected
  repos/yum/mirrors/puppetlabs/el/6/products/i386

We want $architecture, not $hardwaremodel, there.

So, a patch is forthcoming for all of that.  Once that's in, it just remains to put the right kickstart file in scl1 and this is finished.

Comment 6

[Dustin J. Mitchell [:dustin] (he/him)]

Attachment: bug764933.patch

Turns out the puppet version was already pinned (good, I thought so).  I moved it to packages::puppet for good measure.

This gets a 32-bit CentOS install actually installing packages, but it still fails due to missing releng packages.  We can solve that later, though (by building the packages).  This bug was just to get them kickstarting.

Comment 7

[Rail Aliiev [:rail]]

Comment on attachment 642987 [details] [diff] [review]
bug764933.patch

lgtm