Hello,
When I kick off SVN1992 with storeconfigs=yes, I get the following error:
err: Could not store configs: SQLite3::SQLException: SQL logic error
or missing database: INSERT INTO resources ("exported",
"line",
"title", "host_id", "restype",
"source_file_id") VALUES(NULL, 23,
''svnpkgadd-emacs-nox-etc'', NULL, NULL, NULL)
The database does exist, and when I attempt to execute the SQL
statement from sqlite3 I get:
# sqlite3 clientconfigs.sqlite3
SQLite version 3.3.6
Enter ".help" for instructions
sqlite> INSERT INTO resources ("exported", "line",
"title", "host_id",
"restype", "source_file_id") VALUES(NULL, 23,
''svnpkgadd-emacs-nox-etc'', NULL, NULL, NULL);
SQL error: resources.restype may not be NULL
Changing "t.column :restype, :string, :null => false" to
"t.column
:restype, :string" in puppet/rails/database/schema.rb succeed the
second time I ran the client....
.r''
On Dec 29, 2006, at 12:12 PM, RijilV wrote:> Hello, > > When I kick off SVN1992 with storeconfigs=yes, I get the following > error: > > err: Could not store configs: SQLite3::SQLException: SQL logic error > or missing database: INSERT INTO resources ("exported", "line", > "title", "host_id", "restype", "source_file_id") VALUES(NULL, 23, > ''svnpkgadd-emacs-nox-etc'', NULL, NULL, NULL) > > The database does exist, and when I attempt to execute the SQL > statement from sqlite3 I get: > > # sqlite3 clientconfigs.sqlite3 > SQLite version 3.3.6 > Enter ".help" for instructions > sqlite> INSERT INTO resources ("exported", "line", "title", "host_id", > "restype", "source_file_id") VALUES(NULL, 23, > ''svnpkgadd-emacs-nox-etc'', NULL, NULL, NULL); > SQL error: resources.restype may not be NULL > > > Changing "t.column :restype, :string, :null => false" to "t.column > :restype, :string" in puppet/rails/database/schema.rb succeed the > second time I ran the client....Weird. How did you manage to have a resource with no type? That should be completely impossible. I definitely don''t want to allow NULL types. What''s the code that resulted in this? Also, did you already have a client db from previous releases? I can''t imagine that that would be the problem, but if you do, I recommend getting rid of it. -- If you would be a real seeker after truth, it is necessary that at least once in your life you doubt, as far as possible, all things. -- Rene Descartes --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
After some testing, I found a couple of things...
my site.pp now looks like:
node default {
package { "tcpdump":
ensure => latest,
}
}
After removing ''clientconfigs.sqlite3'' I get the following
error the
first time I run a client:
notice: Using default node for pt-fc4-hvm.test
err: Puppet::Parser::AST::ResourceDef failed with error NameError:
undefined local variable or method `provider'' for
Puppet::Type::Package::Ensure:Class at /etc/puppet/manifests/site.pp:5
If ''clientconfigs.sqlite3'' already exists:
notice: Using default node for pt-fc4-hvm.test
info: Redefining package in Puppet::Type
err: Could not store configs: SQLite3::SQLException: SQL logic error
or missing database: INSERT INTO resources ("exported",
"line",
"title", "host_id", "restype",
"source_file_id") VALUES(NULL, 5,
''tcpdump'', NULL, NULL, NULL)
Turning off storeconfigs works. Is this possibly a local problem?
I''m running puppetmaster on FedoraCore6, test clients on FC6 and FC4.
All of this is on a Xen machine, puppetmaster is being run in the
Dom0, there are FC6 and FC4 HVM domUs, and one FC6 paravirtulized
domU. Sqlite3 was from rpms, when installing the gem for sqlite3-ruby
everything went fine and was detected correctly.
.r''
On 12/29/06, Luke Kanies <luke@madstop.com> wrote:>
> On Dec 29, 2006, at 12:12 PM, RijilV wrote:
>
> > Hello,
> >
> > When I kick off SVN1992 with storeconfigs=yes, I get the following
> > error:
> >
> > err: Could not store configs: SQLite3::SQLException: SQL logic error
> > or missing database: INSERT INTO resources ("exported",
"line",
> > "title", "host_id", "restype",
"source_file_id") VALUES(NULL, 23,
> > ''svnpkgadd-emacs-nox-etc'', NULL, NULL, NULL)
> >
> > The database does exist, and when I attempt to execute the SQL
> > statement from sqlite3 I get:
> >
> > # sqlite3 clientconfigs.sqlite3
> > SQLite version 3.3.6
> > Enter ".help" for instructions
> > sqlite> INSERT INTO resources ("exported",
"line", "title", "host_id",
> > "restype", "source_file_id") VALUES(NULL, 23,
> > ''svnpkgadd-emacs-nox-etc'', NULL, NULL, NULL);
> > SQL error: resources.restype may not be NULL
> >
> >
> > Changing "t.column :restype, :string, :null => false" to
"t.column
> > :restype, :string" in puppet/rails/database/schema.rb succeed
the
> > second time I ran the client....
>
> Weird. How did you manage to have a resource with no type? That
> should be completely impossible.
>
> I definitely don''t want to allow NULL types. What''s the
code that
> resulted in this?
>
> Also, did you already have a client db from previous releases? I
> can''t imagine that that would be the problem, but if you do, I
> recommend getting rid of it.
>
> --
> If you would be a real seeker after truth, it is necessary that at
> least once in your life you doubt, as far as possible, all things.
> -- Rene Descartes
> ---------------------------------------------------------------------
> Luke Kanies | http://reductivelabs.com | http://madstop.com
>
>
> _______________________________________________
> Puppet-users mailing list
> Puppet-users@madstop.com
> https://mail.madstop.com/mailman/listinfo/puppet-users
>
On Dec 29, 2006, at 1:11 PM, RijilV wrote:> After some testing, I found a couple of things... > > my site.pp now looks like: > > node default { > package { "tcpdump": > ensure => latest, > } > } > > After removing ''clientconfigs.sqlite3'' I get the following error the > first time I run a client: > > notice: Using default node for pt-fc4-hvm.test > err: Puppet::Parser::AST::ResourceDef failed with error NameError: > undefined local variable or method `provider'' for > Puppet::Type::Package::Ensure:Class at /etc/puppet/manifests/site.pp:5 > > If ''clientconfigs.sqlite3'' already exists: > > notice: Using default node for pt-fc4-hvm.test > info: Redefining package in Puppet::Type > err: Could not store configs: SQLite3::SQLException: SQL logic error > or missing database: INSERT INTO resources ("exported", "line", > "title", "host_id", "restype", "source_file_id") VALUES(NULL, 5, > ''tcpdump'', NULL, NULL, NULL) > > > Turning off storeconfigs works. Is this possibly a local problem? > I''m running puppetmaster on FedoraCore6, test clients on FC6 and FC4. > All of this is on a Xen machine, puppetmaster is being run in the > Dom0, there are FC6 and FC4 HVM domUs, and one FC6 paravirtulized > domU. Sqlite3 was from rpms, when installing the gem for sqlite3-ruby > everything went fine and was detected correctly.This seems really strange. I can''t even conceive of how you could get a resource that doesn''t have a type, since the class that''s trying to write to rails itself requires a type. That''s the entirety of your configuration? The first bits, where package complains about missing the provider, especially concern me. At the very least, the client-side stuff should have nothing to do with whether the db exists. Can you try running the package tests in svn? Just cd into test/providers and run ''sudo ./package.rb'', then cd into test/types and run ''./ package.rb''. Feel free to just run the first one as yourself, at least to start -- it''ll install and remove a couple of packages during testing, but it''ll fail if the packages are already installed so it shouldn''t affect your system. -- Measure with a micrometer. Mark with chalk. Cut with an axe. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
That is all of my configuration on the test setup.. I ran package.rb on a few of the hosts, and noticed this. Things ran fine if I didn''t have gems installed, if gems was installed I got: Finished in 15.652345 seconds. 1) Failure:test_wxrubylayouts_gem(TestPackageProvider) [./package.rb:163:in `run_package_installation_test'' ./package.rb:210:in `test_wxrubylayouts_gem'']:Could not install package.Exception raised:Class: <ArgumentError>Message: <"Illformed requirement [-v]">---Backtrace---/usr/lib/ruby/site_ruby/1.8/rubygems/version.rb:296:in `parse''/usr/lib/ruby/site_ruby/1.8/rubygems/version.rb:227:in `initialize''/usr/lib/ruby/site_ruby/1.8/rubygems/version.rb:226:in `collect''/usr/lib/ruby/site_ruby/1.8/rubygems/version.rb:226:in `initialize''/usr/lib/ruby/site_ruby/1.8/rubygems/version.rb:27:in `new''/usr/lib/ruby/site_ruby/1.8/rubygems/version.rb:27:in `initialize''/usr/lib/ruby/site_ruby/1.8/rubygems.rb:184:in `new''/usr/lib/ruby/site_ruby/1.8/rubygems.rb:184:in `activate''/usr/lib/ruby/site_ruby/1.8/rubygems.rb:66:in `active_gem_with_options''/usr/lib/ruby/site_ruby/1.8/rubygems.rb:50:in `gem''../../lib/puppet/provider/package/gem.rb:74:in `install''./package.rb:164:in `run_package_installation_test''./package.rb:163:in `run_package_installation_test''./package.rb:210:in `test_wxrubylayouts_gem''---------------5 tests, 1556 assertions, 1 failures, 0 errors If I remove gems the test runs fine. Doesn''t really explain what is going on however, as I never had gems installed on any of the test clients until I ran the test on the server and got the above error. The fact that the server fails this test couldn''t effect the client could it? .r'' On 12/29/06, Luke Kanies <luke@madstop.com> wrote:> This seems really strange. I can''t even conceive of how you could > get a resource that doesn''t have a type, since the class that''s > trying to write to rails itself requires a type. That''s the entirety > of your configuration? > > The first bits, where package complains about missing the provider, > especially concern me. At the very least, the client-side stuff > should have nothing to do with whether the db exists. Can you try > running the package tests in svn? Just cd into test/providers and > run ''sudo ./package.rb'', then cd into test/types and run ''./ > package.rb''. Feel free to just run the first one as yourself, at > least to start -- it''ll install and remove a couple of packages > during testing, but it''ll fail if the packages are already installed > so it shouldn''t affect your system. > > -- > Measure with a micrometer. Mark with chalk. Cut with an axe. > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >
On Dec 29, 2006, at 3:44 PM, RijilV wrote:> That is all of my configuration on the test setup.. > > I ran package.rb on a few of the hosts, and noticed this. Things ran > fine if I didn''t have gems installed, if gems was installed I got:[snip] Weird, so gems are failing for you. Can anyone else reproduce this problem?> If I remove gems the test runs fine. Doesn''t really explain what is > going on however, as I never had gems installed on any of the test > clients until I ran the test on the server and got the above error. > The fact that the server fails this test couldn''t effect the client > could it?Well, if gems don''t work on the server then they probably don''t work on the client, but you''re not using gems so it shouldn''t matter either way. If the other package tests succeed, then you''re probably ok. What package type are you using here? -- The real art of conversation is not only to say the right thing at the right place but to leave unsaid the wrong thing at the tempting moment. -- Dorothy Nevill --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com