Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo

2019-10-17 Thread Anthony Chevalet (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anthony Chevalet commented on  PUP-  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet::Type.type('yumrepo') wrongly reports enabled repo   
 

  
 
 
 
 

 
 Yes sure. It looks to occur only on registered systems where rhsmcertd is running. I will try to reproduce with puppet 5 and reopen if needed. Thank you.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323658.1567695504000.4970.1571316180197%40Atlassian.JIRA.


Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo

2019-10-14 Thread Anthony Chevalet (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anthony Chevalet commented on  PUP-  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet::Type.type('yumrepo') wrongly reports enabled repo   
 

  
 
 
 
 

 
 Well I'm still not able to reproduce in test environment even with 4.10.12.. I see it only in production environment (randomly)..  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323658.1567695504000.141558.1571052660252%40Atlassian.JIRA.


Jira (PUP-7734) puppet.conf bad environment setting breaks ENC correct environment setting

2019-10-10 Thread Anthony Chevalet (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anthony Chevalet commented on  PUP-7734  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet.conf bad environment setting breaks ENC correct environment setting   
 

  
 
 
 
 

 
 Any update?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.197952.1498577662000.137796.1570712280192%40Atlassian.JIRA.


Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo

2019-09-05 Thread Anthony Chevalet (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anthony Chevalet updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-  
 
 
  Puppet::Type.type('yumrepo') wrongly reports enabled repo   
 

  
 
 
 
 

 
Change By: 
 Anthony Chevalet  
 

  
 
 
 
 

 
 *Puppet Version: 4.10.12* *Puppet Server Version: 2.8.1* *OS Name/Version: CentOS Linux release 7.6.1810*I have weird behavior which occurs randomly where Puppet::Type.type('yumrepo') reports that a yum repo is enabled despite it is not.I'm using this fact:{noformat}  require 'puppet'  def to_boolean(value)  %w[absent yes true 1].include?(value.downcase) endFacter endFacter .add('enabled_repos') do  setcode dorepos = []Puppet::Type.type('yumrepo').instances.find_all do |repo|  repo_value = repo.retrieve  repos << repo.name if to_boolean(repo_value[repo.property(:enabled)].to_s.strip)endrepos.sort  endend{noformat}I have a repo defined with enbled=0, ex: myrepoI run this loop to reproduce: {noformat}( date; while :; do facter -p enabled_repos | grep -i myrepo && date && break; sleep 1; done ; yum repolist ) >enabled-repo.tmp 2>&1 &{noformat}After few days I get:{noformat}Mon Sep  2 03:48:12 UTC 2019  "myrepo",Thu Sep  5 16:09:28 UTC 2019Loaded plugins: enabled_repos_upload, fastestmirror, langpacks, package_upload, product-id, search-  : disabled-repos, subscription-manager, tracer_upload, versionlockLoading mirror speeds from cached hostfilerepo id repo name status!Centos_Centos_7_Base Centos_7 Base 10,019!Centos_Centos_7_Extras Centos 7 Extras 435!Centos_Centos_7_Opstools Centos 7 Opstools 896!Centos_Centos_7_Updates Centos 7 Updates 4,067!Centos_Centos_7_kvm-common Centos 7 kvm-common 79!Centos_Centos_7_ovirt Centos 7 ovirt 744!Centos_Centos_sclo Centos sclo 786!Centos_Centos_sclo-rh Centos sclo-rh 8,444repolist: 25,470Uploading Enabled Repositories ReportLoaded plugins: fastestmirror, langpacks, product-id, subscription-manager,  : versionlock{noformat}myrepo is included in the fact enabled_repos but it is not enabled on the system.*Desired Behavior:*myrepo is not included in the fact enabled_repos. Only repos with enable=1 should be included.*Actual Behavior:*myrepo is included in the fact enabled_repos but it is not enabled on the system.I'm using foreman with katello plugin and yum subscriptions.  
 

  
 
 
 
 

 
 
 

Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo

2019-09-05 Thread Anthony Chevalet (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anthony Chevalet updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-  
 
 
  Puppet::Type.type('yumrepo') wrongly reports enabled repo   
 

  
 
 
 
 

 
Change By: 
 Anthony Chevalet  
 

  
 
 
 
 

 
 *Puppet Version: 4.10.12* *Puppet Server Version: 2.8.1* *OS Name/Version: CentOS Linux release 7.6.1810*I have weird behavior which occurs randomly where Puppet::Type.type('yumrepo') reports that a yum repo is enabled despite it is not.I'm using this fact :    {noformat}require 'puppet'def to_boolean(value)  %w[absent yes true 1].include?(value.downcase)endFacter.add('enabled_repos') do  setcode dorepos = []Puppet::Type.type('yumrepo').instances.find_all do |repo|  repo_value = repo.retrieve  repos << repo.name if to_boolean(repo_value[repo.property(:enabled)].to_s.strip)endrepos.sort  endend  {noformat}I have a repo defined with enbled=0, ex: myrepo   I run this loop to reproduce:   {noformat}( date; while :; do facter -p enabled_repos | grep -i myrepo && date && break; sleep 1; done ; yum repolist ) >enabled-repo.tmp 2>&1 &{noformat}After few days I get:    {noformat}Mon Sep  2 03:48:12 UTC 2019  "myrepo",Thu Sep  5 16:09:28 UTC 2019Loaded plugins: enabled_repos_upload, fastestmirror, langpacks, package_upload, product-id, search-  : disabled-repos, subscription-manager, tracer_upload, versionlockLoading mirror speeds from cached hostfilerepo id repo name status!Centos_Centos_7_Base Centos_7 Base 10,019!Centos_Centos_7_Extras Centos 7 Extras 435!Centos_Centos_7_Opstools Centos 7 Opstools 896!Centos_Centos_7_Updates Centos 7 Updates 4,067!Centos_Centos_7_kvm-common Centos 7 kvm-common 79!Centos_Centos_7_ovirt Centos 7 ovirt 744!Centos_Centos_sclo Centos sclo 786!Centos_Centos_sclo-rh Centos sclo-rh 8,444repolist: 25,470Uploading Enabled Repositories ReportLoaded plugins: fastestmirror, langpacks, product-id, subscription-manager,  : versionlock{noformat}myrepo is included in the fact enabled_repos but it is not enabled on the system.   *Desired Behavior:*myrepo is not included in the fact enabled_repos. Only repos with enable=1 should be included.*Actual Behavior:*myrepo is included in the fact enabled_repos but it is not enabled on the system.I'm using foreman with katello plugin and yum subscriptions.    
 

  
 
 
 
 

 
 

Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo

2019-09-05 Thread Anthony Chevalet (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anthony Chevalet updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-  
 
 
  Puppet::Type.type('yumrepo') wrongly reports enabled repo   
 

  
 
 
 
 

 
Change By: 
 Anthony Chevalet  
 

  
 
 
 
 

 
 *Puppet Version: 4.10.12* *Puppet Server Version: 2.8.1* *OS Name/Version: CentOS Linux release 7.6.1810*I have weird behavior which occurs randomly where Puppet::Type.type('yumrepo') reports that a yum repo is enabled despite it is not. I'm using this fact {noformat}  require 'puppet'def to_boolean(value)  %w[absent yes true 1].include?(value.downcase)endFacter.add('enabled_repos') do  setcode dorepos = []Puppet::Type.type('yumrepo').instances.find_all do |repo|  repo_value = repo.retrieve  repos << repo.name if to_boolean(repo_value[repo.property(:enabled)].to_s.strip)endrepos.sort  endend{noformat}I have a repo defined with enbled=0, ex: myrepo I run this loop to reproduce: {noformat}  ( date; while :; do facter -p enabled_repos | grep -i myrepo && date && break; sleep 1; done ; yum repolist ) >enabled-repo.tmp 2>&1 &{noformat}After few days I get:  {noformat}  Mon Sep  2 03:48:12 UTC 2019  "myrepo",Thu Sep  5 16:09:28 UTC 2019Loaded plugins: enabled_repos_upload, fastestmirror, langpacks, package_upload, product-id, search-  : disabled-repos, subscription-manager, tracer_upload, versionlockLoading mirror speeds from cached hostfilerepo id repo name status!Centos_Centos_7_Base Centos_7 Base 10,019!Centos_Centos_7_Extras Centos 7 Extras 435!Centos_Centos_7_Opstools Centos 7 Opstools 896!Centos_Centos_7_Updates Centos 7 Updates 4,067!Centos_Centos_7_kvm-common Centos 7 kvm-common 79!Centos_Centos_7_ovirt Centos 7 ovirt 744!Centos_Centos_sclo Centos sclo 786!Centos_Centos_sclo-rh Centos sclo-rh 8,444repolist: 25,470Uploading Enabled Repositories ReportLoaded plugins: fastestmirror, langpacks, product-id, subscription-manager,  : versionlock{noformat}myrepo is included in the fact enabled_repos but it is not enabled on the system. *Desired Behavior:*myrepo is not included in the fact enabled_repos. Only repos with enable=1 should be included.*Actual Behavior:*myrepo is included in the fact enabled_repos but it is not enabled on the system. I'm using foreman with katello plugin and yum subscriptions.    
 

  
 
 
 
 

 
 
   

Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo

2019-09-05 Thread Anthony Chevalet (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anthony Chevalet created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-  
 
 
  Puppet::Type.type('yumrepo') wrongly reports enabled repo   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 4.10.12  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Types and Providers  
 
 
Created: 
 2019/09/05 7:58 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Anthony Chevalet  
 

  
 
 
 
 

 
 Puppet Version: 4.10.12 Puppet Server Version: 2.8.1 OS Name/Version: CentOS Linux release 7.6.1810 I have weird behavior which occurs randomly where Puppet::Type.type('yumrepo') reports that a yum repo is enabled despite it is not.  I'm using this fact    
 
 
 
 
 require 'puppet'def to_boolean(value)  
 
 
   %w[absent yes true 1].include?(value.downcase)  
 
 
 endFacter.add('enabled_repos') do  
 
 
   setcode do  
 
 

Jira (PUP-7813) Yum package provider: ensure => latest fails when packages update available

2017-08-16 Thread Anthony Chevalet (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Chevalet commented on  PUP-7813 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum package provider: ensure => latest fails when packages update available  
 
 
 
 
 
 
 
 
 
 
As per Eric comments at http://projects.theforeman.org/issues/20567, the enabled_repos_upload plugin has a valid output that puppet does not handle: 
 
 
 
 
 
 
Uploading Enabled Reposistories Report 
 
 
 
 
Loaded plugins: fastestmirror, product-id 
 
 
 
 
Cannot upload enabled repos report, is this client registered?
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For 

Jira (PUP-7813) Yum package provider: ensure => latest fails when packages update available

2017-08-11 Thread Anthony Chevalet (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Chevalet commented on  PUP-7813 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum package provider: ensure => latest fails when packages update available  
 
 
 
 
 
 
 
 
 
 
Bug reported on katello-agent: http://projects.theforeman.org/issues/20567 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7813) Yum package provider: ensure => latest fails when packages update available

2017-08-11 Thread Anthony Chevalet (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Chevalet commented on  PUP-7813 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum package provider: ensure => latest fails when packages update available  
 
 
 
 
 
 
 
 
 
 
The culprit is the enabled_repos_upload yum plugin: 
 
 
 
 
 
 
d-infra-mgt.cfc.ks.net 15:56:48 ~ # puppet resource  package kernel ensure=latest 
 
 
 
 
Error: Could not get latest version: undefined method `[]' for nil:NilClass 
 
 
 
 
Error: /Package[kernel]/ensure: change from 3.10.0-514.10.2.el7 to latest failed: Could not get latest version: undefined method `[]' for nil:NilClass 
 
 
 
 
package { 'kernel': 
 
 
 
 
  ensure => '3.10.0-514.10.2.el7', 
 
 
 
 
} 
 
 
 
 
d-infra-mgt.cfc.ks.net 15:56:57 ~ #  
 
 
 
 
d-infra-mgt.cfc.ks.net 15:56:57 ~ # sed -i 's:enabled=1:enabled=0:g' /etc/yum/pluginconf.d/enabled_repos_upload.conf 
 
 
 
 
d-infra-mgt.cfc.ks.net 15:57:04 ~ # puppet resource  package kernel ensure=latest 
 
 
 
 

Jira (PUP-7813) Yum package provider: ensure => latest fails when packages update available

2017-08-10 Thread Anthony Chevalet (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Chevalet commented on  PUP-7813 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum package provider: ensure => latest fails when packages update available  
 
 
 
 
 
 
 
 
 
 
Looks like it is linked to python2-boto available in the EPEL repo: {{[root@t-puppet4-03 ~]# puppet resource package python2-boto package  { 'python2-boto': ensure => 'purged', } 
[root@t-puppet4-03 ~]# puppet resource package python2-boto ensure=latest Notice: /Package[python2-boto]/ensure: created package  { 'python2-boto': ensure => '2.45.0-3.el7', } 
[root@t-puppet4-03 ~]# puppet resource package python2-boto ensure=latest Error: Could not get latest version: undefined method `[]' for nil:NilClass Error: /Package[python2-boto]/ensure: change from 2.45.0-3.el7 to latest failed: Could not get latest version: undefined method `[]' for nil:NilClass package  { 'python2-boto': ensure => '2.45.0-3.el7', } 
}} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7813) Yum package provider: ensure => latest fails when packages update available

2017-08-03 Thread Anthony Chevalet (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Chevalet commented on  PUP-7813 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum package provider: ensure => latest fails when packages update available  
 
 
 
 
 
 
 
 
 
 
Hi Josh Cooper, here it is: 
 
 
 
 
 
 
p-infra-katello.ks.net 12:11:46 ~ # puppet --version 
 
 
 
 
4.10.5 
 
 
 
 
p-infra-katello.ks.net 12:11:48 ~ # puppet resource package kernel  
 
 
 
 
package { 'kernel': 
 
 
 
 
  ensure => '3.10.0-514.21.2.el7', 
 
 
 
 
} 
 
 
 
 
p-infra-katello.ks.net 12:11:55 ~ # puppet resource package kernel ensure=latest --trace 
 
 
 
 
Error: Could not get latest version: undefined method `[]' for nil:NilClass 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/yum.rb:112:in `update_to_hash' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/yum.rb:95:in `block in parse_updates' 
  

Jira (PUP-7813) Yum package provider: ensure => latest fails when packages update available

2017-08-02 Thread Anthony Chevalet (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Chevalet updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7813 
 
 
 
  Yum package provider: ensure => latest fails when packages update available  
 
 
 
 
 
 
 
 
 

Change By:
 
 Anthony Chevalet 
 
 
 
 
 
 
 
 
 
 If one package is listed in the output of 'yum check-update', any package update fails.{noformat}# puppet resource package kernel ensure=latestError: Could not get latest version: undefined method `[]' for nil:NilClassError: /Package[kernel]/ensure: change from 3.10.0-514.26.2.el7 to latest failed: Could not get latest version: undefined method `[]' for nil:NilClasspackage { 'kernel':  ensure => '3.10.0-514.26.2.el7',}{noformat}{noformat}# /bin/yum check-updateLoaded plugins: enabled_repos_upload, fastestmirror, package_upload, product-id, search-disabled-repos, subscription-  : manager, tracer_uploadKS_Centos_Centos_7_Base   | 2.1 kB  00:00:00  KS_Centos_Centos_7_Extras | 2.5 kB  00:00:00  KS_Centos_Centos_7_Updates| 2.5 kB  00:00:00  KS_Centos_Centos_sclo | 2.1 kB  00:00:00 KS_Centos_Centos_sclo-rh  | 2.1 kB  00:00:00 KS_Datadog_Datadog| 1.8 kB  00:00:00 KS_EPEL_EPEL_Centos7  | 2.1 kB  00:00:00 KS_Extra_rpm-extra| 2.1 kB  00:00:00 KS_Foreman_Foreman-1_15   | 2.1 kB  00:00:00 KS_Foreman_Foreman-1_15-plugins   | 2.1 kB  00:00:00 KS_Katello-agent_agent-3_4| 2.1 kB  00:00:00 KS_Katello_Candlepin_3_4  | 2.1 kB  00:00:00 KS_Katello_Pulp_3_4   | 2.1 kB  00:00:00  KS_Katello_Server_3_4 | 2.1 kB  00:00:00  KS_Puppet_puppet_4| 1.8 kB  00:00:00 KS_Zabbix_Zabbix_3_2  | 1.8 kB  00:00:00 KS_rsyslog_rsyslog| 1.8 kB  00:00:00  Loading mirror speeds from cached hostfileforeman-installer-katello.noarch  3.4.4-1.el7   KS_Katello_Server_3_4katello-debug.noarch  3.4.4-2.el7   KS_Katello_Server_3_4katello-installer-base.noarch 3.4.4-1.el7   KS_Katello_Server_3_4katello-service.noarch3.4.4-2.el7   

Jira (PUP-7813) Yum package provider: ensure => latest fails when packages update available

2017-08-02 Thread Anthony Chevalet (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Chevalet updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7813 
 
 
 
  Yum package provider: ensure => latest fails when packages update available  
 
 
 
 
 
 
 
 
 

Change By:
 
 Anthony Chevalet 
 
 
 
 
 
 
 
 
 
 If one package is listed in the output of 'yum check-update', any package update fails.{noformat}# puppet resource package kernel ensure=latest {color:red} Error: Could not get latest version: undefined method `[]' for nil:NilClassError: /Package[kernel]/ensure: change from 3.10.0-514.26.2.el7 to latest failed: Could not get latest version: undefined method `[]' for nil:NilClass {color} package { 'kernel':  ensure => '3.10.0-514.26.2.el7',}{noformat}{noformat}# /bin/yum check-updateLoaded plugins: enabled_repos_upload, fastestmirror, package_upload, product-id, search-disabled-repos, subscription-  : manager, tracer_uploadKS_Centos_Centos_7_Base   | 2.1 kB  00:00:00 KS_Centos_Centos_7_Extras | 2.5 kB  00:00:00 KS_Centos_Centos_7_Updates| 2.5 kB  00:00:00 KS_Centos_Centos_sclo | 2.1 kB  00:00:00 KS_Centos_Centos_sclo-rh  | 2.1 kB  00:00:00 KS_Datadog_Datadog| 1.8 kB  00:00:00 KS_EPEL_EPEL_Centos7  | 2.1 kB  00:00:00 KS_Extra_rpm-extra| 2.1 kB  00:00:00 KS_Foreman_Foreman-1_15   | 2.1 kB  00:00:00 KS_Foreman_Foreman-1_15-plugins   | 2.1 kB  00:00:00 KS_Katello-agent_agent-3_4| 2.1 kB  00:00:00 KS_Katello_Candlepin_3_4  | 2.1 kB  00:00:00 KS_Katello_Pulp_3_4   | 2.1 kB  00:00:00 KS_Katello_Server_3_4 | 2.1 kB  00:00:00 KS_Puppet_puppet_4| 1.8 kB  00:00:00 KS_Zabbix_Zabbix_3_2  | 1.8 kB  00:00:00 KS_rsyslog_rsyslog| 1.8 kB  00:00:00 Loading mirror speeds from cached hostfileforeman-installer-katello.noarch  3.4.4-1.el7   KS_Katello_Server_3_4katello-debug.noarch  3.4.4-2.el7   KS_Katello_Server_3_4katello-installer-base.noarch 3.4.4-1.el7   KS_Katello_Server_3_4katello-service.noarch3.4.4-2.el7   

Jira (PUP-7813) Yum package provider: ensure => latest fails when packages update available

2017-08-02 Thread Anthony Chevalet (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Chevalet created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7813 
 
 
 
  Yum package provider: ensure => latest fails when packages update available  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.10.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/02 10:24 AM 
 
 
 

Environment:
 
 
CentOS Linux release 7.3.1611 (3.10.0-514.26.2.el7.x86_64) puppet-agent-1.10.5-1.el7.x86_64 
 
 
 

Labels:
 

 puppet-agent 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Anthony Chevalet 
 
 
 
 
 
 
 
 
 
 
If one package is listed in the output of 'yum check-update', any package update fails. 
 
 
 
 
 
 
# puppet resource package kernel ensure=latest