Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-5041

"environment non existent" acceptance tests failing on puppet-server master

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.2.2
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      1
    • Sprint:
      Client 2015-08-19
    • Release Notes:
      Not Needed

      Description

      http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppet-server_integration-system_no-conditional_full-master/98/LAYOUT=redhat6-64ma-64a,LDAP_TYPE=default,PLATFORM=default,label=beaker/testReport/junit/%28root%29/ruby_puppet_acceptance_tests_environment/environment_scenario_non_existent_rb/

      Expected the output:
      /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'doesnotexist' anywhere in the path: /tmp/environment_scenario-non_existent.rb.mPm5yg/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound)
      	from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context'
      	from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run'
      	from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:128:in `run'
      	from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute'
      	from /opt/puppetlabs/bin/puppet:5:in `<main>'
       
      To match: (?-mix:Could not find a directory environment named 'doesnotexist' anywhere in the path.*\/etc\/puppetlabs\/code)
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              erict Eric Thompson
              Reporter:
              ruth Ruth Linehan
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support