Friday, 2022-08-19

*** dmellado_ is now known as dmellado00:10
*** dmellado_ is now known as dmellado02:14
*** dmellado_ is now known as dmellado02:47
*** soniya29 is now known as soniya29|ruck05:11
*** soniya29|ruck is now known as soniya29|ruck|afk07:03
*** soniya29|ruck|afk is now known as soniya29|ruck07:38
*** soniya29|ruck is now known as soniya29|ruck|lunch08:00
*** jpena|off is now known as jpena08:33
*** soniya29|ruck|lunch is now known as soniya29|ruck08:47
*** dmellado_ is now known as dmellado09:03
kopecmartinarxcruz: tosky gates in tempestconf working now -> https://review.opendev.org/c/openinfra/python-tempestconf/+/85351710:57
opendevreviewVadym Markov proposed openstack/devstack stable/victoria: Use proper sed separator for paths  https://review.opendev.org/c/openstack/devstack/+/85375611:34
*** dmellado_ is now known as dmellado11:44
*** tosky is now known as Guest53212:51
*** tosky_ is now known as tosky12:51
efoleyHi, I'm looking for help to get the ``telemetry-dsvm-integration-centos-8s`` job fixed for stable branches on aodh, ceilometer, etc. Here's my attempt to fix it: https://review.opendev.org/c/openstack/ceilometer/+/853668, the same type of error is present across backports on stable branches in ceilometer, aodh (perhaps others, I don't want to rerun them all to get new logs). Anyone have any pointers?13:02
*** dmellado_ is now known as dmellado13:20
kopecmartinhi efoley, i'm checking this https://review.opendev.org/c/openstack/ceilometer/+/852878/ , the jsonschmea version issue might be related to py3.6 , i vaguely remember seeing that issue before we dropped py3.6 and 3.713:31
kopecmartinregarding the issue on cs9, it looks like pip is not installed, a package like python39-pip (or something like that) should help13:32
efoleykopecmartin: I'm seeing similar issues on multiple stable branches (versions are not resolvable for different packages each time). The constraints file that is being used for tempest is master, which is what I was trying to solve for. 13:36
efoleyhttps://review.opendev.org/c/openstack/aodh/+/845197 (yoga) and https://review.opendev.org/c/openstack/aodh/+/837053 (xena) show issues with oslo.log.13:38
opendevreviewDan Smith proposed openstack/tempest master: Allow free-form image import parameters  https://review.opendev.org/c/openstack/tempest/+/85260713:42
opendevreviewDan Smith proposed openstack/tempest master: Add testing for glance-download import method  https://review.opendev.org/c/openstack/tempest/+/85260813:42
*** jpena is now known as jpena|off13:45
kopecmartinefoley: oh, i see, maybe override-checkout will help, i noticed that that the job doesn't have that https://opendev.org/openstack/telemetry-tempest-plugin/src/branch/master/.zuul.yaml#L147 however our jobs for older releases do https://opendev.org/openstack/tempest/src/branch/master/zuul.d/stable-jobs.yaml#L514:48
efoleykopecmartin: Thanks for the pointer, I'll take a look. These issues are blocking all backports to telemetry projects.14:54
efoleymartinkopec: IIUC, I should add a new job per stable branch, each with a different name and value for override-checkout?14:57
efoleyThen on each of the stable branches, update zuul.yaml to user the -<branch> job instead of the one currently being used?14:58
kopecmartinefoley: yes, the override_checkout defines branch or tag , e.g. it'll tell devstack to checkout to wallaby and thus install wallaby release of openstack 15:35
kopecmartinhttps://zuul-ci.org/docs/zuul/latest/job-content.html#var-zuul.override_checkout15:35
efoleyIt looks like we're not doing that at all for the telemetry-dvsm-integration-centos-8s jobs. :/ Does that mean we've been testing all these against master every time? Oh dear 15:42
kopecmartinefoley: i think so15:48
efoleykopecmartin: Looks like the expected versions are checked out before override-checkout.16:00
efoleyhttps://zuul.opendev.org/t/openstack/build/286857c33215435d9a315fce53c6eecd/log/job-output.txt#20816:00
efoleySo that might not be the issue. 16:00
kopecmartini'm always confused with these errors, so tempest requires cliff>=2.8.0 while it can't be 2.9.0 and the constraint limits us to version 4.0.0 which should be ok with tempest, so what's the issue? ah16:12
efoleyMaybe it's python36 that's the issue. cliff 4.0.0 might be python>=3716:15
kopecmartinefoley: you're right16:16
kopecmartinhttps://pypi.org/project/cliff/16:16
efoleyI'm making my way towards that. I think I'll need to pin the tempest version, but my attempt in PS2 was doing it incorrectly. I'm testing an update now16:17
efoleyI might end up with a  -yoga-and-below job, or one more appropriately named for the python-version.16:17
efoleyI'll try to test overriding the tempest constraints. Will probably hit more issues, but the solution feels like it's getting closer16:19
efoleyI also mispelled TEMPEST_VENV_UPPER_CONSTRAINTS.16:29
efoley5th time's the charm, looks like cliff was successfully installed this time!16:56
efoleykopecmartin: thanks for your time!16:57
efoleySpoke too soon, still failing. I need to do a bit more investigation, and maybe set a new TEMPEST_BRANCH variable.17:33

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!