Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2015-08-13 Thread Pierre Radermecker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pierre Radermecker commented on  PUP-1244 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum provider using "version-release" to validate installation.  
 
 
 
 
 
 
 
 
 
 
Is there a possibility to have a fix in 3.x ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2015-01-30 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1244 
 
 
 
  Yum provider using "version-release" to validate installation.  
 
 
 
 
 
 
 
 
 
 
Release tickets do not need to be testrailed. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Contact:
 
 Eric Thompson Kurt Wall 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-11-06 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-1244 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum provider using "version-release" to validate installation.  
 
 
 
 
 
 
 
 
 
 
Yeah there was a ton of review of this along the way. Resolving. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-09-11 Thread Jason Antman (JIRA)
Title: Message Title










 

 Jason Antman commented on an issue











 






  Re: Yum provider using "version-release" to validate installation. 










Thanks so much for making those fixes and getting this pushed through... I was without connectivity for most of yesterday afternoon/evening.












   

 Add Comment











 













 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 







 When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification.   {code}  $snmp_version = "5.3.2.2"  package { "net-snmp": ensure => "${snmp_version}"; }   Client output:   debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Changing ensur...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.googl

Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-07-25 Thread Joshua Partlow (JIRA)
Title: Message Title










 

 Joshua Partlow assigned an issue to Jason Antman











 







Found an error still, I think; notes in the PR.









 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Joshua Partlow




Assignee:

 Joshua Partlow Jason Antman












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-07-22 Thread Joshua Partlow (JIRA)
Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Joshua Partlow









 When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification.{code}$snmp_version = "5.3.2.2"package { "net-snmp": ensure => "${snmp_version}"; }  Client output:  debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Changing ensuredebug: //Node[client.example.com]/snmp::base/Package[net-snmp]: 1 change(s)debug: Package[net-snmp](provider=yum): Ensuring => 5.3.2.2**(1)** debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/yum -d 0 -e 0 -y install net-snmp-5.3.2.2'**(2)** debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q net-snmp --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}'err: //Node[client.example.com]/snmp::base/Package[net-snmp]/ensure: change from 5.3.2.2-7.el5_4.2 to 5.3.2.2 failed: Could not update: Failed to update to version 5.3.2.2, got version 5.3.2.2-7.el5_4.2 instead at /opt/git/development/modules/snmp/manifests/init.pp:26notice: //Node[client.example.com]/snmp::base/File[/etc/snmp/snmpd.conf]: Dependency package[net-snmp] has 1 failureswarning: //Node[labtest40-v3.ea-colo.ea.com]/snmp::base/File[/etc/snmp/snmpd.conf]: Skipping because of failed dependencies{code}The package is installed **(1)** but the error is still shown at the time of validation **(2)**, same situation if package is already installed.in .../provider/package/yum.rb:{code}def install chop lines ---is = self.queryunless israise Puppet::Error, "Could not find package %s" % self.nameend# FIXME: Should we raise an exception even if should == :latest# and yum updated us to a version other than @param_hash[:ensure] ?if should && should != is[:ensure]raise Puppet::Error, "Failed to update to version #{should}, got version #{is[:ensure]} instead"end{code}The error arises as **should** is not equal to **is[:ensure]**in .../provider/package/rpm.rb the query define comment says it will provide the **"version-release"**{code}# Find the fully versioned package name and the version alone. Returns# a hash with entries :instance => fully versioned package name, and# :ensure => version-releasedef query{code}The validation is made in the ensure attribute($snmp_version) string against "version-release" installed.  It makes sense when somebody defines something like ensure => "${snmp_version}-${snmp-release}", but not in this use case.Tested in 0.24.8 but reported also on 0.25.4.rpm.rb and yum.rb are not behaving in the same way as yum cli behaves.












   

 Add Comment
 

Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-07-21 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker assigned an issue to Joshua Partlow











 







