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

Transient hostname-related failure on Solaris SPARC hosts

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Build Automation
    • Labels:
      None
    • Template:
    • Team:
      Agent
    • QA Risk Assessment:
      No Action

      Description

      Solaris SPARC hosts sometimes come up after an LDOM reset thinking their hostname is unknown.delivery.puppetlabs.net. Hilarity ensues. Also, test failures. To wit (see https://jenkins.puppetlabs.com/user/kurt.wall/my-views/view/puppet-agent%20master%20Manual%20Pipeline/job/platform_puppet-agent_intn-van-sys_suite-manual-puppet-master/52/SLAVE_LABEL=beaker,TEST_TARGET=solaris-10-sparc/console):

              ta0m7niiyxkamyp.delivery.puppetlabs.net (master) 18:35:13$ service puppetserver reload
                Redirecting to /bin/systemctl reload  puppetserver.service
              
              ta0m7niiyxkamyp.delivery.puppetlabs.net (master) executed in 4.16 seconds
              RuntimeError: PuppetAcceptance::DSL::Helpers.with_puppet_running_on failed (check backtrace for location) because: Host 'sol10.delivery.puppetlabs.net' exited with 1 running:
               puppet agent -t --environment corrective_change_new_resource_b0nc56m7 --server ta0m7niiyxkamyp.delivery.puppetlabs.net
              Last 10 lines of output were:
              	Info: Using configured environment 'corrective_change_new_resource_b0nc56m7'
              	Info: Retrieving pluginfacts
              	Info: Retrieving plugin
              	Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: No matching entry for selector parameter with value 'unknown.delivery.puppetlabs.net' at /etc/puppetlabs/code/environments/corrective_change_new_resource_b0nc56m7/manifests/site.pp:2:14 on node unknown.delivery.puppetlabs.net
              	Warning: Not using cache on failed catalog
              	Error: Could not retrieve catalog; skipping run
      

      We should diagnose and fix this.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              kurt.wall Kurt Wall
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support