- service-announce - lists.opendev.org

review.opendev.org Gerrit Outages in the Next Couple of Weeks
by Clark Boylan 06 Oct '21

06 Oct '21

Hello, The OpenDev team will be performing a Gerrit 3.3 upgrade on Sunday October 10, 2021 from 21:00UTC to 23:00UTC. Then on Friday October 15, 2021 from 18:00UTC to 19:00UTC we will be renaming a number of projects in Gerrit. Both of these actions require Gerrit service downtime on review.opendev.org. We expect the outages will be shorter than the allotted time but this gives us some flexibility. If you would like to rename your project, now is the time to do the work to make sure your renames are on the list. Please reach out to the OpenDev team and we'll help you get the necessary changes proposed and reviewed. If you are curious, Gerrit 3.3 release notes can be found at: https://www.gerritcodereview.com/3.3.html. Notably, we are able to revert to 3.2 should that become necessary. Feel free to bring up any questions or concerns with the team and we'll do our best to answer, Clark

1 0

Renaming Projects on July 30, 2021 at 15:00UTC
by Clark Boylan 26 Jul '21

26 Jul '21

Hello everyone, The OpenDev team will be renaming projects in Gerrit and Gitea on Friday July 30, 2021 starting at 15:00 UTC. This requires a short Gerrit downtime. If you need to rename a project now is the time to get it on the list at https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_…. Let us know if you have any questions. Clark

1 0

Take care when deleting email addresses in Gerrit
by Clark Boylan 14 Jul '21

14 Jul '21

Hello everyone, We have discovered a bug in Gerrit [0] that allows you to delete your account's Ubuntu One OpenID association if you delete the email from your account associated with that OpenID. When you do this the next time you log in Gerrit will create a new account for you. Fixing this after the fact is currently difficult. We are working to correct this but the required corrections take time. We would like to avoid these issues in the first place. Please avoid deleting email addresses from your accounts unless you are sure they are not associated with your OpenID. If you would like help double checking that for you please let us know and one of our Gerrit admins can double check. We are working to make this fixable after the fact, and will try to work with the Gerrit upstream to prevent you from deleting Ubuntu One OpenID associations from your account in the first place. Until then we apologize for the inconvenience. Finally, this message and others like it are sent to service-announce(a)lists.opendev.org. I am sending this email to a much broader set of mailing lists because the service-announce list membership is quite small. All of our users should be subscribed to that list to get important notices like this one. We keep the traffic low and only send mail there when we feel it is important for you to see it. [0] https://bugs.chromium.org/p/gerrit/issues/detail?id=14776 Clark

1 0

OpenDev IRC services are moving to OFTC this weekend
by Jeremy Stanley 26 May '21

26 May '21

As a majority of our constituent projects have voiced a preference for enacting our long-standing evacuation plan, the OpenDev Collaboratory's IRC service bots will be switching from Freenode to the OFTC network this weekend (May 29-30, 2021). We understand this is short notice, but multiple projects have requested that we act quickly. Please expect some gaps in channel logging and notifications from our various bots over the course of the weekend. I have provided a much more detailed writeup to the service-discuss mailing list, and encourage anyone with questions to read it and follow up there if needed. Subsequent updates will be sent only to service-discuss, in order to limit noise for individual project lists and keep further discussion focused in one place as much as possible: http://lists.opendev.org/pipermail/service-discuss/2021-May/000249.html -- Jeremy Stanley

1 0

Switching default nodeset in base job to ubuntu-focal
by Jeremy Stanley 18 May '21

18 May '21

The OpenDev Collaboratory is normally somewhat conservative about when it changes its Zuul node "default" (that is, the nodeset in its base job). It's been ubuntu-bionic since at least July of 2019 when we first moved our base job into its own repository, and ubuntu-focal nodes have been available in our deployment since before Ubuntu's 20.04 LTS was officially released more than a year ago. All that is to say, updating our default is overdue. On Tuesday, 2021-05-18 (two weeks from today) we'll approve https://review.opendev.org/789098 to update the nodeset to ubuntu-focal for any jobs which don't specify their own or inherit from another job which does. We've already merged a change which updates our base-test job to reflect this, so you can test either by explicitly setting your jobs to use an ubuntu-focal nodeset or to inherit from base-test (though we don't recommend merging changes for the latter, just rely on speculative execution to identify problems which you may encounter when the default changes). Please reply to the service-discuss mailing list with any questions or concerns. You should also feel free to leave comments on the change linked above. -- Jeremy Stanley