I'm rolling off of the PR role and Joshua Partlow is rolling on. Assigning this to him so that he can finish it off. I've rebased and reworked the commits and pushed them up to https://github.com/zaphod42/puppet/tree/pr/2866. Joshua Partlow, I think you just need to run this through some exploratory tests and check that the unit test coverage looks good. After that a few notes about the change in the puppet 4 BREAKS.md doc would not go awry.









 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Andy Parker




Assignee:

 Andy Parker Joshua Partlow












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-07-17 Thread Jason Antman (JIRA)
Title: Message Title










 

 Jason Antman commented on an issue











 






  Re: Yum provider using "version-release" to validate installation. 










Cool, thanks Andy Parker!












   

 Add Comment











 













 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 







 When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification.   {code}  $snmp_version = "5.3.2.2"  package { "net-snmp": ensure => "${snmp_version}"; }Client output:debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Cha...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-07-16 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker assigned an issue to Andy Parker











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Andy Parker




Assignee:

 Jason Antman Andy Parker












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-07-16 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Andy Parker




Component/s:

 Community












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-07-11 Thread Jason Antman (JIRA)
Title: Message Title










 

 Jason Antman assigned an issue to Jason Antman











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Jason Antman




Assignee:

 Jason Antman












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-07-11 Thread Jason Antman (JIRA)
Title: Message Title










 

 Jason Antman commented on an issue











 






  Re: Yum provider using "version-release" to validate installation. 










I've rebase this on the puppet-4 branch and cut https://github.com/puppetlabs/puppet/pull/2866












   

 Add Comment











 













 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 







 When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification.   {code}  $snmp_version = "5.3.2.2"  package { "net-snmp": ensure => "${snmp_version}"; }Client output:debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Cha...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-07-10 Thread Jason Antman (JIRA)
Title: Message Title










 

 Jason Antman assigned an issue to Jason Antman











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Jason Antman




Assignee:

 Jason Antman












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-05-30 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Kylo Ginsberg




Fix Version/s:

 4.0.0












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-02-26 Thread Jose Luis Ledesma (JIRA)
Title: Message Title










 

 Jose Luis Ledesma commented on an issue











 






  Re: Yum provider using "version-release" to validate installation. 










I have found a problem trying to upgrade a package on rhel6. It seems could be related to this ticket:


cat libcgroup.pp package { 'libcgroup': ensure => '0.37-7.2.el6_4', }




rpm -q libcgroup libcgroup-0.37-7.el6.x86_64




puppet apply libcgroup.pp --no-noop --debug [... lots of messages... ] Debug: Package[libcgroup](provider=yum): Ensuring => 0.37-7.2.el6_4 Debug: Executing '/bin/rpm -q libcgroup --nosignature --nodigest --qf % {NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} :DESC: %{SUMMARY}\n' Debug: Package[libcgroup](provider=yum): Downgrading package libcgroup from version 0.37-7.el6 to 0.37-7.2.el6_4 Debug: Executing '/usr/bin/yum -d 0 -e 0 -y downgrade libcgroup-0.37-7.2.el6_4' Debug: Executing '/bin/rpm -q libcgroup --nosignature --nodigest --qf %{NAME}
 %|EPOCH?{%{EPOCH}}: {0}
| % {VERSION}
 % {RELEASE}
 % {ARCH}
 :DESC: % {SUMMARY}
\n' Error: Could not update: Failed to update to version 0.37-7.2.el6_4, got version 0.37-7.el6 instead Error: /Stage[main]/Main/Package[libcgroup]/ensure: change from 0.37-7.el6 to 0.37-7.2.el6_4 failed: Could not update: Failed to update to version 0.37-7.2.el6_4, got version 0.37-7.el6 instead


