- service-announce - lists.opendev.org

review.opendev.org Gerrit 3.6 upgrade December 12th, 20:00UTC
by Ian Wienand 07 Dec '22

07 Dec '22

Hello, We are planning upgrade review.opendev.org to the Gerrit 3.6 release on 12th December, 2022 at around 20:00UTC. This will involve an outage of around 1 hour. There should not be much user-visible change after the upgrade; the major items do not affect our usage. The full release notes are at [1] Thank you, -i [1] https://www.gerritcodereview.com/3.6.html

1 0

Mailman v3 migration for OpenDev and Zuul mailing lists 2022-12-05
by Jeremy Stanley 06 Dec '22

06 Dec '22

On Monday, December 5 at 20:00 UTC, the OpenDev Collaboratory systems administrators will be migrating the lists.opendev.org and lists.zuul-ci.org mailing list sites from their existing Mailman 2.1.29 server to a shiny new Mailman 3.3.7 deployment. This maintenance window is expected to last no more than one hour. The key takeaways are as follows: * There will be a brief outage for the affected sites while DNS is updated and configuration, subscriber lists and message archives are imported, but incoming messages should correctly queue at the sender's end and arrive at the conclusion of our work * Because this is on a new server, there are new IP addresses from which list mail will be originating, 162.209.78.70 and 2001:4800:7813:516:be76:4eff:fe04:5423 * Moderation queues will not be copied to the new server, so moderators are encouraged to process any held messages prior to the migration time in order to avoid losing them * Anyone wishing to adjust their list subscriptions, or handle moderation or list configuration after the migration needs to use the Sign Up button on the Web page to create a new account; it will be linked to your imported roles as soon as you confirm by following a URL from an E-mail message the server sends you, and is global for all sites on the server so you only need to do this once * The software providing Web front-ends for list management and archive browsing is entirely new in Mailman v3 and therefore has a much different appearance, though we've added appropriate redirects and frozen copies of old archives in order to accommodate existing hyperlinks Once we smooth out any unanticipated rough patches with the new service, we'll schedule additional maintenance to migrate mailing list sites for other domains (Airship, Kata, OpenInfra, OpenStack, StarlingX). If you have any questions or concerns, feel free to follow up on the service-discuss mailing list or find us in the #opendev channel on the OFTC IRC network. -- Jeremy Stanley

1 1

Discussing Storyboard Needs on service-discuss
by Clark Boylan 07 Nov '22

07 Nov '22

I wanted to make sure that everyone subscribed to this list is aware that we are discussing the Storyboard service, its maintenance needs, and user needs on a thread on service-discuss(a)lists.opendev.org [0]. I have been told that not everyone is aware of the service-discuss list and may have missed that thread. Please follow up on that thread if you have any feedback for (not) wanting to use storyboard or desire to help maintain the service. This is a good opportunity to remind everyone that OpenDev runs three mailing lists for user interaction: 1. service-announce(a)lists.opendev.org [1] This mailing list. Intended to be kept low volume and limited to the most important email notices. 2. service-discuss(a)lists.opendev.org [2] Where we discuss the service needs, meeting agendas, and other topics with more volume. The bulk of our mailing list discussion will be here. All are welcome to join and participate. -discuss and -announce are separate to give people a lower volume option with -announce. 3. service-incident(a)lists.opendev.org This is a private mailing list that OpenDev admins and other trusted individuals may be subscribed to. Users can email this list with sensitive messages like vulnerability disclosures. [0] https://lists.opendev.org/pipermail/service-discuss/2022-October/000370.html [1] https://lists.opendev.org/cgi-bin/mailman/listinfo/service-announce [2] https://lists.opendev.org/cgi-bin/mailman/listinfo/service-discuss

1 0

Changes to our base job nodeset and Ansible 5 removal
by Clark Boylan 12 Oct '22

12 Oct '22

