[SERVER-420] Try out puppet-server acceptance against aio packages for non-el7 linux platforms Created: 2015/03/09  Updated: 2015/03/25  Resolved: 2015/03/20

Status: Closed
Project: Puppet Server
Component/s: Puppet Server
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: Jeff McCune Assignee: Unassigned
Resolution: Done Votes: 0
Labels: AIO
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
is blocked by SERVER-438 Produce puppetserver 2.0.0-rc2 Closed
relates to SERVER-499 Fix pre_suite for Windows Closed
relates to PUP-4093 Try out puppet acceptance against aio... Resolved
relates to SERVER-412 Get Pup4/Pup-Svr2 acceptance tests pa... Closed
SERVER-426 Try puppet-server on Ubuntu 14.04 64 ... Sub-task Closed  
SERVER-424 Try Puppet Server on Ubuntu 12.04 64 ... Sub-task Closed  
SERVER-430 Try Puppet Server on RHEL6 64 bit Sub-task Closed Jeff McCune  
SERVER-428 Try Puppet Server on Fedora 20 64 bit Sub-task Closed Jeff McCune  
SERVER-432 Try Puppet Server on Debian 8 64 bit Sub-task Closed  
SERVER-434 Try Puppet Server on Debian 7 64 bit Sub-task Closed  
Epic Link: Green: Puppet 4.0 Changes
Sub-team: emerald
Story Points: 3
Sprint: Server Emerald 2015-03-18, Server Emerald 2015-04-01
QA Contact: Erik Dasher


We are currently running the AIO puppet-server component pipeline:


against EL7 only.

We will be adding additional platforms once we get EL7 out the door a in priority order which can be found here:


Note that, in addition to EL7, we have have packages currently for:

  • RHEL5
  • RHEL6
  • Debian 7 (wheezy)
  • Ubuntu 12.04 (precise)
  • Ubuntu 14.04 (trusty)

For each platform, please add a comment to the ticket reporting success/failure. If there are failures, create tickets to track the followup work (i.e. don't do it in the aegis of this ticket or it might live forever).
One thing to note is that we should only be testing against el7 masters, so some of the node configs (in acceptance/config/nodes) will need to be updated accordingly.

Risk assessment: Low (no additional validation needed)
Probability: Low (does not impact users)
Severity: Low (does not impact users)

Comment by Jeff McCune [ 2015/03/19 ]

Working with Wayne today, we sorted out the following plan of action:

Within the context of the aio branch and pipeline, which strives to mirror the master pipeline so that we can easily integrate back into master when the time comes, the following things are true:

  • Jobs inside of the pipeline are matrix jobs, but there is only a single dimension to the matrix. There are not multiple dimensions in order to avoid testing combinations that we don't want to test or having to deal with combination filters.
  • The single dimension is on LAYOUT. PLATFORM will remain because it may cause issues if it is removed, but the value of PLATFORM will be empty (NONE).
  • sqa-utils-gem is sufficient. It needs to have support added for fedora20 and debian8, which is ticketed in QENG-2053. These VM's already exist as templates in the pooler. It would be a nice to avoid the default of adding the agent role to the master, but this is non-trivial to add.
Comment by Jeff McCune [ 2015/03/19 ]

Here's the list of layouts we want to test based on the meeting with Josh Cooper and Justin Stoller:

The thinking is: We're going to test the agent running on the master at 64 bit. For additional coverage we're going to test a 32 bit agent, when available, over the network. We're going to get windows coverage by testing win2008r2-64a against redhat7 on merge and nightly and windows2008-r2-64a nightly against ubuntu1404-65m.

The values for the LAYOUT parameter are:

On Merge:



redhat7-64m-64a (32 bit is not available)

Comment by Jeff McCune [ 2015/03/19 ]

Build #42 is the first build that I've run that attempts all of the GA targets.

Comment by Jeff McCune [ 2015/03/19 ]

Build #42 was no-good because 2.0.0-rc3 has only RHEL7 packages.

Build #46 is closer because PACKAGE_BUILD_VERSION=2.0.0.SNAPSHOT.2015.03.19T1436, which has package builds for RPM and DEB platforms. Similarly, puppet-agent 0.9.0 is not a suitable value for PUPPET_BUILD_VERSION becasue it is rhel7 only as well. Recent puppet-agent builds with expanded platforms are suitable.

Comment by Jeff McCune [ 2015/03/20 ]

Putting into closed because all of the platforms have been run and triaged into other tickets.

Generated at Sun May 31 14:07:21 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.