So it seems that puppet thinks that going from 0.37-7.el6 to 0.37-7.2.el6_4 is a downgrade (although some messages talks about an update) when in fact is an update so the yum command fails.












   

 Add Comment











 













 

Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-02-25 Thread Felix Frank (JIRA)
Title: Message Title










 

 Felix Frank updated an issue











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Felix Frank









 When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification.  {code} $snmp_version = "5.3.2.2"package { "net-snmp": ensure => "${snmp_version}"; }Client output:debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Changing ensuredebug: //Node[client.example.com]/snmp::base/Package[net-snmp]: 1 change(s)debug: Package[net-snmp](provider=yum): Ensuring => 5.3.2.2**(1)** debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/yum -d 0 -e 0 -y install net-snmp-5.3.2.2'**(2)** debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q net-snmp --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}'err: //Node[client.example.com]/snmp::base/Package[net-snmp]/ensure: change from 5.3.2.2-7.el5_4.2 to 5.3.2.2 failed: Could not update: Failed to update to version 5.3.2.2, got version 5.3.2.2-7.el5_4.2 instead at /opt/git/development/modules/snmp/manifests/init.pp:26notice: //Node[client.example.com]/snmp::base/File[/etc/snmp/snmpd.conf]: Dependency package[net-snmp] has 1 failureswarning: //Node[labtest40-v3.ea-colo.ea.com]/snmp::base/File[/etc/snmp/snmpd.conf]: Skipping because of failed dependencies  {code} The package is installed **(1)** but the error is still shown at the time of validation **(2)**, same situation if package is already installed.in .../provider/package/yum.rb:  {code} def install chop lines ---is = self.queryunless israise Puppet::Error, "Could not find package %s" % self.nameend# FIXME: Should we raise an exception even if should == :latest# and yum updated us to a version other than @param_hash[:ensure] ?if should && should != is[:ensure]raise Puppet::Error, "Failed to update to version #{should}, got version #{is[:ensure]} instead"end  {code} The error arises as **should** is not equal to **is[:ensure]**in .../provider/package/rpm.rb the query define comment says it will provide the **"version-release"**  {code} # Find the fully versioned package name and the version alone. Returns# a hash with entries :instance => fully versioned package name, and# :ensure => version-releasedef query  {code} The validation is made in the ensure attribute($snmp_version) string against "version-release" installed.  It makes sense when somebody defines something like ensure => "${snmp_version}-${snmp-release}", but not in this use case.Tested in 0.24.8 but reported also on 0.25.4.rpm.rb and yum.rb are not behaving in the same way as yum cli behaves.












   

 Add Comment
 

Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-01-11 Thread Jason Antman (JIRA)
Title: Message Title










 

 Jason Antman assigned an issue to Jason Antman











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Jason Antman




Assignee:

 Jason Antman












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-01-06 Thread Zachary Stern (JIRA)
Title: Message Title










 

 Zachary Stern updated an issue











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Zachary Stern




Labels:

 customer redmine yum












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-01-06 Thread Jason Antman (JIRA)
Title: Message Title










 

 Jason Antman commented on an issue











 






  Re: Yum provider using "version-release" to validate installation. 