As mentioned in the previous email [0] about updating our default Ansible version to Ansible 6, Zuul will be removing support for Ansible 5 soon. Based on Zuul's currently estimated release schedule we expect this to happen on or near October 18. This change won't take effect until OpenDev restarts Zuul. We will try to make that happen quickly after Zuul lands this change in order to catch any issues quickly. Additionally, it has been called out that we are still defaulting our base job nodeset to ubuntu-focal. Ubuntu Jammy has been released for about 6 months now and has a .1 release as well. To catch up we will update the default nodeset in our base jobs to ubuntu-jammy on October 25, 2022. If you would like to test that your jobs run against Ubuntu Jammy you can modify your jobs to set `nodeset: ubuntu-jammy` today and test them. Note, any jobs that expect a specific platform should already be explicitly setting the nodeset they rely on. There are a number of jobs already running on Jammy which gives us confidence in the newer images. [0] https://lists.opendev.org/pipermail/service-announce/2022-October/000046.ht… Clark

1 0

Updating Zuul tenants' default-ansible-version to 6
by Clark Boylan 05 Oct '22

05 Oct '22

Hello, The OpenDev team is planning to update the default-ansible-version to 6 in the near future. Zuul is planning to drop support for Ansible 5, and switching OpenDev to Ansible 6 early allows us to provide valuable feedback if there are problems. There are other reasons for the switch as well. Ansible 5 broke pipelining, but we expect Ansible 6 to correct this problem. Having pipelining should improve the runtime of jobs. We had been holding off on making this change as StarlingX and OpenStack have both recently worked through some fairly major releases. Those releases exist now making this a good time for a change like this. As far as testing goes, Zuul's Zuul tenant has been running with an Ansible 6 default for several weeks now. I've also tested this change with Devstack specifically [0] as Devstack seems to have a good representative set of complicated jobs. The change to update our defaults is up for review [1]. Feel free to leave any comments there or on this email thread. Note that you can override this change if necessary using the same mechanism I used to test Devstack [0]. However, if you do this please communicate that change to us as Zuul does plan to remove Ansible 5 support which means any problems with Ansible 6 need to be communicated back to Zuul. [0] https://review.opendev.org/c/openstack/devstack/+/858436 [1] https://review.opendev.org/c/openstack/project-config/+/860474

1 0

Dropping support for Ansible 2.x in our Zuul
by Jeremy Stanley 21 Sep '22

21 Sep '22

Following the earlier 2.8/2.9 deprecation in June and change of our default to Ansible 5 in July, we will soon be restarting onto a version of Zuul which no longer supports 2.x versions at all. While we've looked for any lingering overrides to old Ansible versions in master branch jobs and given projects a heads up individually, we lack insight into whether the same may be occurring on non-default branches of projects. If you are aware of any jobs on any of your branches which pin back to an earlier Ansible version, we strongly recommend you remove those overrides at your earliest opportunity, otherwise those jobs will break in the coming days. Here is the change to remove support for Ansible 2.8 and 2.9 in Zuul (we generally restart our Zuul services every weekend, so that's when it's most likely to take effect): https://review.opendev.org/857796 For some example changes which clean up old Ansible version overrides, see this review topic list: https://review.opendev.org/q/topic:cleanup-old-ansible -- Jeremy Stanley

1 0

Move Zuul queue declarations to the project level
by Jeremy Stanley 19 Sep '22

19 Sep '22

This is just a reminder to users of our Zuul service that if you find changes aren't getting any jobs run, or seem to not be running some jobs you expect, you should double-check your configuration to make sure you don't have a lingering "queue" setting in your project pipelines. Over the weekend, we updated to a version of Zuul which removed the long-deprecated support for pipeline level queue declarations, and it now expects queues to be set at the project level instead. We directly notified some projects which we knew would be impacted, but did not send a broader announcement to this list, so I just wanted to be sure anyone taken by surprise with this change doesn't have to waste additional time troubleshooting it. Earlier today, the OpenDev sysadmins corrected numerous cases of this error in the central openstack/project-config repository used by the openstack tenant, but there are still many projects which have similar errors in their in-repository configuration as well. For the reminder from the Zuul maintainers, see here: https://lists.zuul-ci.org/pipermail/zuul-discuss/2022-May/001801.html Also these posts to the OpenStack discussion lists may include helpful information about the transition: https://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0305… -- Jeremy Stanley

