[MODULES-4078] Solaris 11 unable to `pkg refresh` puppetlabs.com Created: 2016/11/07  Updated: 2018/11/26

Status: Accepted
Project: Modules
Component/s: puppet_agent
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Brandon High Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: maintenance, solaris
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Team: Platform OS

 Description   

Not sure if this is just a transient network issue or a permanent problem but we're seeing the following failure when attempting to upgrade Solaris 11 agents with the puppet_agent module

Debug: /Stage[main]/Puppet_agent::Osfamily::Solaris/Exec[puppet_agent copy packages]: The container Class[Puppet_agent::Osfamily::Solaris] will propagate my refresh event
      Debug: Exec[puppet_agent ensure pkg publishers are available](provider=posix): Executing 'pkg refresh puppetlabs.com'
      Debug: Executing: 'pkg refresh puppetlabs.com'
      Notice: /Stage[main]/Puppet_agent::Osfamily::Solaris/Exec[puppet_agent ensure pkg publishers are available]/returns: pkg: The image cannot be modified as it is currently in use by another package client.
      Error: /Stage[main]/Puppet_agent::Osfamily::Solaris/Exec[puppet_agent ensure pkg publishers are available]: Failed to call refresh: pkg refresh puppetlabs.com returned 7 instead of one of [0]
      Error: /Stage[main]/Puppet_agent::Osfamily::Solaris/Exec[puppet_agent ensure pkg publishers are available]: pkg refresh puppetlabs.com returned 7 instead of one of [0]
      Debug: Class[Puppet_agent::Osfamily::Solaris]: The container Stage[main] will propagate my refresh event
      Debug: Class[Puppet_agent::Osfamily::Solaris]: The container Class[Puppet_agent::Prepare] will propagate my refresh event

Example of a failing job



 Comments   
Comment by Branan Riley [ 2018/05/11 ]

I'm gonna assume this was a transient at this point. Feel free to re-open if you want

Comment by Fadimana Baylak [ 2018/11/23 ]

Hi Brandon,

Did you solve this problem? I'm still getting this error.

 

 

Comment by Brandon High [ 2018/11/26 ]

Fadimana Baylak We're not seeing the issue in our CI system anymore. Unfortunately, I don't have any information on what changed.

Generated at Fri Dec 13 08:12:35 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.