[PUP-4057] Acceptance tests should not rely on the puppetpath beaker option Created: 2015/02/27  Updated: 2015/04/09  Resolved: 2015/03/02

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

Type: Bug Priority: Normal
Reporter: Josh Cooper Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: AIO
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks SERVER-401 Investigate jetty_external_root_ca.rb... Closed
Relates
relates to SERVER-400 Try beaker from pr/719 Closed
Template:
Story Points: 1
Sprint: Client 2015-03-04
QA Contact: Kurt Wall

 Description   

Several acceptance tests rely on puppetpath for both code and configuration related paths. Historically that setting was the same as puppetconfdir, but with the code/config split, it no longer makes sense.

The acceptance tests should be updated to:

  1. Use beaker's host.puppet['setting'] methods so the test doesn't depend on hard-coded beaker default
  2. Query for codedir or confdir as appropriate.
  3. Take into account the agent vs master application, e.g. host.puppet('master')['confdir']


 Comments   
Comment by William Hopper [ 2015/03/02 ]

Merged at https://github.com/puppetlabs/puppet/commit/18afa5884d8db9272fddc2807585fd0addf2a0b6

Comment by Kylo Ginsberg [ 2015/03/02 ]

This passed CI. No test/review needed since it's an acceptance test change.

Comment by Kurt Wall [ 2015/03/26 ]

Nothing for Test Rail here.

Generated at Thu Nov 14 01:37:53 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.