1 0

Updating Zuul's Default Ansible Version to Ansible v5
by Clark Boylan 11 Jul '22

11 Jul '22

Hello, The OpenDev team will be updating the default Ansible version in our Zuul tenants from Ansible 2.9 to Ansible 5 on June 30, 2022. Zuul itself will eventually update its default, but making the change in our tenant configs allows us to control exactly when this happens. There are some known issues with this transition; however, we've already worked through and addressed a number of them. If you'd like to double check your jobs work with Ansible 5 today you can do that by pushing a change(s) that updates job.ansible-version [0] to the value '5'. If you do this and find problems please let us know. The Zuul zuul tenant is already running with this set tenant wide which means we expect most of the base job pre-run and post-run content to work with Ansible 5. We also did some spot checking of things like devstack and tempest and expect most of those jobs to function too. Finally, we can eventually expect Zuul to drop support for Ansible 2.8 and 2.9 in the future. What this means is we shouldn't just pin to those old versions without a plan forward to addressing any remaining v5 incompatibilities. [0] https://zuul-ci.org/docs/zuul/latest/config/job.html#attr-job.ansible-versi… If you have any questions let us know. Clark

2 1

A Quick OpenDev Activity Update
by Clark Boylan 23 Jun '22

23 Jun '22

It has been a couple months since I sent out our last activity update, and now seems like a good time to share what is new. Ubuntu Jammy test nodes are now available in both x86_64 and ARM64 flavors. This version of Ubuntu ships with python3.10 and is ready for you to start testing your python projects on this newer runtime. Our Gerrit server running at https://review.opendev.org has been upgraded from Gerrit 3.4 to 3.5. This newer version of Gerrit brings features like new change search predicates, updates to the UI, and performance updates. On the whole this is a bit more of an incremental update compared to previous upgrades. We expect many users haven't even noticed that the upgrade happened. If you'd like to learn more you can read the Gerrit 3.5 release notes: https://www.gerritcodereview.com/3.5.html. Glean 1.23.0 has been released and finally adds proper support for static ipv6 configuration on RPM based distros. Our Ethercalc server previously running at https://ethercalc.openstack.org has been shutdown and removed. On the Zuul side of things there are two changes you should be aware of and planning for. The first is the planned removal of pipeline specific queues in your Zuul config. This configuration was deprecated a number of releases ago and is slated for removal in the next major Zuul release. The OpenStack tenant is the only Zuul tenant that has this old style of configuration. More information on which projects are affected and how to correct it can be found in my email about this topic: https://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html. Note that projects with this configuration in place that do not update will have broken Zuul configurations after we upgrade to the next major Zuul release. Next, is the plan for changing the default Zuul Ansible version from Ansible 2.9 to Ansible 5 on June 30, 2022. We've already done some testing of this and the base jobs as well as devstack and tempest seem to work with newer Ansible. If you'd like to learn more (including how you can test your specific projects early) please check my previous email on this subject: https://lists.opendev.org/pipermail/service-announce/2022-June/000041.html. Looking ahead we should expect our Gitea farm to be upgraded to v1.17. Work will begin on upgrading Gerrit to version 3.6, but it is still too early to know when we will perform that upgrade. There are a few larger tasks we'd like to get moving on including updating our Keycloak server to provide SSO capabilities for our services, upgrading our list servers to Mailman 3, modernizing our StoryBoard deployment, and deploying a Prometheus service to collect server and service metrics. If any of these sound interesting to you, and you would like to help, please reach out. Clark

1 0

CentOS/Fedora IPv6 on gate nodes
by Ian Wienand 02 Jun '22

02 Jun '22

