Hi,


Some of you might be aware of this, but tempest jobs in vitrage repo
have been broken for some time (I remember I saw consistent failures
early in this cycle and I'm afraid that the situation hasn't been improved.)

I spent some time to dig into these failures and found out a few problems.
However I'm afraid I can't fix these all with my limited knowledge about vitrage.
# I've helped its project maintenance for some time but I've never looked into
# its implementations quite in detail.
So I'm sharing my observations here hoping someone who know better about it can
look into these.

1. Usage of removed oslo_context.context.RequestContext interfaces
This is the most trivial and can be fixed easily.
https://review.opendev.org/c/openstack/vitrage/+/957004/2/vitrage/api/hooks.py

2. Usage of asyncore modules from pysnmp-lextudio
Recent release of pysnmp-lextudio no longer provides these modules, likely due
to removal of asyncore in Python 3.12 . I was drafting the migration to asyncio
version in https://review.opendev.org/c/openstack/vitrage/+/957004 but learned
simple replacement does not work and we need more careful assessment.
This might be the most tricky problem atm.

3. Some tempest test failures
I can no longer see old CI results, but as far as I'm aware, CI jobs were
blocked by a few tests consistently failing early in this cycle so we may
have to dig into these, too. You may find some tempest tests failures in
https://review.opendev.org/c/openstack/vitrage/+/957004 though I'm unsure
if these are related to broken snmp service, which is caused by incomplete
migration to asyncio (which I described in 2).

I'm adding the tc tag, to notify them of the current status.


Thank you,
Takashi Kajinami


--
Takashi Kajinami
irc: tkajinam
github: https://github.com/kajinamit
launchpad: https://launchpad.net/~kajinamit