I have a (what I thought was) simple class for getting maven installed on a new dev workstation: class maven { file { "/tmp/et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm": ensure => present, mode => 755, source => "puppet:///maven/ et_p6_sunjdk15-1.5.0.11-5.centos5.i386rpm", } package {"et_p6_sunjdk15": ensure => installed, provider => rpm, source => File["/tmp/ et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm"], } file { "/tmp/et_p6_maven-2.0.90.3-3.noarch.rpm": ensure => present, mode => 755, source => "puppet:///maven/ et_p6_maven-2.0.90.3-3.noarch.rpm", } package { "et_p6_maven": ensure => installed, provider => rpm, require => Package["et_p6_sunjdk15"], source => File["/tmp/ et_p6_maven-2.0.90.3-3.noarch.rpm"], } } Here''s the relevant output from a --debug --test on the puppet client: debug: Puppet::Type::Package::ProviderRpm: Executing ''/bin/rpm -i -- oldpackage file /tmp/et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm'' err: //Node[p8]/p8class/maven/Package[et_p6_sunjdk15]/ensure: change from absent to present failed: Execution of ''/bin/rpm -i --oldpackage file /tmp/et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm'' returned 256: error: open of file failed: No such file or directory notice: //Node[p8]/p8class/maven/Package[et_p6_maven]: Dependency package[et_p6_sunjdk15] has 1 failures warning: //Node[p8]/p8class/maven/Package[et_p6_maven]: Skipping because of failed dependencies BUT the files do exist: [jleggett@lxp6d15m3 modules]$ ls -l /tmp/et_* -rwxr-xr-x 1 jleggett etrade 3022508 Jun 9 09:13 /tmp/ et_p6_maven-2.0.90.3-3.noarch.rpm -rwxr-xr-x 1 jleggett etrade 66051511 Jun 9 09:26 /tmp/ et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm [jleggett@lxp6d15m3 modules]$ And a manual run of the cmd puppet runs givs same error: [jleggett@lxp6d15m3 modules]$ /bin/rpm -i --oldpackage file /tmp/ et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm error: open of file failed: No such file or directory [jleggett@lxp6d15m3 modules]$ but a rpm -Uvh installs it?!?! [jleggett@lxp6d15m3 modules]$ sudo rpm -Uvh /tmp/ et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm Preparing... ########################################### [100%] 1:et_p6_sunjdk15 ########################################### [100%] [jleggett@lxp6d15m3 modules]$ So now, after manually adding the sunjsk to the box, with rpm -Uvh, now the maven package gives the same problem: debug: Puppet::Type::Package::ProviderRpm: Executing ''/bin/rpm -i -- oldpackage file /tmp/et_p6_maven-2.0.90.3-3.noarch.rpm'' err: //Node[p8]/p8class/maven/Package[et_p6_maven]/ensure: change from absent to present failed: Execution of ''/bin/rpm -i --oldpackage file / tmp/et_p6_maven-2.0.90.3-3.noarch.rpm'' returned 256: error: open of file failed: No such file or directory any ideas? This doesn''t seem it should be this complicated for something this straightforward. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Mon, 2008-06-09 at 09:43 -0700, Jeff Leggett wrote:> I have a (what I thought was) simple class for getting maven installed > on a new dev workstation: > > class maven { > file { "/tmp/et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm": > ensure => present, > mode => 755, > source => "puppet:///maven/ > et_p6_sunjdk15-1.5.0.11-5.centos5.i386rpm", > }Is this a typo ? Note how there''s np ''.'' in ''i386rpm''. Also, using the puppet protocol for transferring large files is very seriously not recommended.> package {"et_p6_sunjdk15": > ensure => installed, > provider => rpm, > source => File["/tmp/ > et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm"], > }What you want is package {"et_p6_sunjdk15": ensure => installed, provider => rpm, source => "/tmp/et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm", require => File["/tmp/et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm"], } Note that the argument to ''source'' must be just a string; to say that the file statement should be evaluated before the corresponding package statement, you need to add the ''require'' attribute. Puppet should really throw an error here, because you useda resource where a string is expected, but I am not sure how easy/hard that would be to actually implement. David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
O> > I have a (what I thought was) simple class for getting maven installed > on a new dev workstation: > > class maven { > file { "/tmp/et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm": > ensure => present, > mode => 755, > source => "puppet:///maven/ > et_p6_sunjdk15-1.5.0.11-5.centos5.i386rpm", > } > package {"et_p6_sunjdk15": > ensure => installed, > provider => rpm, > source => File["/tmp/ > et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm"], > } > file { "/tmp/et_p6_maven-2.0.90.3-3.noarch.rpm": > ensure => present, > mode => 755, > source => "puppet:///maven/ > et_p6_maven-2.0.90.3-3.noarch.rpm", > } > > package { "et_p6_maven": > ensure => installed, > provider => rpm, > require => Package["et_p6_sunjdk15"], > source => File["/tmp/ > et_p6_maven-2.0.90.3-3.noarch.rpm"], > } > } >This would make alot more since to put in a private repo and use the default yum provider. That way yum handles the dependence tree and the downloading to the client. This will also make updating the rpm a lot easier in the future. Update the repo and when puppet calls yum it sees the update and away it goes.> > any ideas? This doesn''t seem it should be this complicated for > something this straightforward. >Let your tools do the heavy lifting. Between this email and a few of your others, it looks to me like you are trying to use directly manipulate every thing with puppet is stead of abstracting it out so that puppet can work it''s magic, let you not worry about the details. Evan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Also, is there a limit on filesize for puppet? I get this when it tries to d/l the sunjdk RPM: debug: //Node[p8]/p8class/maven/File[/tmp/ et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm]: File does not exist debug: Calling fileserver.describe debug: //Node[p8]/p8class/maven/File[/tmp/ et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm]: Changing ensure debug: //Node[p8]/p8class/maven/File[/tmp/ et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm]: 1 change(s) debug: Calling fileserver.retrieve debug: Storing state debug: Stored state in 0.03 seconds /usr/lib/ruby/1.8/timeout.rb:54:in `rbuf_fill'': execution expired (Timeout::Error) from /usr/lib/ruby/1.8/timeout.rb:56:in `timeout'' from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout'' from /usr/lib/ruby/1.8/net/protocol.rb:132:in `rbuf_fill'' from /usr/lib/ruby/1.8/net/protocol.rb:116:in `readuntil'' from /usr/lib/ruby/1.8/net/protocol.rb:126:in `readline'' from /usr/lib/ruby/1.8/net/http.rb:2020:in `read_status_line'' from /usr/lib/ruby/1.8/net/http.rb:2009:in `read_new'' from /usr/lib/ruby/1.8/net/http.rb:1050:in `request'' ... 44 levels... from /usr/lib/ruby/site_ruby/1.8/puppet/network/client/ master.rb:263:in `run'' from /usr/lib/ruby/1.8/sync.rb:229:in `synchronize'' from /usr/lib/ruby/site_ruby/1.8/puppet/network/client/ master.rb:245:in `run'' from /usr/sbin/puppetd:439 [jleggett@lxp6d15m3 modules]$ On Jun 9, 12:43 pm, Jeff Leggett <jeffrey.legg...@etrade.com> wrote:> I have a (what I thought was) simple class for getting maven installed > on a new dev workstation: > > class maven { > file { "/tmp/et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm": > ensure => present, > mode => 755, > source => "puppet:///maven/ > et_p6_sunjdk15-1.5.0.11-5.centos5.i386rpm", > } > package {"et_p6_sunjdk15": > ensure => installed, > provider => rpm, > source => File["/tmp/ > et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm"], > } > file { "/tmp/et_p6_maven-2.0.90.3-3.noarch.rpm": > ensure => present, > mode => 755, > source => "puppet:///maven/ > et_p6_maven-2.0.90.3-3.noarch.rpm", > } > > package { "et_p6_maven": > ensure => installed, > provider => rpm, > require => Package["et_p6_sunjdk15"], > source => File["/tmp/ > et_p6_maven-2.0.90.3-3.noarch.rpm"], > } > > } > > Here''s the relevant output from a --debug --test on the puppet > client: > > debug: Puppet::Type::Package::ProviderRpm: Executing ''/bin/rpm -i -- > oldpackage file /tmp/et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm'' > err: //Node[p8]/p8class/maven/Package[et_p6_sunjdk15]/ensure: change > from absent to present failed: Execution of ''/bin/rpm -i --oldpackage > file /tmp/et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm'' returned 256: > error: open of file failed: No such file or directory > > notice: //Node[p8]/p8class/maven/Package[et_p6_maven]: Dependency > package[et_p6_sunjdk15] has 1 failures > warning: //Node[p8]/p8class/maven/Package[et_p6_maven]: Skipping > because of failed dependencies > > BUT the files do exist: > > [jleggett@lxp6d15m3 modules]$ ls -l /tmp/et_* > -rwxr-xr-x 1 jleggett etrade 3022508 Jun 9 09:13 /tmp/ > et_p6_maven-2.0.90.3-3.noarch.rpm > -rwxr-xr-x 1 jleggett etrade 66051511 Jun 9 09:26 /tmp/ > et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm > [jleggett@lxp6d15m3 modules]$ > > And a manual run of the cmd puppet runs givs same error: > > [jleggett@lxp6d15m3 modules]$ /bin/rpm -i --oldpackage file /tmp/ > et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm > error: open of file failed: No such file or directory > [jleggett@lxp6d15m3 modules]$ > > but a rpm -Uvh installs it?!?! > > [jleggett@lxp6d15m3 modules]$ sudo rpm -Uvh /tmp/ > et_p6_sunjdk15-1.5.0.11-5.centos5.i386.rpm > Preparing... > ########################################### [100%] > 1:et_p6_sunjdk15 > ########################################### [100%] > [jleggett@lxp6d15m3 modules]$ > > So now, after manually adding the sunjsk to the box, with rpm -Uvh, > now the maven package gives the same problem: > > debug: Puppet::Type::Package::ProviderRpm: Executing ''/bin/rpm -i -- > oldpackage file /tmp/et_p6_maven-2.0.90.3-3.noarch.rpm'' > err: //Node[p8]/p8class/maven/Package[et_p6_maven]/ensure: change from > absent to present failed: Execution of ''/bin/rpm -i --oldpackage file / > tmp/et_p6_maven-2.0.90.3-3.noarch.rpm'' returned 256: error: open of > file failed: No such file or directory > > any ideas? This doesn''t seem it should be this complicated for > something this straightforward.--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hi> Also, is there a limit on filesize for puppet? I get this when it > tries to d/l the sunjdk RPM:no but until puppet didn''t change to REST, you will hit problems like these by serving a lot or huge file. As other already mentioned you better setup your own repo. greets Pete --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Jun 9, 1:08 pm, "Evan Hisey" <ehi...@gmail.com> wrote: Let your tools do the heavy lifting. Between this email and a few of> your others, it looks to me like you are trying to use directly > manipulate every thing with puppet is stead of abstracting it out so > that puppet can work it''s magic, let you not worry about the details.That might very well be? Can you better explain what you mean by that to me so I can? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On 09/06/2008, Jeff Leggett <jeffrey.leggett@etrade.com> wrote:> > On Jun 9, 1:08 pm, "Evan Hisey" <ehi...@gmail.com> wrote: > Let your tools do the heavy lifting. Between this email and a few of > > your others, it looks to me like you are trying to use directly > > manipulate every thing with puppet is stead of abstracting it out so > > that puppet can work it''s magic, let you not worry about the details. > > > That might very well be? Can you better explain what you mean by that > to me so I can? >I think the general idea here is you''re making alot of work for yourself here. Instead of pulling packages down with puppet then explicitly calling them to be installed, just create a yum repository, use puppet to ensure that repository is included on the machine, and just use the yum provider. If you''re tied to using RPM rather than yum (not recommended, rpm doesn''t resolve dependencies, yum does), atleast make use of its ability to pull from a URL and setup a webserver to host your RPMs so you''re not pulling them with puppet to the local system. .r'' --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
OH - of course, yes. That is the plan, but I am trying to get setup for a puppet demo tomorrow internally and haven''t gotten those added to the yum repo yet.. .that is the plan long term of course. On Jun 9, 1:53 pm, RijilV <rij...@gmail.com> wrote:> On 09/06/2008, Jeff Leggett <jeffrey.legg...@etrade.com> wrote: > > > > > On Jun 9, 1:08 pm, "Evan Hisey" <ehi...@gmail.com> wrote: > > Let your tools do the heavy lifting. Between this email and a few of > > > your others, it looks to me like you are trying to use directly > > > manipulate every thing with puppet is stead of abstracting it out so > > > that puppet can work it''s magic, let you not worry about the details. > > > That might very well be? Can you better explain what you mean by that > > to me so I can? > > I think the general idea here is you''re making alot of work for > yourself here. Instead of pulling packages down with puppet then > explicitly calling them to be installed, just create a yum repository, > use puppet to ensure that repository is included on the machine, and > just use the yum provider. > > If you''re tied to using RPM rather than yum (not recommended, rpm > doesn''t resolve dependencies, yum does), atleast make use of its > ability to pull from a URL and setup a webserver to host your RPMs so > you''re not pulling them with puppet to the local system. > > .r''--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
OK, so I rewrote the maven.pp file as follows: class maven { yumrepo { "p6.rhas5.x86": name => "p6-RHAS5-x86", enabled => 1, baseurl => "http://yum.etrade.com/p6.rhas5.x86/", } package {"et_p6_sunjdk15": ensure => installed, provider => yum, require => Yumrepo["p6.rhas5.x86"], } package { "et_p6_maven": ensure => installed, provider => yum, require => Package["et_p6_sunjdk15"], } } Now the --test output says: err: Could not prefetch package provider ''yum'': Execution of ''/usr/bin/ python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ yumhelper.py'' returned 256: Loading "rhnplugin" plugin Loading "installonlyn" plugin Repository ''p6-RHAS5-x86'' is missing name in configuration, using id This system is not registered with RHN. RHN support will be disabled. Traceback (most recent call last): File "/usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ yumhelper.py", line 32, in ? ypl = pkg_lists(my) File "/usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ yumhelper.py", line 27, in pkg_lists return my.doPackageLists(''updates'') File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 988, in doPackageLists self.doRepoSetup() File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 299, in doRepoSetup repo.setup(self.conf.cache) File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 505, in setup raise Errors.RepoError, (''Cannot open/read repomd.xml file for repository: %s'' % self) yum.Errors.RepoError: Cannot open/read repomd.xml file for repository: p6-RHAS5-x86 What''d I do now? On Jun 9, 2:14 pm, Jeff Leggett <jeffrey.legg...@etrade.com> wrote:> OH - of course, yes. That is the plan, but I am trying to get setup > for a puppet demo tomorrow internally and haven''t gotten those added > to the yum repo yet.. .that is the plan long term of course. > > On Jun 9, 1:53 pm, RijilV <rij...@gmail.com> wrote: > > > On 09/06/2008, Jeff Leggett <jeffrey.legg...@etrade.com> wrote: > > > > On Jun 9, 1:08 pm, "Evan Hisey" <ehi...@gmail.com> wrote: > > > Let your tools do the heavy lifting. Between this email and a few of > > > > your others, it looks to me like you are trying to use directly > > > > manipulate every thing with puppet is stead of abstracting it out so > > > > that puppet can work it''s magic, let you not worry about the details. > > > > That might very well be? Can you better explain what you mean by that > > > to me so I can? > > > I think the general idea here is you''re making alot of work for > > yourself here. Instead of pulling packages down with puppet then > > explicitly calling them to be installed, just create a yum repository, > > use puppet to ensure that repository is included on the machine, and > > just use the yum provider. > > > If you''re tied to using RPM rather than yum (not recommended, rpm > > doesn''t resolve dependencies, yum does), atleast make use of its > > ability to pull from a URL and setup a webserver to host your RPMs so > > you''re not pulling them with puppet to the local system. > > > .r''--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Can you install the package using yum by hand? There appears to be a problem with the repo. - Chad On Mon, Jun 9, 2008 at 3:36 PM, Jeff Leggett <jeffrey.leggett@etrade.com> wrote:> > OK, so I rewrote the maven.pp file as follows: > > class maven { > yumrepo { "p6.rhas5.x86": > name => "p6-RHAS5-x86", > enabled => 1, > baseurl => "http://yum.etrade.com/p6.rhas5.x86/", > } > package {"et_p6_sunjdk15": > ensure => installed, > provider => yum, > require => Yumrepo["p6.rhas5.x86"], > } > package { "et_p6_maven": > ensure => installed, > provider => yum, > require => Package["et_p6_sunjdk15"], > } > } > > Now the --test output says: > > err: Could not prefetch package provider ''yum'': Execution of ''/usr/bin/ > python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ > yumhelper.py'' returned 256: Loading "rhnplugin" plugin > Loading "installonlyn" plugin > Repository ''p6-RHAS5-x86'' is missing name in configuration, using id > This system is not registered with RHN. > RHN support will be disabled. > Traceback (most recent call last): > File "/usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ > yumhelper.py", line 32, in ? > ypl = pkg_lists(my) > File "/usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ > yumhelper.py", line 27, in pkg_lists > return my.doPackageLists(''updates'') > File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 988, > in doPackageLists > self.doRepoSetup() > File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 299, > in doRepoSetup > repo.setup(self.conf.cache) > File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 505, in > setup > raise Errors.RepoError, (''Cannot open/read repomd.xml file for > repository: %s'' % self) > yum.Errors.RepoError: Cannot open/read repomd.xml file for repository: > p6-RHAS5-x86 > > What''d I do now? > > > On Jun 9, 2:14 pm, Jeff Leggett <jeffrey.legg...@etrade.com> wrote: >> OH - of course, yes. That is the plan, but I am trying to get setup >> for a puppet demo tomorrow internally and haven''t gotten those added >> to the yum repo yet.. .that is the plan long term of course. >> >> On Jun 9, 1:53 pm, RijilV <rij...@gmail.com> wrote: >> >> > On 09/06/2008, Jeff Leggett <jeffrey.legg...@etrade.com> wrote: >> >> > > On Jun 9, 1:08 pm, "Evan Hisey" <ehi...@gmail.com> wrote: >> > > Let your tools do the heavy lifting. Between this email and a few of >> > > > your others, it looks to me like you are trying to use directly >> > > > manipulate every thing with puppet is stead of abstracting it out so >> > > > that puppet can work it''s magic, let you not worry about the details. >> >> > > That might very well be? Can you better explain what you mean by that >> > > to me so I can? >> >> > I think the general idea here is you''re making alot of work for >> > yourself here. Instead of pulling packages down with puppet then >> > explicitly calling them to be installed, just create a yum repository, >> > use puppet to ensure that repository is included on the machine, and >> > just use the yum provider. >> >> > If you''re tied to using RPM rather than yum (not recommended, rpm >> > doesn''t resolve dependencies, yum does), atleast make use of its >> > ability to pull from a URL and setup a webserver to host your RPMs so >> > you''re not pulling them with puppet to the local system. >> >> > .r'' > > >-- Chad M. Huneycutt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
>> Now the --test output says: >> >> err: Could not prefetch package provider ''yum'': Execution of ''/usr/bin/ >> python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ >> yumhelper.py'' returned 256: Loading "rhnplugin" plugin >> Loading "installonlyn" plugin >> Repository ''p6-RHAS5-x86'' is missing name in configuration, using id >> This system is not registered with RHN. >> RHN support will be disabled. >> Traceback (most recent call last): >> File "/usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ >> yumhelper.py", line 32, in ? >> ypl = pkg_lists(my) >> File "/usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ >> yumhelper.py", line 27, in pkg_lists >> return my.doPackageLists(''updates'') >> File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 988, >> in doPackageLists >> self.doRepoSetup() >> File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 299, >> in doRepoSetup >> repo.setup(self.conf.cache) >> File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 505, in >> setup >> raise Errors.RepoError, (''Cannot open/read repomd.xml file for >> repository: %s'' % self) >> yum.Errors.RepoError: Cannot open/read repomd.xml file for repository: >> p6-RHAS5-x86^^^^^^^^^^^^^^^^^^^^This is indicative of a broken repo. The repo.xml could be bad or missing. It looks like you may not have run createrepo on the directory or it did not run correctly. What was the command line you used? Evan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---