We just have released our new stable code base OBS 2.8.0. Please find the full announcement on our blog:
http://openbuildservice.org/2017/04/07/version-2.8/
Updaters need to adapt their repository channels and should read the README.UPDATERS file which comes with this version.
Features ========
UI: * Allow triggering services from the UI. * Show a hint to project maintainers, when he/she is not a package maintainer of the target package of a request * Main projects list is now filtered based on a configurable (by the admin) regular expression * Users can download the public key and SSL certificate for a project via the project home page * import of kiwi build descriptions is supported (obs-service-kiwi_import)
API: * Allow admins to lock or delete users and their home projects via new command * Users can be declared as sub accounts of other users. Useful for automated scripts. * New API route to get public key and SSL certificate: GET /source/:project_name/_keyinfo * New feature toggle config file. Use config/feature.yml to enable/disable features in the OBS.
Backend: * multibuild: allow to build multiple jobs from one source package without the need of creating local links * experimental support of snap package format * workers are now also tracked when they went away (new states "down", "away" and "dead") * worker capabilities can be requested * usable workers can be requested with uncommited constraints * functionality to remove published packages (osc unpublish) * New obsservicedispatch service to handle source service runs in a queue and asynchron. * preinstall images can be used for local building * improved speed of diffing sources * Support caching of pulled git sources
Shipment: * optional docker container to run source services is provided
Wanted changes: ===============
* kiwi builds: build configuration changes from the project where the kiwi file is stored have always an effect now.
* maintenance_release requests are locking only the source packages on creation now. They don't lock the patchinfos. The project gets locked on release now.
* service wrapper script for LXC got replaced by a docker alternative
Other changes ============= * Server side pagination on user show page for improving the performance.
* The way to identify spiders got changed. A separate configuration via apache is no longer required. See the Administration Guide.
* Frontend stack is using ruby 2.4 and rails 5.0.1 now
Notes for systems using systemd: ================================
OBS is using init scripts, not systemd style .service files. This will stay until we will switch from SLES 11 to SLES 12 as default production platform.
openSUSE installations may use systemd (instead of sysvinit) and it should work in general. Not working are usages like
# rcobssrcserver status
You will only get the systemd status here.
Also stopping services may not kill all processes, which leads to abstract errors when trying to restart them. We heard also about trashed MySQL databases when using systemd.
To avoid these problems you need switch directory to avoid the systemd mapper:
# cd /etc/init.d # ./obssrcserver status|stop|start
Am 07.04.2017 um 10:46 schrieb Evan Rolfe:
Updaters need to adapt their repository channels and should read the README.UPDATERS file which comes with this version.
running into update issue:
== 20170118091131 AddReviewIdToReview: migrating ============================== -- add_reference(:reviews, :review, {:index=>true, :foreign_key=>true}) -> 4.9735s == 20170118091131 AddReviewIdToReview: migrated (4.9736s) =====================
== 20170123115500 RemoveDuplicateIndexes: migrating =========================== -- execute("ALTER TABLE `attrib_namespace_modifiable_bies` DROP INDEX `index_attrib_namespace_modifiable_bies_on_attrib_namespace_id`;") -> 0.3035s -- execute("ALTER TABLE `attrib_types` DROP INDEX `attrib_namespace_id`;") rails aborted! StandardError: An error has occurred, all later migrations canceled:
Mysql2::Error: Can't DROP 'attrib_namespace_id'; check that column/key exists: ALTER TABLE `attrib_types` DROP INDEX `attrib_namespace_id`; /srv/www/obs/api/db/migrate/20170123115500_remove_duplicate_indexes.rb:32:in `up' bin/rails:4:in `require' bin/rails:4:in `<main>' ActiveRecord::StatementInvalid: Mysql2::Error: Can't DROP 'attrib_namespace_id'; check that column/key exists: ALTER TABLE `attrib_types` DROP INDEX `attrib_namespace_id`; /srv/www/obs/api/db/migrate/20170123115500_remove_duplicate_indexes.rb:32:in `up' bin/rails:4:in `require' bin/rails:4:in `<main>' Mysql2::Error: Can't DROP 'attrib_namespace_id'; check that column/key exists /srv/www/obs/api/db/migrate/20170123115500_remove_duplicate_indexes.rb:32:in `up' bin/rails:4:in `require' bin/rails:4:in `<main>' Tasks: TOP => db:migrate (See full trace by running task with --trace)
########## #1553 - Kann Index 'index_attrib_types_on_attrib_namespace_id_and_name' nicht löschen: wird für eine Fremdschlüsselbeschränkung benötigt
need help please
Am 07.04.2017 um 10:46 schrieb Evan Rolfe:
Updaters need to adapt their repository channels and should read the README.UPDATERS file which comes with this version.
running into update issue:
== 20170118091131 AddReviewIdToReview: migrating ============================== -- add_reference(:reviews, :review, {:index=>true, :foreign_key=>true}) -> 4.9735s == 20170118091131 AddReviewIdToReview: migrated (4.9736s) =====================
== 20170123115500 RemoveDuplicateIndexes: migrating =========================== -- execute("ALTER TABLE `attrib_namespace_modifiable_bies` DROP INDEX `index_attrib_namespace_modifiable_bies_on_attrib_namespace_id`;") -> 0.3035s -- execute("ALTER TABLE `attrib_types` DROP INDEX `attrib_namespace_id`;") rails aborted! StandardError: An error has occurred, all later migrations canceled:
Mysql2::Error: Can't DROP 'attrib_namespace_id'; check that column/key exists: ALTER TABLE `attrib_types` DROP INDEX `attrib_namespace_id`; /srv/www/obs/api/db/migrate/20170123115500_remove_duplicate_indexes.rb:32:in `up' bin/rails:4:in `require' bin/rails:4:in `<main>' ActiveRecord::StatementInvalid: Mysql2::Error: Can't DROP 'attrib_namespace_id'; check that column/key exists: ALTER TABLE `attrib_types` DROP INDEX `attrib_namespace_id`; /srv/www/obs/api/db/migrate/20170123115500_remove_duplicate_indexes.rb:32:in `up' bin/rails:4:in `require' bin/rails:4:in `<main>' Mysql2::Error: Can't DROP 'attrib_namespace_id'; check that column/key exists /srv/www/obs/api/db/migrate/20170123115500_remove_duplicate_indexes.rb:32:in `up' bin/rails:4:in `require' bin/rails:4:in `<main>' Tasks: TOP => db:migrate (See full trace by running task with --trace)
########## #1553 - Kann Index 'index_attrib_types_on_attrib_namespace_id_and_name' nicht löschen: wird für eine Fremdschlüsselbeschränkung benötigt
need help please
On Dienstag, 2. Mai 2017, 11:41:17 CEST wrote Christian:
Am 07.04.2017 um 10:46 schrieb Evan Rolfe:
Updaters need to adapt their repository channels and should read the README.UPDATERS file which comes with this version.
running into update issue:
== 20170118091131 AddReviewIdToReview: migrating
-- add_reference(:reviews, :review, {:index=>true, :foreign_key=>true}) -> 4.9735s == 20170118091131 AddReviewIdToReview: migrated (4.9736s) =====================
== 20170123115500 RemoveDuplicateIndexes: migrating
-- execute("ALTER TABLE `attrib_namespace_modifiable_bies` DROP INDEX `index_attrib_namespace_modifiable_bies_on_attrib_namespace_id`;") -> 0.3035s -- execute("ALTER TABLE `attrib_types` DROP INDEX `attrib_namespace_id`;") rails aborted! StandardError: An error has occurred, all later migrations canceled:
Mysql2::Error: Can't DROP 'attrib_namespace_id'; check that column/key exists: ALTER TABLE `attrib_types` DROP INDEX `attrib_namespace_id`; /srv/www/obs/api/db/migrate/20170123115500_remove_duplicate_indexes.rb:32:in `up' bin/rails:4:in `require' bin/rails:4:in `<main>' ActiveRecord::StatementInvalid: Mysql2::Error: Can't DROP 'attrib_namespace_id'; check that column/key exists: ALTER TABLE `attrib_types` DROP INDEX `attrib_namespace_id`; /srv/www/obs/api/db/migrate/20170123115500_remove_duplicate_indexes.rb:32:in `up' bin/rails:4:in `require' bin/rails:4:in `<main>' Mysql2::Error: Can't DROP 'attrib_namespace_id'; check that column/key exists /srv/www/obs/api/db/migrate/20170123115500_remove_duplicate_indexes.rb:32:in `up' bin/rails:4:in `require' bin/rails:4:in `<main>' Tasks: TOP => db:migrate (See full trace by running task with --trace)
########## #1553 - Kann Index 'index_attrib_types_on_attrib_namespace_id_and_name' nicht löschen: wird für eine Fremdschlüsselbeschränkung benötigt
need help please
Did you solved this meanwhile?
It should be save to comment out the drop in the migration. It should have existed, but it is gone now anyway...
On Mai 23 2017, Adrian Schröter adrian@suse.de wrote:
Did you solved this meanwhile?
I also saw a similar error with RemoveDuplicateIndexes when migrating from 2.6 to 2.8. Apparently there are configurations where the index was never created in the first place.
Mysql2::Error: Can't DROP 'package_id'; check that column/key exists: ALTER TABLE `channels` DROP INDEX `package_id`;
Andreas.
Am 23.05.2017 um 09:31 schrieb Adrian Schröter:
Did you solved this meanwhile?
I roled back ...
It should be save to comment out the drop in the migration. It should have existed, but it is gone now anyway...
will try it again in about two weeks ...
buildservice@lists.opensuse.org
-
Adrian Schröter -
Andreas Schwab -
Christian -
Evan Rolfe