Hello, Consistent IPv6 setup will soon be coming to CentOS and Fedora nodes pending a release of glean [1], the tool we use in the OpenDev gate to configure networking on test nodes. After recent work we believe we now handle the heterogeneous IPv6 setup methods in all our donated clouds consistently. Debian-based distros have had better support for this, so the IPv6 path is generally well tested. However, if this reveals any issues, please reach out (IRC #opendev or service-discuss(a)lists.opendev.org) and we can look into it. Thank you, -i [1] https://opendev.org/opendev/glean/

1 0

review.opendev.org Gerrit 3.5 upgrade June 19th, 20:00UTC
by Ian Wienand 18 May '22

18 May '22

Hello, We are planning upgrade review.opendev.org to the Gerrit 3.5 release on 19th June, 2022 at around 20:00UTC. This will involve an outage of around 1 hour. There should not be much user-visible change after the upgrade. There are some enhanced search predicates [1] which you may find useful. Thank you, -i [1] https://www.gerritcodereview.com/3.5.html#new-change-predicates

1 0

Retiring and shutting down the ethercalc.openstack.org service
by Clark Boylan 04 May '22

04 May '22

Hello, The https://ethercalc.openstack.org service has become problematic for several reasons: * Our configuration management for the service is still based on Puppet and needs to be modernized to continue running the service. * The service itself isn't well maintained. Its build system is apparently broken [0]. * The service does not capture a history of changes like etherpad, confusing users. * The service crashes semi frequently. The major known user of this service was the PTG planning process. We've talked to the folks that help organize and plan the PTG, and they think other tools (like PTGBot) can be used instead without major trouble. Considering all of this, the OpenDev team would like to retire and shutdown this service. The current plan is to keep the service up and running until the end of the month. Then on May 31, 2022 shut down the server hosting the service, snapshot this server, and finally delete it. Please back up any data you would like to preserve before May 31, 2022. [0] https://github.com/audreyt/ethercalc/pull/781 If you have any questions or concerns feel free to respond to this thread or reach out to the OpenDev team. Clark

1 0

A not so Short OpenDev Activity Update
by Clark Boylan 22 Apr '22

22 Apr '22

It has been a busy few weeks for the OpenDev team. We thought it would be a good idea to capture some of the more user facing aspects of what we have been doing lately. Git-review and Bindep both have new releases. Git-review 2.3.0 and 2.3.1 [0] bring better support for newer OpenSSH and signed Git commits, as well as drop compatibility with Python 3.5. Bindep 2.11.0 [1] adds support for AlmaLinux. Git fixed a security issue [2] that broke DevStack and other test jobs. The OpenDev team helped to quickly diagnose the problem and proposed fixes to projects once the issue was understood. If you have jobs with unexpected git operation failures or Python package install issues there is a good chance it is related to this update. You will want to ensure that the user running git commands in a repo is the same user that owns the files in the repo (typically "zuul"). Otherwise you will need to mark the repository as a "safe" repository. Our Twitter status account [3] has been resurrected to provide another way for our users to follow along as we make changes. Whenever we make `#status` messages in IRC that content gets mirrored to this account which you can follow on Twitter. We have also been doing quite a bit of Spring Cleaning (it is spring for some of us anyway). We no longer build Debian Buster or Python 3.7 versions of opendevorg/python-builder and opendevorg/python-base. We did our best to check that no one was using these images, but if you are, the images will remain on Docker Hub until Docker Hub times them out. You should update to a Bullseye Python 3.8 or newer image. Bullseye Python 3.10 images are newly available too. The OpenStack Health service was shut down some time ago, and its configuration management and source repositories have been retired or cleaned up as appropriate. The ELK system that powered elastic-recheck is in the process of being shutdown and retired in favor of a new OpenSearch hosted system managed by OpenStack more directly. Please read the documentation [4] for using the new system if you would like to continue to query job logs using Kibana. Our distro mirrors are getting a haircut to remove packages for unused architectures in our CI system, ISOs/images, and old distro releases. This cleanup will ensure we have plenty of room to add a Jammy Jellyfish mirror to our collection. We'd like to remind our users that while these mirrors are publicly available they are not intended for public consumption. We can and do modify them as our CI system needs change. Finally, looking ahead we'll begin to work on rolling out Jammy Jellyfish images for the CI system now that this latest Ubuntu LTS is available. Our Gerrit 3.5 upgrade should also pick up steam. Most of the changes we expect Gerrit users to see will be in the UI itself. You can read the release notes [5] to find out more. We aren't ready to set a date for this, but you should expect a short downtime which we will announce via service-announce(a)lists.opendev.org. Unfortunately, the Gerrit problems with SSH RSA keys won't be resolved until Gerrit 3.6. [0] https://lists.opendev.org/pipermail/service-announce/2022-April/000036.html [1] https://lists.opendev.org/pipermail/service-announce/2022-April/000035.html [2] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24765 [3] https://twitter.com/opendevinfra/ [4] https://governance.openstack.org/sigs/tact-sig.html#opensearch [5] https://www.gerritcodereview.com/3.5.html

1 0

git-review 2.3.0 and 2.3.1
by Jeremy Stanley 19 Apr '22

19 Apr '22

It's my pleasure to announce the release of git-review 2.3.0 and follow-up fix version 2.3.1. These are the corresponding release notes since the previous release: ======= 2.3.1 ======= Bug Fixes --------- * Improved version string parsing for Git in order to no longer break on Mac OSX/Darwin systems (story 2010002). ======= 2.3.0 ======= Upgrade Notes ------------- * Python 3.5 is no longer supported. * Git 2.10.0 or later is required as git-review now needs the ``--no-show-signature`` option for git-log. Bug Fixes --------- * Git's log.ShowSignature option is now supported. Previously, setting it would confuse git-review into thinking there were twice as many changes to push. * OpenSSH has deprecated its use of scp/rcp protocol in favor of SFTP, which the embedded Apache mina-sshd in widely-deployed Gerrit versions does not yet support. The default officially changed in OpenSSH 9.0 (some distributions, such as Fedora and CentOS, switched their default behavior to this as early as OpenSSH 8.7 or 8.8), leading to a "subsystem request failed on channel 0" error during commit-msg hook retrieval. Now git-review will attempt to detect whether scp's -O option is available to force use of the legacy scp/rcp protocol, and apply it if so. Future git-review versions may change the fallback behavior once an SFTP subsystem is implemented and available for a new Gerrit release. As always, the latest version of git-review is available from PyPI: https://pypi.org/project/git-review Current documentation can be found here: https://docs.opendev.org/opendev/git-review Its source code can be obtained from 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 OFTC IRC network if you have any questions. -- Jeremy Stanley

1 0

bindep 2.11.0
by Jeremy Stanley 19 Apr '22

19 Apr '22

It's my pleasure to announce the release of bindep 2.11.0. These are the corresponding release notes since the previous release: New Features ------------ * Add support for AlmaLinux to Bindep. As always, the latest version of bindep is available from PyPI: https://pypi.org/project/bindep Current documentation can be found here: https://docs.opendev.org/opendev/bindep Its source code can be obtained from the OpenDev Collaboratory: https://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 OFTC IRC network if you have any questions. -- Jeremy Stanley

1 0

review.opendev.org Gerrit downtime for project renames April 15, 2022
by Clark Boylan 07 Apr '22

07 Apr '22

Hello, The OpenDev team will be renaming Gerrit projects on April 15, 2022 beginning at 15:00 UTC. This process requires a Gerrit downtime for the service running on review.opendev.org and is expected to last no more than an hour. If you would like to rename a project, now is the time to begin planning for that work ensuring the necessary changes are proposed. If you have any questions please feel free to respond to this email or reach out to the team. Clark

1 0

Zuul behavior change with Depends-On across queues
by Jeremy Stanley 05 Apr '22

05 Apr '22

A recent improvement to more accurately report Zuul's enqueuing has resulted in an unanticipated difference in behavior for changes declaring a Depends-On relationship between projects which don't share a dependent queue. If you approve the depending change before the dependency has merged, Zuul will now report a Verified -2 vote on the depending change (where previously it just ignored your approval entirely). As a result, because the openstack tenant is configured to require a positive Verified vote before enqueuing into the gate pipeline, this means the depending change will need to be rechecked in order to replace that -2 vote with a +1 in that tenant. For tenants without such a "clean check" rule, the change in behavior is entirely cosmetic. One thing you can do to avoid this is make sure any projects which regularly utilize Depends-On between their changes are configured to belong to the same named queue, which will result in Zuul enqueuing those approved changes into the gate pipeline together without needing to wait for one to merge before the other can be tested. Zuul expects related projects to share a queue and, on approval, will only look up parent and child changes to enqueue within the related projects list, as determined by the queue to which they belong. An alternative workaround is to only approve a change once you've confirmed that any Depends-On has merged, if that dependency is in another project which does not share the same queue. Feel free to follow up on the service-discuss ML with any comments/concerns, or find us in the #opendev channel on OFTC as usual. -- Jeremy Stanley

1 0

Temporary addition of unsigned tag permissions
by Jeremy Stanley 01 Feb '22

01 Feb '22

In the wake of yesterday's Gerrit 3.4 upgrade maintenance, we've observed a regression in behavior where signed Git tags are being misidentified as unsigned[*]. Since our ACLs normally disallow pushing of unsigned (annotated) tags, the result is tag pushes being rejected with a permissions error. As an emergency measure, and in an attempt to not roll back our Gerrit upgrade while working with their developers on a proper patch so solve this, we have updated the ACLs for all projects with a workaround so that they will be able to continue pushing tags. Unfortunately, this workaround means that projects will temporarily be able to push unsigned tags as well as signed ones, so we ask anyone manually tagging their projects be extra careful to remember to pass the -s option to git's tag subcommand. Once we have a proper fix in place, the temporary addition of unsigned tag permissions will be rolled back, and a follow-up announcement sent to this mailing list. [*] https://bugs.chromium.org/p/gerrit/issues/detail?id=15616 -- Jeremy Stanley

1 1

Gerrit Maintenance and Downtime January 24, 2022
by Clark Boylan 19 Jan '22

19 Jan '22

Hello, The OpenDev team will be taking the early year quiet as an opportunity to rename a few projects in Gerrit and upgrade Gerrit to 3.4 starting January 24, 2022 at 22:00 UTC. We expect to be done by 00:00 UTC January 25, 2022. If you would like to rename a project now is the time to get that preparation done. Please link any rename proposals in our list here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_… The Gerrit 3.4 release notes can be found at https://www.gerritcodereview.com/3.4.html. This upgrade does not require offline reindexing which means it should happen quickly. We are also automatically testing the 3.3 to 3.4 upgrade in our CI system. Additionally there is a downgrade process that we can use to fall back to 3.3 if necessary. Let us know if you have any questions or concerns, Clark

1 0

Changes to OpenDev's stable of CI images
by Clark Boylan 07 Dec '21

07 Dec '21

Hello, CentOS 8 reaches end of life on December 31, 2021. This means now is the time for you to convert jobs to CentOS 8|9 Stream or some other appropriate platform. The OpenDev team will plan to remove CentOS 8 images and mirrors from our infrastructure in early January, hopefully by January 14, 2022. Again, please update your jobs now so that you are prepared. These changes are necessary as the distro will no longer be supported, and there is no way for us to ensure that the images will be secure or that we'll even be able to build them. We've also got Fedora 35 lined up to replace Fedora 34. Due to Fedora's short support window we typically swap out one Fedora release with the next when the next is ready. If you are using the fedora-34 label please update it to fedora-35. If you are using fedora-latest we'll be updating that to use fedora-35 and the swap will happen automatically for you. We expect to have Fedora 34 cleaned up by the end of the year. Additionally both OpenSUSE 15 and Tumbleweed could use some help. For OpenSUSE 15 we need to update it to 15.3 as well as updating the associated mirrors if we plan to keep it around. I'm happy to keep this image around if we can get volunteers in the community that can help with that. If there isn't interest in modernizing the OpenSUSE 15 images I'd like to propose we clean them up in January along with the CentOS 8 images. For Tumbleweed, the images haven't received much use or attention. I'd like to propose that we simply retire this image and clean it up. We had thought it might be a good platform for monitoring upcoming changes in the Linux world, but the reality is that only works if you've got people active caring for it and adjusting to those changes. The Tumbleweed cleanup will likely begin before the end of the year. Finally, our Gentoo images bounce between being buildable and broken with more time spent being broken than not. I'd like to propose that this image also get cleaned up in the near future. Again, if there is interest in the community for keeping this alive I think we can make that happen. But as is this image is not in a sustainable place and it would be better for us to stop running jobs on it. Let us know if you have any questions or comments, Clark

1 0

git-review 2.2.0
by Jeremy Stanley 24 Nov '21

24 Nov '21

It's my pleasure to announce the release of git-review 2.2.0. These are the corresponding release notes since the previous release: Bug Fixes --------- * When checking for unstaged or uncommitted changes to avoid performing a test rebase, unstaged and uncommitted changes in Git submodules are now ignored since those won’t be rebased anyway. * git-review now handles the Git core.hooksPath configuration option correctly. Thus, it installs the commit-msg hook into the core.hooksPath directory, if that option is set. Otherwise, it continues to install the hook into .git/hooks, relative to the root of the checkout. * With Git 2.18.0 and later, the --rebase-merges (-r) option will be used in place of the deprecated --preserve-merges (-p) option. This fixes a critical error when git-review is used with Git versions 2.34.0 onward, where the old option is no longer available. As always, the latest version of git-review is available from PyPI: https://pypi.org/project/git-review Current documentation can be found here: https://docs.opendev.org/opendev/git-review Its source code can be obtained from 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 OFTC IRC network if you have any questions. -- Jeremy Stanley

1 0

Bindep 2.10.1 has been released
by Jeremy Stanley 20 Oct '21

20 Oct '21

Please take notice that version 2.10.1 of Bindep has been released. Notable Changes --------------- * The Packaging module dependency from 2.10.0 was adjusted to accommodate versions of Pip prior to 9.0.0 (when PEP 503 data-requires-python support was added) on Python 3.5 and earlier. As always, the latest version of Bindep is available from PyPI: https://pypi.org/project/bindep Read the latest documentation: https://docs.opendev.org/opendev/bindep/latest/ And source code can be obtained through the OpenDev Collaboratory: https://opendev.org/opendev/bindep Please don't hesitate to follow up through the service-discuss at lists.opendev.org mailing list or in the #opendev channel on the OFTC IRC network if you have any questions. -- Jeremy Stanley

1 0

Bindep 2.10.0 has been released
by Clark Boylan 18 Oct '21

18 Oct '21

I am happy to announce version 2.10.0 of Bindep has been released. Notable Changes --------------- * Packaging (https://pypi.org/project/packaging/) is now a required dependency. * Support for Rocky Linux is added. * Support for Manjaro is added. As always, the latest version of Bindep is available from PyPI: https://pypi.org/project/bindep Read the latest documentation: https://docs.opendev.org/opendev/bindep/latest/ And source code can be obtained through the OpenDev Collaboratory: https://opendev.org/opendev/bindep Please don't hesitate to follow up through the service-discuss at lists.opendev.org mailing list or in the #opendev channel on the OFTC IRC network if you have any questions. Clark

1 0

Gear 0.16.0 has been released
by Clark Boylan 18 Oct '21

18 Oct '21

I am happy to announce version 0.16.0 of Gear has been released. Notable Changes --------------- * The testsuite has been updated to support newer OpenSSL fixing issues like https://storyboard.openstack.org/#!/story/2009250. * TLS version negotiation is improved to prefer the newest version of TLS supported by both client and server excluding TLS 1.3. * Connections to gearman servers are now randomly distributed which should more evenly distribute load. * Timeout processing is improved to avoid a situation where a connection timeout could deadlock the client. As always, the latest version of gear is available from PyPI: https://pypi.org/project/gear Read the latest documentation: https://docs.opendev.org/opendev/gear/latest/ And source code can be obtained through the OpenDev Collaboratory: https://opendev.org/opendev/gear Please don't hesitate to follow up through the service-discuss at lists.opendev.org mailing list or in the #opendev channel on the OFTC IRC network if you have any questions. Clark

1 0

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