[opensuse-buildservice] Best way to keep local Installation updated
We have a local installation of obs running on ESX Server for a few years. We have problems every time we have to update the OBS server to a current version. If we start with the Appliance from http://openbuildservice.org/download/other/ would we be able to keep that Installation updated? Can we then simply update the appliance by downloading the new Image and deploy it to the Server? Or would it be better to do a Package Installation on a Opensuse Server and keep that current? -- Ralf Becker Director Software Development Stylite AG Isaac-Fulda-Allee 9 | Tel. +49 6131 32702-0 D-55124 Mainz | Fax. +49 6131 32702-70 Email: rb@stylite.de www.stylite.de | www.egroupware.org Managing Directors: Andre Keller | Ralf Becker | Gudrun Mueller Chairman of the supervisory board: Prof. Dr. Birger Leon Kropshofer VAT DE214280951 | Registered HRB 46224 Mainz Germany -- Ralf Becker Outdoor Unlimited Training GmbH [www.outdoor-training.de] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 (0)631 31657-0
On Montag, 4. April 2016, 10:14:50 wrote Ralf Becker:
We have a local installation of obs running on ESX Server for a few years. We have problems every time we have to update the OBS server to a current version.
If we start with the Appliance from http://openbuildservice.org/download/other/ would we be able to keep that Installation updated?
yes
Can we then simply update the appliance by downloading the new Image and deploy it to the Server?
The appliance images are migrating the data, if /srv/obs is mounted on an extra volume.
Or would it be better to do a Package Installation on a Opensuse Server and keep that current?
You can also just update the packages. No matter if you deployed the appliance or did a manual installation. Read the README.UPDATERS file for details, esp. how to migrate the database. -- 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 Donnerstag, 28. April 2016, 09:40:15 wrote Adrian Schröter:
On Montag, 4. April 2016, 10:14:50 wrote Ralf Becker:
We have a local installation of obs running on ESX Server for a few years. We have problems every time we have to update the OBS server to a current version.
If we start with the Appliance from http://openbuildservice.org/download/other/ would we be able to keep that Installation updated?
yes
Can we then simply update the appliance by downloading the new Image and deploy it to the Server?
The appliance images are migrating the data, if /srv/obs is mounted on an extra volume.
Or would it be better to do a Package Installation on a Opensuse Server and keep that current?
You can also just update the packages. No matter if you deployed the appliance or did a manual installation. Read the README.UPDATERS file for details, esp. how to migrate the database.
You wrote in your other mail that you run OBS 2.4. Please note that you may need to update to 2.5 first to go to 2.6 (or 2.7 beta) directly. -- 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
Hi Adrian, Am 28.04.16 um 09:41 schrieb Adrian Schröter:
On Donnerstag, 28. April 2016, 09:40:15 wrote Adrian Schröter:
On Montag, 4. April 2016, 10:14:50 wrote Ralf Becker:
We have a local installation of obs running on ESX Server for a few years. We have problems every time we have to update the OBS server to a current version.
If we start with the Appliance from http://openbuildservice.org/download/other/ would we be able to keep that Installation updated?
yes
Can we then simply update the appliance by downloading the new Image and deploy it to the Server?
The appliance images are migrating the data, if /srv/obs is mounted on an extra volume.
Or would it be better to do a Package Installation on a Opensuse Server and keep that current?
You can also just update the packages. No matter if you deployed the appliance or did a manual installation. Read the README.UPDATERS file for details, esp. how to migrate the database.
You wrote in your other mail that you run OBS 2.4. Please note that you may need to update to 2.5 first to go to 2.6 (or 2.7 beta) directly.
We have success full updated from our 2.4.5 appliance to a 2.5.7 appliance, all OBS data incl. projects and packages seems to be present. We then tried to update from 2.5.7 to a 2.6.9 appliance without obvious error messages on the console, but OBS seems empty now. Logs look like it did not migrate but created a new instance: obs:/srv/obs # cat /srv/www/obs/api/log/db_migrate.log 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 db_project_type table by loading test fixtures Seeding issue trackers ... Any pointers where to look? We also tried and failed with the following upgrade: We installed and empty 2.6.9, created a single project and package and tried to update to 2.7beta (2.6.90) appliance. Project is also gone after the upgrade. Ralf -- Ralf Becker Director Software Development Stylite AG Isaac-Fulda-Allee 9 | Tel. +49 6131 32702-0 D-55124 Mainz | Fax. +49 6131 32702-70 Email: rb@stylite.de www.stylite.de | www.egroupware.org Managing Directors: Andre Keller | Ralf Becker | Gudrun Mueller Chairman of the supervisory board: Prof. Dr. Birger Leon Kropshofer VAT DE214280951 | Registered HRB 46224 Mainz Germany
On Freitag, 29. April 2016, 15:28:18 wrote Ralf Becker: ...
We have success full updated from our 2.4.5 appliance to a 2.5.7 appliance, all OBS data incl. projects and packages seems to be present.
We then tried to update from 2.5.7 to a 2.6.9 appliance without obvious error messages on the console, but OBS seems empty now.
Logs look like it did not migrate but created a new instance:
obs:/srv/obs # cat /srv/www/obs/api/log/db_migrate.log 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 db_project_type table by loading test fixtures Seeding issue trackers ...
Any pointers where to look?
We also tried and failed with the following upgrade: We installed and empty 2.6.9, created a single project and package and tried to update to 2.7beta (2.6.90) appliance. Project is also gone after the upgrade.
Uh, that is not something you want to have before weekend .... When you see the "Seeding" lines someone or some script must have called the db:setup rake command. It could be done by the obsapisetup script. It is doing so, when your database is in mysql is not called "api_production" . So, that would be the first thing I would check (use "SHOW DATABASES" on mysql console). You can either rename it then or configure the other name in /srv/www/obs/api/config/database.yml and run the migration manual -- 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
Hi Adrian, Am 29.04.16 um 16:49 schrieb Adrian Schröter:
On Freitag, 29. April 2016, 15:28:18 wrote Ralf Becker: ...
We have success full updated from our 2.4.5 appliance to a 2.5.7 appliance, all OBS data incl. projects and packages seems to be present.
We then tried to update from 2.5.7 to a 2.6.9 appliance without obvious error messages on the console, but OBS seems empty now.
Any pointers where to look?
We also tried and failed with the following upgrade: We installed and empty 2.6.9, created a single project and package and tried to update to 2.7beta (2.6.90) appliance. Project is also gone after the upgrade.
Uh, that is not something you want to have before weekend ....
When you see the "Seeding" lines someone or some script must have called the db:setup rake command.
It could be done by the obsapisetup script. It is doing so, when your database is in mysql is not called "api_production" .
Database was the right lead: it is in /srv/obs/MySql, but that is not written into /etc/my.cnf, if you upgrade. datadir is not set and defaults to (empty) /var/lib/mysql. That should be fixed in your update routines, to ease updates. Other problem that we now manually fixed is: after each update obsrun has a new nummeric user-id, as user is created again in /etc/passwd. That should be alt least mentioned in your upgrade guide, or better handled automatic. Last thing we noticed and manually fixed: calculation of worker size leads to a negative result. So we got 2.6.9 working now, after above manual fixes. We tried upgrading to 2.7beta, which works, but we reverted because of a HTTP 500 status, whenever you click on a project link. Probably for a reason it's still beta. Ralf -- Ralf Becker Director Software Development Stylite AG Isaac-Fulda-Allee 9 | Tel. +49 6131 32702-0 D-55124 Mainz | Fax. +49 6131 32702-70 Email: rb@stylite.de www.stylite.de | www.egroupware.org Managing Directors: Andre Keller | Ralf Becker | Gudrun Mueller Chairman of the supervisory board: Prof. Dr. Birger Leon Kropshofer VAT DE214280951 | Registered HRB 46224 Mainz Germany
On Dienstag, 3. Mai 2016, 08:43:41 wrote Ralf Becker:
Hi Adrian,
Am 29.04.16 um 16:49 schrieb Adrian Schröter:
On Freitag, 29. April 2016, 15:28:18 wrote Ralf Becker: ...
We have success full updated from our 2.4.5 appliance to a 2.5.7 appliance, all OBS data incl. projects and packages seems to be present.
We then tried to update from 2.5.7 to a 2.6.9 appliance without obvious error messages on the console, but OBS seems empty now.
Any pointers where to look?
We also tried and failed with the following upgrade: We installed and empty 2.6.9, created a single project and package and tried to update to 2.7beta (2.6.90) appliance. Project is also gone after the upgrade.
Uh, that is not something you want to have before weekend ....
When you see the "Seeding" lines someone or some script must have called the db:setup rake command.
It could be done by the obsapisetup script. It is doing so, when your database is in mysql is not called "api_production" .
Database was the right lead: it is in /srv/obs/MySql, but that is not written into /etc/my.cnf, if you upgrade. datadir is not set and
hm, it should be ...
defaults to (empty) /var/lib/mysql.
That should be fixed in your update routines, to ease updates.
Other problem that we now manually fixed is: after each update obsrun has a new nummeric user-id, as user is created again in /etc/passwd. That should be alt least mentioned in your upgrade guide, or better handled automatic.
obsrun should be fixed to id 103 for historic reasons ... done in config.sh executed when building the appliance.
Last thing we noticed and manually fixed: calculation of worker size leads to a negative result.
So we got 2.6.9 working now, after above manual fixes.
We tried upgrading to 2.7beta, which works, but we reverted because of a HTTP 500 status, whenever you click on a project link. Probably for a reason it's still beta.
hm, no, traces from /srv/www/obs/log/ logfiles would have been nice ... -- 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 Dienstag, 3. Mai 2016, 09:25:32 wrote Adrian Schröter:
On Dienstag, 3. Mai 2016, 08:43:41 wrote Ralf Becker: ...
Other problem that we now manually fixed is: after each update obsrun has a new nummeric user-id, as user is created again in /etc/passwd. That should be alt least mentioned in your upgrade guide, or better handled automatic.
obsrun should be fixed to id 103 for historic reasons ... done in config.sh executed when building the appliance.
there is indeed a bug .... do you have your server data in a OBS named LVM volume group? Or how do you mount your produciton data? -- 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
Hi Adrian, Am 03.05.16 um 09:45 schrieb Adrian Schröter:
On Dienstag, 3. Mai 2016, 09:25:32 wrote Adrian Schröter:
On Dienstag, 3. Mai 2016, 08:43:41 wrote Ralf Becker: ...
Other problem that we now manually fixed is: after each update obsrun has a new nummeric user-id, as user is created again in /etc/passwd. That should be alt least mentioned in your upgrade guide, or better handled automatic.
obsrun should be fixed to id 103 for historic reasons ... done in config.sh executed when building the appliance.
For both updates we did, we had to fix obsrun id.
there is indeed a bug .... do you have your server data in a OBS named LVM volume group?
Yes: obs:~ # vgs VG #PV #LV #SN Attr VSize VFree OBS 1 7 0 wz--n- 250,00g 26,50g
Or how do you mount your produciton data?
Ralf -- Ralf Becker Director Software Development Stylite AG Isaac-Fulda-Allee 9 | Tel. +49 6131 32702-0 D-55124 Mainz | Fax. +49 6131 32702-70 Email: rb@stylite.de www.stylite.de | www.egroupware.org Managing Directors: Andre Keller | Ralf Becker | Gudrun Mueller Chairman of the supervisory board: Prof. Dr. Birger Leon Kropshofer VAT DE214280951 | Registered HRB 46224 Mainz Germany
Hi Adrian, Am 03.05.16 um 09:25 schrieb Adrian Schröter:
On Dienstag, 3. Mai 2016, 08:43:41 wrote Ralf Becker:
Am 29.04.16 um 16:49 schrieb Adrian Schröter: We tried upgrading to 2.7beta, which works, but we reverted because of a HTTP 500 status, whenever you click on a project link. Probably for a reason it's still beta.
hm, no, traces from /srv/www/obs/log/ logfiles would have been nice ...
HTTP 500 was noted in browser and according to my college Wim there was nothing in the logs about it. We removed that snapshot, so it's not that easy to give you further logs. Only think I can say, it happend in multiple places, when I click on a project (not package or other navigation) link. Ralf -- Ralf Becker Director Software Development Stylite AG Isaac-Fulda-Allee 9 | Tel. +49 6131 32702-0 D-55124 Mainz | Fax. +49 6131 32702-70 Email: rb@stylite.de www.stylite.de | www.egroupware.org Managing Directors: Andre Keller | Ralf Becker | Gudrun Mueller Chairman of the supervisory board: Prof. Dr. Birger Leon Kropshofer VAT DE214280951 | Registered HRB 46224 Mainz Germany
participants (2)
-
Adrian Schröter -
Ralf Becker