Uploaded image for project: 'Puppet Agent'
  1. Puppet Agent
  2. PA-2336

Issues with SLES 15

    XMLWordPrintable

Details

    • CI Blocker
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • None
    • None
    • None
    • None
    • modules
    • Platform OS
    • Platform OS Kanban
    • Needs Assessment

    Description

      When attempting to add SLES 15 to the module test pipelines I ran into some issues regarding the images. First of all I found that there was no agent image available from:
      http://enterprise.delivery.puppetlabs.net/,http://enterprise.delivery.puppetlabs.net
      thus preventing me from running a master agent setup from it as we normally do with SLES.
      While then trying to run an agent only build I received an error message stating that the 'repomd.xml' file within the puppet 6 SLES 15 yum repository had been signed with an unknown key and as such it was caused to error out, see below:

      Failure/Error: run_puppet_install_helper
      Beaker::Host::CommandFailure:
        Host 'm2owv8ttzjv122u.delivery.puppetlabs.net' exited with 104 running:
         zypper --non-interactive --gpg-auto-import-keys in puppet-agent
        Last 10 lines of output were:
       
        	File 'repomd.xml' from repository 'Puppet 6 Repository sles 15 - x86_64' is signed with an unknown key '7F438280EF8D349F'. Continue? [yes/no] (no): no
        	Warning: Skipping repository 'Puppet 6 Repository sles 15 - x86_64' because of the above error.
        	Loading repository data...
        	Error building the cache:
        	[puppet6|http://yum.puppetlabs.com/puppet6/sles/15/x86_64] Valid metadata not found at specified URL
        	Some of the repositories have not been refreshed because of an error.
        	Reading installed packages...
        	'puppet-agent' not found in package names. Trying capabilities.
        	No provider of 'puppet-agent' found.
       
      # ./.bundle/gems/ruby/2.4.0/gems/beaker-4.0.0/lib/beaker/host.rb:375:in `exec'
      # ./.bundle/gems/ruby/2.4.0/gems/beaker-4.0.0/lib/beaker/command_factory.rb:35:in `execute'
      # ./.bundle/gems/ruby/2.4.0/gems/beaker-4.0.0/lib/beaker/host/unix/pkg.rb:77:in `install_package'
      # ./.bundle/gems/ruby/2.4.0/gems/beaker-puppet-1.1.0/lib/beaker-puppet/install_utils/foss_utils.rb:373:in `block in install_puppet_agent_on'
      # ./.bundle/gems/ruby/2.4.0/gems/beaker-4.0.0/lib/beaker/shared/host_manager.rb:130:in `run_block_on'
      # ./.bundle/gems/ruby/2.4.0/gems/beaker-4.0.0/lib/beaker/shared/host_manager.rb:118:in `block in run_block_on'
      # ./.bundle/gems/ruby/2.4.0/gems/beaker-4.0.0/lib/beaker/shared/host_manager.rb:117:in `map'
      # ./.bundle/gems/ruby/2.4.0/gems/beaker-4.0.0/lib/beaker/shared/host_manager.rb:117:in `run_block_on'
      # ./.bundle/gems/ruby/2.4.0/gems/beaker-4.0.0/lib/beaker/dsl/patterns.rb:37:in `block_on'
      # ./.bundle/gems/ruby/2.4.0/gems/beaker-puppet-1.1.0/lib/beaker-puppet/install_utils/foss_utils.rb:346:in `install_puppet_agent_on'
      # ./.bundle/gems/ruby/2.4.0/gems/beaker-puppet_install_helper-0.9.7/lib/beaker/puppet_install_helper.rb:98:in `run_puppet_install_helper_on'
      # ./.bundle/gems/ruby/2.4.0/gems/beaker-puppet_install_helper-0.9.7/lib/beaker/puppet_install_helper.rb:8:in `run_puppet_install_helper'
      # ./spec/spec_helper_acceptance.rb:9:in `<top (required)>'
      # ./spec/acceptance/force_spec.rb:1:in `require'
      # ./spec/acceptance/force_spec.rb:1:in `<top (required)>'
      

      Finally after retrying on a debug run I noticed an error stating that it was unable to find a nightly build, which I confirmed after navigating both to the yum archive and to the nightly archive:

        curl: (22) The requested URL returned error:   404 Not Found
        error: http://nightlies.puppetlabs.com/07BB6C57: import read failed(2).
      

      Attachments

        Issue Links

          Activity

            People

              scott.garman Scott Garman
              david.swan David Swan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support