Re: [opensuse-buildservice] Bootstrap private OBS issues
On Freitag, 28. Juli 2017, 23:49:16 CEST wrote Hans-Peter Jansen:
Hi Adrian,
On Freitag, 28. Juli 2017 23:31:50 Adrian Schröter wrote:
On Freitag, 28. Juli 2017, 23:18:02 CEST wrote Hans-Peter Jansen:
Create your own login and password and set yourself as Admin. <first part okay, but how can I archive the second part?>
in webui it is
Configuration -> Manage users
and select "Make user admin" on actions menu of your user.
Log on to the Web UI as Admin and click on the Icon "Setup OBS". <There's no such Icon, probably unnecessary nowadays?!?>
It is called "Configuration" these days. You see it only as admin.
Accept the default. It should work.
well, that should be, go to "Interconnect" tab and accept the default.
However, you will also be sent there when you try to add a repo to your project and there are no base distros.
<hmm>
Create your first repository project
Create by web UI
A project at the root of OBS. Select from under 'Locations' -> 'Projects'. At the top left click on 'Create a new project '. Give it a name (e.g. Meego-test)
you see ... the wiki page is unmaintained Meego documentation ;)
Enter a 'ProjectName'(Meego-test:1.2), 'Tilte'(Meego-test 1.2), 'Description'. you need to be 'Admin' to create a project at the root of OBS. <Hmm, did that as Admin, but harvested a "Sorry, you are not authorized to create this Project.">
Any ideas anybody?
You are no admin most likely.
I guess so, but I'm logged in as Admin, it says "OBS Instance Superuser Admin" in the profile, but there's no Configuration link, neither on the profile page:
nor on the main page:
Am I too silly?
uh, looks like a bug indeed.... anyway, you should be able to reach it by going to http://$your_host/configuration manually -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Freitag, 28. Juli 2017, 23:57:36 CEST wrote Adrian Schröter:
On Freitag, 28. Juli 2017, 23:49:16 CEST wrote Hans-Peter Jansen: ...
I guess so, but I'm logged in as Admin, it says "OBS Instance Superuser Admin" in the profile, but there's no Configuration link, neither on the profile page:
nor on the main page:
Am I too silly?
uh, looks like a bug indeed....
anyway, you should be able to reach it by going to
http://$your_host/configuration
manually
what is osc -A https://$your_api api /person/Admin saying? Does it list the global admin role for that user? -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Freitag, 28. Juli 2017 23:58:45 Adrian Schröter wrote:
On Freitag, 28. Juli 2017, 23:57:36 CEST wrote Adrian Schröter:
On Freitag, 28. Juli 2017, 23:49:16 CEST wrote Hans-Peter Jansen: ...
I guess so, but I'm logged in as Admin, it says "OBS Instance Superuser Admin" in the profile, but there's no Configuration link, neither on the profile page:
nor on the main page:
Am I too silly?
uh, looks like a bug indeed....
anyway, you should be able to reach it by going to
http://$your_host/configuration
manually
what is
osc -A https://$your_api api /person/Admin
saying? Does it list the global admin role for that user?
~> osc -A https://obsserver.lisa.loc api /person/Admin <person> <login>Admin</login> <email>root@lisa.loc</email> <realname>OBS Instance Superuser</realname> <state>confirmed</state> <watchlist/> </person> -- Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Freitag, 28. Juli 2017 23:57:36 you wrote:
On Freitag, 28. Juli 2017, 23:49:16 CEST wrote Hans-Peter Jansen:
Am I too silly?
uh, looks like a bug indeed....
anyway, you should be able to reach it by going to
http://$your_host/configuration
manually
Nope, results in "Requires admin privileges"... Can I modify the db admin record directly? Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Samstag, 29. Juli 2017, 00:14:40 CEST wrote Hans-Peter Jansen:
On Freitag, 28. Juli 2017 23:57:36 you wrote:
On Freitag, 28. Juli 2017, 23:49:16 CEST wrote Hans-Peter Jansen:
Am I too silly?
uh, looks like a bug indeed....
anyway, you should be able to reach it by going to
http://$your_host/configuration
manually
Nope, results in "Requires admin privileges"...
Can I modify the db admin record directly?
hm, you could tweak the SQL db or you can try to run bundle.ruby2.4 exec rails.ruby2.4 db:setup again, which should have done this in first place...
Pete
-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Samstag, 29. Juli 2017 00:18:35 Adrian Schröter wrote:
On Samstag, 29. Juli 2017, 00:14:40 CEST wrote Hans-Peter Jansen:
On Freitag, 28. Juli 2017 23:57:36 you wrote:
On Freitag, 28. Juli 2017, 23:49:16 CEST wrote Hans-Peter Jansen:
Am I too silly?
uh, looks like a bug indeed....
anyway, you should be able to reach it by going to
http://$your_host/configuration
manually
Nope, results in "Requires admin privileges"...
Can I modify the db admin record directly?
hm, you could tweak the SQL db or you can try to run
bundle.ruby2.4 exec rails.ruby2.4 db:setup
again, which should have done this in first place...
Now it gets interesting: obsserver:/srv/www/obs/api# bundle.ruby2.4 exec rails.ruby2.4 db:setup /usr/lib64/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/xml_mini.rb:51: warning: constant ::Fixnum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/xml_mini.rb:52: warning: constant ::Bignum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activejob-5.0.1/lib/active_job/arguments.rb:38: warning: constant ::Fixnum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activejob-5.0.1/lib/active_job/arguments.rb:38: warning: constant ::Bignum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/core_ext/numeric/conversions.rb:138: warning: constant ::Fixnum is deprecated ERROR 1049 (42000): Unknown database 'api_development' rails aborted! failed to execute: `mysql` Please check the output above for any errors and make sure that `mysql` is installed in your PATH and has proper permissions. /srv/www/obs/api/lib/tasks/databases.rake:90:in `block (2 levels) in <top (required)>' bin/rails:4:in `require' bin/rails:4:in `<main>' Tasks: TOP => db:structure:load (See full trace by running task with --trace) -- Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Samstag, 29. Juli 2017, 00:34:04 CEST wrote Hans-Peter Jansen:
On Samstag, 29. Juli 2017 00:18:35 Adrian Schröter wrote:
On Samstag, 29. Juli 2017, 00:14:40 CEST wrote Hans-Peter Jansen:
On Freitag, 28. Juli 2017 23:57:36 you wrote:
On Freitag, 28. Juli 2017, 23:49:16 CEST wrote Hans-Peter Jansen:
Am I too silly?
uh, looks like a bug indeed....
anyway, you should be able to reach it by going to
http://$your_host/configuration
manually
Nope, results in "Requires admin privileges"...
Can I modify the db admin record directly?
hm, you could tweak the SQL db or you can try to run
bundle.ruby2.4 exec rails.ruby2.4 db:setup
again, which should have done this in first place...
Now it gets interesting:
obsserver:/srv/www/obs/api# bundle.ruby2.4 exec rails.ruby2.4 db:setup /usr/lib64/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/xml_mini.rb:51: warning: constant ::Fixnum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/xml_mini.rb:52: warning: constant ::Bignum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activejob-5.0.1/lib/active_job/arguments.rb:38: warning: constant ::Fixnum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activejob-5.0.1/lib/active_job/arguments.rb:38: warning: constant ::Bignum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/core_ext/numeric/conversions.rb:138: warning: constant ::Fixnum is deprecated ERROR 1049 (42000): Unknown database 'api_development'
k, forgot to mention that you have to add RAILS_ENV=production to the line -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Samstag, 29. Juli 2017 00:40:42 you wrote:
On Samstag, 29. Juli 2017, 00:34:04 CEST wrote Hans-Peter Jansen:
On Samstag, 29. Juli 2017 00:18:35 Adrian Schröter wrote:
On Samstag, 29. Juli 2017, 00:14:40 CEST wrote Hans-Peter Jansen:
On Freitag, 28. Juli 2017 23:57:36 you wrote:
On Freitag, 28. Juli 2017, 23:49:16 CEST wrote Hans-Peter Jansen:
Am I too silly?
uh, looks like a bug indeed....
anyway, you should be able to reach it by going to
http://$your_host/configuration
manually
Nope, results in "Requires admin privileges"...
Can I modify the db admin record directly?
hm, you could tweak the SQL db or you can try to run
bundle.ruby2.4 exec rails.ruby2.4 db:setup
again, which should have done this in first place...
Now it gets interesting:
obsserver:/srv/www/obs/api# bundle.ruby2.4 exec rails.ruby2.4 db:setup /usr/lib64/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/xml _mini.rb:51: warning: constant ::Fixnum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/xm l_mini.rb:52: warning: constant ::Bignum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activejob-5.0.1/lib/active_job/arguments. rb:38: warning: constant ::Fixnum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activejob-5.0.1/lib/active_job/arguments. rb:38: warning: constant ::Bignum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/co re_ext/numeric/conversions.rb:138: warning: constant ::Fixnum is deprecated ERROR 1049 (42000): Unknown database 'api_development'
k, forgot to mention that you have to add
RAILS_ENV=production
to the line
Okay, the complete magic spell was: $ cd /srv/www/obs/api/ $ DISABLE_DATABASE_ENVIRONMENT_CHECK=1 bundle.ruby2.4 exec rails.ruby2.4 db:setup RAILS_ENV=production [...] Seeding architectures table... Seeding roles table... Seeding users table... Seeding roles_users table... Seeding static_permissions table... Seeding static permissions for admin role in roles_static_permissions table... Seeding static permissions for maintainer role in roles_static_permissions table... Seeding static permissions for reader role in roles_static_permissions table... Seeding static permissions for downloader role in roles_static_permissions table... Seeding attrib_namespaces table... Seeding attrib_types table... Seeding issue trackers ... Guess what, I get a Configuration Icon now. Horray. THanks. Cheers, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Samstag, 29. Juli 2017 01:15:16 Hans-Peter Jansen wrote:
On Samstag, 29. Juli 2017 00:40:42 you wrote:
On Samstag, 29. Juli 2017, 00:34:04 CEST wrote Hans-Peter Jansen:
On Samstag, 29. Juli 2017 00:18:35 Adrian Schröter wrote:
On Samstag, 29. Juli 2017, 00:14:40 CEST wrote Hans-Peter Jansen:
On Freitag, 28. Juli 2017 23:57:36 you wrote:
On Freitag, 28. Juli 2017, 23:49:16 CEST wrote Hans-Peter Jansen: > Am I too silly?
uh, looks like a bug indeed....
anyway, you should be able to reach it by going to
http://$your_host/configuration
manually
Nope, results in "Requires admin privileges"...
Can I modify the db admin record directly?
hm, you could tweak the SQL db or you can try to run
bundle.ruby2.4 exec rails.ruby2.4 db:setup
again, which should have done this in first place...
Now it gets interesting:
obsserver:/srv/www/obs/api# bundle.ruby2.4 exec rails.ruby2.4 db:setup /usr/lib64/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/x ml _mini.rb:51: warning: constant ::Fixnum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/x m l_mini.rb:52: warning: constant ::Bignum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activejob-5.0.1/lib/active_job/arguments . rb:38: warning: constant ::Fixnum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activejob-5.0.1/lib/active_job/arguments . rb:38: warning: constant ::Bignum is deprecated /usr/lib64/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/c o re_ext/numeric/conversions.rb:138: warning: constant ::Fixnum is deprecated ERROR 1049 (42000): Unknown database 'api_development'
k, forgot to mention that you have to add
RAILS_ENV=production
to the line
Okay, the complete magic spell was:
$ cd /srv/www/obs/api/ $ DISABLE_DATABASE_ENVIRONMENT_CHECK=1 bundle.ruby2.4 exec rails.ruby2.4 db:setup RAILS_ENV=production [...] Seeding architectures table... Seeding roles table... Seeding users table... Seeding roles_users table... Seeding static_permissions table... Seeding static permissions for admin role in roles_static_permissions table... Seeding static permissions for maintainer role in roles_static_permissions table... Seeding static permissions for reader role in roles_static_permissions table... Seeding static permissions for downloader role in roles_static_permissions table... Seeding attrib_namespaces table... Seeding attrib_types table... Seeding issue trackers ...
Guess what, I get a Configuration Icon now. Horray.
Forgot to mention: this issue might be related to multiple LVM setup attempts. I stopped all obs processes and mysql before them, but had to stop mysql and a screen process manually before being able to unmount /srv/obs cleanly (which might be the reason for the failed unmounts during shutdown as well...). Then I setup LVM though yast, and rebooted. So it started with an empty /srv/obs, which should result in a proper initial OBS setup including the database, even if exercised a few times. Cheers, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (2)
-
Adrian Schröter -
Hans-Peter Jansen