This will apply to the rpm provider as well.
What we want to do is implement version comparison for RPMs (yum itself just passes this off to rpm libraries) the same way RPM does - specifically, to implement rpmvercmp (http://rpm.org/gitweb?p=rpm.git;a=blob;f=lib/rpmvercmp.c;h=b3d08faa4a31354d821cb259106b182410e452fb;hb=HEAD - rpm's tests for this are http://rpm.org/gitweb?p=rpm.git;a=blob;f=tests/rpmvercmp.at;h=2a25bdd9b53caa3f1d757ef5448523a2b06fdae4;hb=HEAD) in our code...












   

 Add Comment











 













 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 







 When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification. $snmp_version = "5.3.2.2"  package { "net-snmp": ensure => "${snmp_version}"; }Client output:debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Chan...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message 

Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-01-05 Thread Jason Antman (JIRA)
Title: Message Title










 

 Jason Antman commented on an issue











 






  Re: Yum provider using "version-release" to validate installation. 










I've started a branch with some unit tests that describe what I think the intended behavior is, as well as some of the current behavior: https://github.com/jantman/puppet/tree/PUP1244tests
I've also copied the current logic of Puppet::Util::Package.versioncmp to a yumversioncmp() method in the yum provider, as the generic (naive) version comparison done by the current versioncmp() is the problem here. There are probably also going to need to be some tweaks to the 'latest' logic. In light of PUP-682 and PUP-683, I'm going to see if I can dive into the yum/rpm source to figure out the details of version comparison before I do any more work.












   

 Add Comment











 













 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 







 When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification. $snmp_version = "5.3.2.2"  package { "net-snmp": ensure => "${snmp_version}"; }Client output:debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Chan...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 


   

Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-01-04 Thread Jason Antman (JIRA)
Title: Message Title










 

 Jason Antman commented on an issue











 






  Re: Yum provider using "version-release" to validate installation. 










From the man page for yum 3.2.29 on CentOS 6.4: """SPECIFYING PACKAGE NAMES A package can be referred to for install, update, remove, list, info etc with any of the following as well as globs of any of the following: name name.arch name-ver name-ver-rel name-ver-rel.arch name-epoch:ver-rel.arch epoch:name-ver-rel.arch """
what we seem to be concerned with is "ver" vs "ver-rel", and perhaps globs of those values (PUP-1365).












   

 Add Comment











 













 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 







 When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification. $snmp_version = "5.3.2.2"  package { "net-snmp": ensure => "${snmp_version}"; }Client output:debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Chan...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Pupp

Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-01-03 Thread Jo Rhett (JIRA)
Title: Message Title










 

 Jo Rhett commented on an issue











 






  Re: Yum provider using "version-release" to validate installation. 










I completely agree with Jason in pretty much every aspect. This should have been a high priority issue, but has been ignored for years.
IMHO it would best to come up with the right answer and make it an incompatible change at a given release target. Trying to make this work backwards compatible is very unlikely.












   

 Add Comment











 













 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 







 When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification. $snmp_version = "5.3.2.2"  package { "net-snmp": ensure => "${snmp_version}"; }Client output:debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Chan...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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+unsubs

Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-01-03 Thread Jason Antman (JIRA)
Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Attaching the full (and non-jira-parsed) output from debug runs










Change By:

 Jason Antman




Attachment:

 PUPPET-1244.txt












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-01-03 Thread Jason Antman (JIRA)
Title: Message Title










 

 Jason Antman commented on an issue











 






  Re: Yum provider using "version-release" to validate installation. 










This was opened 2010-04-12 against 0.24.8 and is still happening today with 3.4.1. I'd classify this as a high priority bug - what's reported by Puppet doesn't match what's actually being done, and even worse, on an initial run the package is actually installed even though the report says the resource failed, and on subsequent runs, the package is downgraded.
To be clear (see below), yum DOES install/upgrade the package (on every puppet run too), but REPORTS FAILURE as the post-yum-command version comparison fails.
I've attached the full --debug output of an example apply run, but what follows here are the important parts: ### [root@djaapafes7 ~]# puppet --version 3.3.2 [root@djaapafes7 ~]# /bin/rpm -q puppet --nosignature --nodigest --qf 'NAME: "% {NAME}" EPOCH: "%|EPOCH?{%{EPOCH}}:{0}|" VERSION: "%{VERSION}" RELEASE: "%{RELEASE}" ARCH: "%{ARCH}"\n' NAME: "puppet" EPOCH: "0" VERSION: "3.3.2" RELEASE: "1.el5" ARCH: "noarch" [root@djaapafes7 ~]# cat /home/jantman/temp/PUP1244.pp package {'puppet': ensure => '3.4.1' } [root@djaapafes7 ~]# puppet apply --debug /home/jantman/temp/PUP1244.pp ... Info: Applying configuration version '1388804396' Debug: Prefetching yum resources for package Debug: Executing '/bin/rpm --version' Debug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME}
 %|EPOCH?{%{EPOCH}}: {0}| %{VERSION} %{RELEASE} %{ARCH} :DESC: %{SUMMARY}\n'' Debug: Package[puppet](provider=yum): Ensuring => 3.4.1 Debug: Executing '/bin/rpm -q puppet --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}
| % {VERSION} %{RELEASE} %{ARCH} :DESC: %{SUMMARY}\n' Debug: Executing '/usr/bin/yum -d 0 -e 0 -y install puppet-3.4.1' Debug: Executing '/bin/rpm -q puppet --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION}
 % {RELEASE} %{ARCH} :DESC: %{SUMMARY}\n' Error: Could not update: Failed to update to version 3.4.1, got version 3.4.1-1.el5 instead Error: /Stage[main]//Package[puppet]/ensure: change from 3.3.2-1.el5 to 3.4.1 failed: Could not update: Failed to update to version 3.4.1, got version 3.4.1-1.el5 instead Debug: Finishing transaction 23456260688080 [root@djaapafes7 ~]# puppet --version 3.4.1 [root@djaapafes7 ~]# /bin/rpm -q puppet --nosignature --nodigest --qf 'NAME: "%{NAME}" EPOCH: "%|EPOCH?{%{EPOCH}}:{0}|" VERSION: "%{VERSION}" RELEASE: "%{RELEASE}