1 1

git-review 2.1.0
by Jeremy Stanley 24 Apr '21

24 Apr '21

It's my pleasure to announce the release of git-review 2.1.0. These are the corresponding release notes since the previous release: New Features ------------ * Add support for --no-thin which is passed to git push. This is useful to work around situations where Gerrit’s JGit and git-review’s C git implementations cannot agree on the pack file contents used to transfer a push. When they disagree you see this as unpack failures due to missing trees. Using --no-thin avoids complicated negotiations and works around this problem. As always, the latest version of git-review is available from PyPI: https://pypi.org/project/git-review Find the updated documentation at its new home: https://docs.opendev.org/opendev/git-review And source code can be obtained through the OpenDev Collaboratory: https://opendev.org/opendev/git-review Please don't hesitate to follow up through the service-discuss(a)lists.opendev.org mailing list or in the #opendev channel on the Freenode IRC network if you have any questions. -- Jeremy Stanley

1 0

git-review 2.0.0
by Jeremy Stanley 03 Mar '21

03 Mar '21

It's my pleasure to announce the release of git-review 2.0.0. These are the corresponding release notes since the previous release: New Features ------------ * A new gitreview.branchauthor option allows configuring the change author (owner) name part of the autocreated branch name when downloading changes. * A new gitreview.notopic configuration setting makes git-review always behave as if the --notopic command line option was supplied. Upgrade Notes ------------- * Not really a deprecation so much as a removal, Gerrit 2.15 (released in 2017) ceased providing a draft state for changes, and many large sites were disabling support for it far earlier than that. As of now, git-review has removed the -D and --draft options entirely, and so can no longer push draft changes on old Gerrit deployments which still allowed them. * As of this release, git-review no longer supports running under the Python 2.7 interpreter. The major version component has been increased accordingly. Users wishing to use git-review with Python 2.7 can cap their installations like pip install "git-review<2", though pip version 9 and later will use python_requires package metadata to avoid installing git-review on an unsupported interpreter. Future removal of support for Python 3 minor versions will only result in a minor version increase for corresponding git-review releases. Bug Fixes --------- * The Change-Id generating commit hook is now installed into any detected Git submodules, so that it will take effect when creating changes within a submodule and not just in the parent repository. * Encoding was corrected for Git credentials, which was previously causing HTTP authentication to fail under some Python 3 versions. * Change download functions now preserve any unapplied local edits on the branch when attempting to reset the worktree. * The --no-follow-tags option to git push is now used for all pushes, so that git-review won’t error when encountering a local tag which is absent from Gerrit. * For safety, attempts to push a commit with unstaged or uncommitted changes in the worktree will be caught and an error reported, rather than leaving it up to git rebase to spot them. This addresses a situation where users enabling rebase.autostash would otherwise experience data loss when the test rebase is subsequently reset. As always, the latest version of git-review is available from PyPI: https://pypi.org/project/git-review Find the updated documentation at its new home: https://docs.opendev.org/opendev/git-review And source code can be obtained through the OpenDev Collaboratory: https://opendev.org/opendev/git-review Please don't hesitate to follow up through the service-discuss(a)lists.opendev.org mailing list or in the #opendev channel on the Freenode IRC network if you have any questions. -- Jeremy Stanley

1 0

Recommended change to Zuul pipeline config for all tenants
by jim＠acmegating.com 16 Feb '21

16 Feb '21

Hi, If you manage the Zuul pipeline definitions for a tenant in OpenDev's Zuul, please make the following change to the pipeline definitions as soon as possible: * Remove any reference to the "mysql" reporter. The current version of Zuul now automatically adds the SQL reporter to every pipeline definition, so the explicit configuration is unnecessary. It is now marked as deprecated and will produce an error in a future release of Zuul, and it produces an warning message now. Here is an example change which I performed for the OpenStack tenant: https://review.opendev.org/775716 Thanks, Jim

1 0

bindep 2.9.0
by Jeremy Stanley 06 Feb '21

06 Feb '21

