)]}'
{
  "commit": "91ca00a96f5a98c2282f4d896d1a45ebe013317a",
  "tree": "92ccce073c027d5a50e9c02e7fe82d5a628f5e1a",
  "parents": [
    "b0ab2128cb84c161a783587aff0637819bd4c8c7"
  ],
  "author": {
    "name": "silvacarloss",
    "email": "ces.eduardo98@gmail.com",
    "time": "Mon Sep 04 10:09:21 2023 -0300"
  },
  "committer": {
    "name": "silvacarloss",
    "email": "ces.eduardo98@gmail.com",
    "time": "Wed Sep 06 13:31:31 2023 -0300"
  },
  "message": "Use Ubuntu Jammy and Temporarily disable scenario tests\n\nA couple of issues happening at the moment:\n\n- Nova recently merged a change that bumps the libvirt version in\nthe Bobcat release [1]. The new libvirt version is not available\nin Ubuntu Focal. In order to get the new libvirt version, our jobs\nthat were using Ubuntu Focal, are now forced to use Jammy, so we\nbump it to the new version in this patch.\n\n- The support for Ubuntu Focal has also been dropped in this\nrelease [2]. Making it one more reason to get the new jammy\nimages.\n\nWhile upgrading the image, some other issues surfaced:\n\n- Some CI jobs are doing IPv6 testing, which use quagga. Quagga\ndoes not have a candidate for installation in Jammy and must be\nreplaced. This issue is already documented [3].\n\n- The inability to set up IPv6, combined with the scenario tests\nbeing enabled in the LVM and CEPH drivers brought up another known\nissue: when doing IPv6 setup, we don\u0027t set up only IPv6 networking\nand we also end up setting crucial information for the scenario\ntests to run in the function that does IPv6 setup. So in case the\njob is only using IPv4 in scenario testing, we currently don\u0027t set\nsome key configuration to let the shares be created/mounted [4].\n\n- Due to the reasons above, the scenario tests will never pass, as\nwe can\u0027t use Focal images, and when using Jammy, we can\u0027t do\nscenario testing.\n\nThis is blocking the Manila gate and all other changes in the CI.\nAs we are forced to use the Jammy image and the scenario tests\nwon\u0027t pass, we disable them in this change, do some refactoring\nin Manila [5], and re-enable them again for IPv4, until we have\nfigured out the quagga replacement.\n\n[1] https://review.opendev.org/c/openstack/nova/+/887255\n[2] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034968.html\n[3] https://bugs.launchpad.net/manila/+bug/1998489\n[4] https://github.com/openstack/manila/blob/master/devstack/plugin.sh#L1104-L1116\n[5] https://review.opendev.org/c/openstack/manila/+/893804\n\nChange-Id: Ia45a8e7f7c9cf9959bcc9b9a7243cccbbd1f4916\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "690b8bc40c3189ee604d5ec8c4502bba91449a65",
      "old_mode": 33188,
      "old_path": "zuul.d/manila-tempest-jobs.yaml",
      "new_id": "6383c4ba93d303b4c97ddd77ca66135dcf13809f",
      "new_mode": 33188,
      "new_path": "zuul.d/manila-tempest-jobs.yaml"
    },
    {
      "type": "modify",
      "old_id": "28db22967dd73b29223c8956511e4705ea446cb5",
      "old_mode": 33188,
      "old_path": "zuul.d/manila-tempest-stable-jobs.yaml",
      "new_id": "e59b5fbe972d467dd7e5396e94dc3f98cab09852",
      "new_mode": 33188,
      "new_path": "zuul.d/manila-tempest-stable-jobs.yaml"
    }
  ]
}