" ARCH: "% {ARCH}"\n' NAME: "puppet" EPOCH: "0" VERSION: "3.4.1" RELEASE: "1.el5" ARCH: "noarch"  ... and if we run it again...  [root@djaapafes7 ~]# puppet apply --debug /home/jantman/temp/PUP1244.pp ... Info: Applying configuration version '1388804480' Debug: Prefetching yum resources for package Debug: Executing '/bin/rpm --version' Debug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}
 :DESC: % {SUMMARY}\n'' Debug: Package[puppet](provider=yum): Ensuring => 3.4.1 Debug: Executing '/bin/rpm -q puppet --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} :DESC: %{SUMMARY}
\n' Debug: Package[puppet](provider=yum): Downgrading package puppet from version 3.4.1-1.el5 to 3.4.1 Debug: Executing '/usr/bin/yum -d 0 -e 0 -y downgrade puppet-3.4.1' Debug: Executing '/bin/rpm -q puppet --nosignature --nodigest --qf % {NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} :DESC: %{SUMMARY}\n' Error: Could not update: Failed to update to version 3.4.1, got version 3.4.1-1.el5 instead Error:

Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-01-03 Thread Jason Antman (JIRA)
Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Jason Antman




Component/s:

 Types and Providers




Labels:

 redmine  yum












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2013-12-26 Thread redmine.exporter (JIRA)
Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 26/Dec/13 3:08 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification.
 $snmp_version = "5.3.2.2" package { "net-snmp": ensure => "$ {snmp_version}"; }  Client output:  debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Changing ensure debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: 1 change(s) debug: Package[net-snmp](provider=yum): Ensuring => 5.3.2.2 *(1)* debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/yum -d 0 -e 0 -y install net-snmp-5.3.2.2' *(2)* debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q net-snmp --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} ' err: //Node[client.example.com]/snmp::base/Package[net-snmp]/ensure: change from 5.3.2.2-7.el5_4.2 to 5.3.2.2 failed: Could not update: Failed to update to version 5.3.2.2, got version 5.3.2.2-7.el5_4.2 instead at /opt/git/development/modules/snmp/manifests/init.pp:26 notice: //Node[client.example.com]/snmp::base/File[/etc/snmp/snmpd.conf]: Dependency package[net-snmp] has 1 failures warning: //Node[labtest40-v3.ea-colo.ea.com]/snmp::base/File[/etc/snmp/snmpd.conf]: Skipping because of failed dependencies   The package is installed *(1)* but the error is still shown at the time of validation *(2)*, same situation if package is already installed.  in .../provider/package/yum.rb:   def install  cho