It's my pleasure to announce the release of bindep 2.9.0. These are the corresponding release notes since the previous release: New Features ------------ * Bindep can now be imported as a Python module, useful when making plugins for other Python-based tools or experimenting in the REPL. * Basic support for Oracle Linux is now included. * A new set of virtual platform profiles, platform:base-py2 and platform:base-py3 can be used to differentiate packages on Debian derivatives (including Ubuntu), Red Hat derivatives (including CentOS and Fedora), and MacOS X/Darwin. Bug Fixes --------- * Improved parsing of warning and error output from the apk tool in alpine. * Now handles parsing pacman 1.5.2 and later output so –brief works on newer releases of Archlinux. * If a local file has the same name as a package, this no longer confuses parsing of pacman output on Arch Linux. Find the updated documentation at its new home: https://docs.opendev.org/opendev/bindep/ Please don't hesitate to follow up through the service-discuss(a)lists.opendev.org mailing list or in the #opendev channel on the Freenode IRC network if you have any questions. -- Jeremy Stanley

1 0

review.opendev.org Gerrit outage and upgrade 15:00UTC November 20 to 01:00UTC November 23, 2020
by Clark Boylan 23 Nov '20

23 Nov '20

The OpenDev team is planning a long weekend Gerrit outage on review.opendev.org starting 15:00UTC November 20 and running to 01:00UTC November 23, 2020 in order to upgrade to Gerrit 3.2. The upgrade has two major portions. First we will incrementally move from our current version 2.13 to 2.16. Each point release requires a database migration and git indexing operations that take the majority of the time. The second major part, once at version 2.16, is to convert Gerrit to use the new NoteDB backend. This stores reviews together with code in the git trees, rather than in a separate database. There are known problems converting to NoteDB from any version prior to 2.16, which is why we need the initial upgrade steps. This is this slowest portion of the upgrade process, and the one most prone to unforeseen issues despite extensive pre-testing. We will be creating snapshots to facilitate quick fallback if required. Once this is complete, we can move to the 3.x series and incrementally upgrade from 3.0 to 3.2. Timing wise we expect the first 2.13 -> 2.16 phase to be completed in about 8 hours. Next we'll start the notedb migration and let that run overnight. When we return the next morning the NoteDB migration should be complete and we can finish with the last set of upgrades to 3.2. Hopefully that means we're done in the first half of the outage window, but if we have problems, things are slower than we expect, or if we have to work through any details after finishing the upgrade we'd like to have the extra buffer in place. Some important things to know: * Gerrit's web UI will be changing. We don't have a lot of control over this. As a result we'll lose some existing CI result rendering niceness that we have on 2.13 (in particular the summary table and CI results toggle will go away). We hope that once we've upgraded we can investigate solving this through Gerrit plugins. * All of our existing integrations with launchpad and storyboard may not be fully functional. The changes to the database system impact aspects of how we lookup user details in order to update bugs. * Gerrit 3.2 requires git 2.2.0 or newer to use the Change ID commit hook. This may be a problem for RHEL/CentOS 7 users. * This upgrade will fix the openssh problems with host keys that Fedora 33 users have experienced. * Q&A * If this upgrade isn't perfect why are we doing it anyway? We've come to the realization that if we don't make imperfect progress we'll never make any progress. We have decided that the benefits outweigh the known drawbacks and we'll do our best to work on those issues after the upgrade. Why now? This is long overdue and the quiet time at the end of the year tends to be a good time for these big upgrades Can I install my favorite Gerrit plugin? We're hoping to complete the upgrade then start looking at things like this. One big reason for it is finishing the upgrade simplifies the number of Gerrit docker images we need to care for. Will my third party CI system continue to work? We expect they will. We know Zuul is tested against newer Gerrit already. How can I help? Once the upgrade is complete you'll want to confirm the basic functionality you rely on is there. We know there will be differences or missing features. Patience as we figure out how to address those on a new Gerrit installation is much appreciated. If you're interested in hacking on Java and Javascript we'd love help with the plugins necessary to address the known problems. You should be able to build this out locally without any special access. Please let us know if you are interested and we can help you bootstrap. Finally, we're continuing to test the upgrade and trying to sort out if we can get this upgrade completed in a shorter period of time. We'll keep you up to date if further testing forces us to postpone or if the outage window timeframe changes at all. As always feel free to send your questions our way and we'll do our best to answer them. On behalf of the OpenDev team, Clark

2 2