Hello Thomas,
FYI gate is failing after cirros image version changed in devstack that's the reason "test_floatingip_associate_disassociate" is failing because the cirros image that the test is using is not available now. We fixed that issue in Horizon by updating cirros image version and then the devstack cirros image version again got updated. we updated again in the horizon.
Even if we disable/skip the test "test_floatingip_associate_disassociate" more integration tests start failing which we trying to fix. We are trying hard to fix the gate asap, but the issue is we still didn't know exactly due to which patch we merged it's started failing. Currently, horizon is using the Firefox browser to run the integration jobs and we can't see the browser error log for that. So we are trying to run that job with Chrome so we can see the error log and fix it.
We think these issues are happening after we updated the JQuery-migrate version for Horizon [1] but the latest JQuery-migrate version is not compatible with the older version of jQuery, maybe that's why it is failing. I purpose an initial patch in openstack/requirements[2], now waiting for it to get merged, and then will move to the next step. The simpler thing we can do to fix the gate, for now, is to move back to the older JQuery-migrate version but we are planning to update these versions for so long and we already know we are going to hit all these issues because these migrations are not so simple.
Thanks & regards, Vishal Manchanda
[1] https://review.opendev.org/c/openstack/requirements/+/883402 [2] https://review.opendev.org/c/openstack/requirements/+/887720
On Thu, Jul 6, 2023 at 2:20 PM Thomas Goirand zigo@debian.org wrote:
Hi team!
It's been more than a month that it's impossible to merge anything in Horizon, due to the gate being broken because of one single functional test being broken:
FAILED
openstack_dashboard/test/integration_tests/tests/test_floatingips.py::TestFloatingipAssociateDisassociate::test_floatingip_associate_disassociate
I do understand that you guys want to fix this, and I do understand how hard this puzzle is, with selenium, the chrome driver, jquery and all. It's far from simple, and I very much welcome the team effort.
However, could we just disable that unit test until this is fixed, so that simple patches like this one can be merged?
https://review.opendev.org/c/openstack/horizon/+/885577
Or more complex one from my colleague?
https://review.opendev.org/c/openstack/horizon/+/885570
More than a month without merging any patch is a long time...
Cheers,
Thomas Goirand (zigo)