Hi,
Dnia czwartek, 11 maja 2023 10:10:50 CEST Rodolfo Alonso Hernandez pisze:
> Hi Julia:
>
> Let me open a LP bug for this issue. I'll check if this call is being
> tested in our CI and with the specific DB backend.
>
> Regards.
>
> On Wed, May 10, 2023 at 7:32 PM Julia Kreger <juliaashleykreger@gmail.com>
> wrote:
>
> > Greetings folks,
> >
> > I have spent a substantial amount of time investigating CI issues as of
> > recent, and I noticed that at some point the legacy
> > "ironic-tempest-pxe_ipmitool-postgres" CI job which has been kept around as
> > a non-voting postgres support canary, is now failing on the master branch.
> >
> > Specifically, looking through the logs[0], it appears that structurally
> > the queries are no longer compatible.
> >
> > np0033933847 neutron-server[90677]: WARNING oslo_db.sqlalchemy.exc_filters
> > [None req-155d0299-07ef-433a-8576-467127c82be4 None None] DBAPIError
> > exception wrapped.: psycopg2.errors.GroupingError: column
> > "subnetpools.address_scope_id" must appear in the GROUP BY clause or be
> > used in an aggregate function
> > May 03 18:41:57.893335 np0033933847 neutron-server[90677]: LINE 2:
> > ...standard_attr_id AS floatingips_standard_attr_id, subnetpool...
> > May 03 18:41:57.893335 np0033933847 neutron-server[90677]:
> > ^
> > May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR
> > oslo_db.sqlalchemy.exc_filters Traceback (most recent call last):
> > May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR
> > oslo_db.sqlalchemy.exc_filters File
> > "/usr/local/lib/python3.8/dist-packages/sqlalchemy/engine/base.py", line
> > 1900, in _execute_context
> > May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR
> > oslo_db.sqlalchemy.exc_filters self.dialect.do_execute(
> > May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR
> > oslo_db.sqlalchemy.exc_filters File
> > "/usr/local/lib/python3.8/dist-packages/sqlalchemy/engine/default.py", line
> > 736, in do_execute
> > May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR
> > oslo_db.sqlalchemy.exc_filters cursor.execute(statement, parameters)
> > May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR
> > oslo_db.sqlalchemy.exc_filters psycopg2.errors.GroupingError: column
> > "subnetpools.address_scope_id" must appear in the GROUP BY clause or be
> > used in an aggregate function
> > May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR
> > oslo_db.sqlalchemy.exc_filters LINE 2: ...standard_attr_id AS
> > floatingips_standard_attr_id, subnetpool...
> > May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR
> > oslo_db.sqlalchemy.exc_filters
> > ^
> >
> > From Ironic's point of view, we're wondering if this is expected? Is it
> > likely to be fixed? If there are no plans to fix the DB queries, Ironic
> > will have no choice but to drop the CI job.
> >
> > Thanks in advance!
> >
> > -Julia
> >
> > [0]:
> > https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_291/882164/1/check/ironic-tempest-pxe_ipmitool-postgres/291f2f8/controller/logs/screen-q-svc.txt
> >
>
We have only one postgres related job in our periodic queue neutron-ovn-tempest-postgres-full and it seems to be pretty stable [1]. I don't know however if it somehow skips this path but I don't see any errors like that in the neutron's log file.
--
Slawek Kaplonski
Principal Software Engineer
Red Hat