Friday, 2023-06-09

rpittaugood morning ironic! Happy Friday! o/06:28
rpittauJayF: I'll test both changes locally, I like the fix more than the workaround :)06:30
rpittauJayF: my VM was more happy with the removal of the test, but I think the fix works as well, we should keep an eye on postgres too as I'm seeing things like ironic.tests.unit.db.sqlalchemy.test_migrations.TestMigrationsPostgreSQL.test_walk_versions                                    907.52807:39
rpittauI will merge the workaround to speed up CI, then we can see with more runs if the fix does work07:40
opendevreviewMerged openstack/ironic master: Disabling test_upgrade_twice temporarily for CI fix  https://review.opendev.org/c/openstack/ironic/+/88560007:53
opendevreviewJacob Anders proposed openstack/ironic master: [WIP] Prevent MissingAttribute error when supportedApplyTime missing  https://review.opendev.org/c/openstack/ironic/+/88573910:09
iurygregorygood morning Ironic11:29
iurygregorywow great news \o/11:36
iurygregoryhttps://review.opendev.org/c/openstack/ironic/+/885661 does sound interesting also11:38
TheJuliagood morning12:55
iurygregorygood morning TheJulia 13:01
* TheJulia tries to wake up13:25
opendevreviewRiccardo Pittau proposed openstack/ironic master: Add test timout to tox config  https://review.opendev.org/c/openstack/ironic/+/88537214:14
opendevreviewRiccardo Pittau proposed openstack/ironic master: Add test timeout to tox config  https://review.opendev.org/c/openstack/ironic/+/88537214:15
opendevreviewRiccardo Pittau proposed openstack/ironic master: Use tox env variables in coverage tests  https://review.opendev.org/c/openstack/ironic/+/88550714:15
rpittaubye everyone, have a great weekend! o/15:02
opendevreviewRiccardo Pittau proposed openstack/ironic master: Add test timeout to tox config  https://review.opendev.org/c/openstack/ironic/+/88537215:11
ydehi, how do you manage to ensure that the OS you'll boot, when using launch instance in nova, without presetting ports on subnets, will chose the proper netif to boot on ? 16:15
ydefor instance, i have a BM node with 4 ports, one with pxe enabled, nova+ironic+neutron create a port for the VM bound to the pxe one (at least it seems to be the default behavior)16:16
ydebut when the os boots, it choses another netif to do the dhcpclient, and fails to bring up network16:17
ydedo i have to use custom cloud init scripts ? or to preprare cloudimages dedicated for BM nodes ? or i've completly missed something ?16:18
ydethanks a lot16:18
opendevreviewJay Faulkner proposed openstack/ironic master: Ensure upgrade twice test uses two engines  https://review.opendev.org/c/openstack/ironic/+/88566117:57
JayFSo I find myself wondering18:05
JayFwe had that grenade problem where the migration was just sorta hanging in the middle18:05
JayFwhich seems suspiciously similar to the issue we're seeing in unit tests18:05
JayFjust want to ask the question: is my fix just removing test coverage from something actually broken?18:05
JayFthe classic: is the test broken, or is what we are testing broken18:06
iurygregoryI'm asking myself why this is only happening now.. (don't think I saw this problem before) .-.18:07
TheJuliaI think your change is more realistic. One question to wonder is are we actually consuming sqlalchemy 2 right now or not18:07
JayFthat's mostly where I've landed, re: the change more closely reflecting realistic usage18:08
JayFbut I wanted to ask the question specifically in relation to those grenade failure scenarios18:08
clarkbiurygregory: sqla 2.0 affected how locks are done18:10
clarkbI would definitely check sqla 2.0 as the first potential culprit18:10
JayFclarkb: fwiw, we already did extensive testing vs sqla 2.0 so it'd still be net-new18:10
JayFhmmm18:10
JayF1.4.41 installed in my it's-not-reproducing tox environment18:11
clarkbin zuul we had nested context managers doing migrations and the first one would hold a lock preventing the second from operating. That isn't the case here and wasn't the case in 1.x but we had to fix it by unnesting things18:11
* JayF upgrades18:11
TheJuliaclarkb: we have had to do a lot of similar changes18:12
JayF...should deprecation warnings cause tests to fail?18:17
JayFI'm under the understanding that they shouldn't, but I'm seeing thousands of fails under sqla 2.0.518:18
JayFand most of it appears to be engine connect signature changing deprecation warnings18:18
JayFeither way, the migration tests ran under 2.0.5 and didn't freeze (without my fix or the test skip)18:21
JayFso I don't think that's a likely culprit18:21
TheJuliayde: there is a way, I just don't remember it off hand. In some of it is just hte luck of the draw18:21
TheJuliaJayF: presently, yes18:21
JayFyou know the toggle for that, or what doc I'd find it in?18:22
TheJulianot off the top of my head18:23
TheJuliahttps://github.com/openstack/ironic/blob/master/tox.ini#L14 is one18:24
JayFoh, and this is the change we need in oslodb, yeah?18:24
TheJuliabut that can get dropped18:24
TheJuliaI believe there were per-project changes18:24
JayFack; I guess "ensure our unit tests run on sqla 2.0" is something we need to do18:24
TheJuliaWell, I think we did on 2.0.1 or something like that last18:26
JayFyeah, it's going to be obnoxious, I think we're going to have to detect the signature of the method or version of sqla to get rid of the warning18:28
JayFif we need it to work on 1.4.x and 2.x18:28
clarkbJayF: a lot of stuff for 2.0 works in 1.4 too18:31
JayFoh, that's a good point18:31
clarkbthe sqla transition was really well done imo and other libraries/tools should look at it as an example. You shouldn't need to do anyhting magical to make a codebase work with both I don't think18:32
TheJulia1.4.x was also a migration version to force a lot of the 2.0 breaking changes to be weeded out by the user in advance18:37
JayFack; I'll take a look at cleaning these up18:38
JayFI literally think it might be a one line change just somewhere deep18:38
TheJuliayeah18:38
TheJuliamost likely exactly the case18:38
clarkbsqlalchemy is 1.4.41 in upper constraints which I would expect to apply to the unittests but haven't confirmed that18:40
JayFhttps://94ab1cfb489723c43f41-e7ab479a8e7045ace97d02ce1ceb0b42.ssl.cf2.rackcdn.com/885661/3/check/openstack-tox-py39/ddda219/job-output.txt (╯°□°)╯︵ ┻━┻18:41
clarkbthe job logs on those should record what they install18:41
JayFclarkb: yes, that fits my observation, I had to force my local tox venv to run =>2.x18:41
JayFTheJulia: rpittau: ^ my "fix" failed during postgresql migrations :( 18:41
JayFTheJulia: rpittau: I think we have a real bug, somewhere, and the one test getting commented/'fixed' by me just eliminated the easiest reproducer :| 18:42
TheJuliaJayF: you just install it directly18:42
TheJuliainside the venv18:43
TheJuliaor exclude constraints from tox.ini18:43
JayFTheJulia: yeah, that's what I did. `source .tox/py310/bin/activate && pip install --upgrade SQLAlchemy`18:43
* TheJulia gives tox cookies to wake up18:47
TheJuliaUhh, tox, why are you looping hitting futex and getting ETIMEDOUT18:48
TheJuliaand now running18:48
TheJulia    sqlalchemy.exc.SADeprecationWarning: The argument signature for the "ConnectionEvents.engine_connect" event listener has changed as of version 2.0, and conversion for the old argument signature will be removed in a future release.  The new signature is "def engine_connect(conn)"18:49
TheJuliathat should be easy18:49
JayFyeah I'm going to knock it out18:50
JayFespecially if the new sig is in 1.4.x18:50
* JayF doesn't think he can take another day of his brain pointed to unit tests looking for a fix that's hiding18:50
JayFso low hanging fruit sqla migration fixes, yes please18:50
opendevreviewJulia Kreger proposed openstack/ironic master: Fix SQLAlchemy engine connection listener  https://review.opendev.org/c/openstack/ironic/+/88579718:50
JayFor you can eat the low hanging fruit instead lol18:51
TheJuliawell, mgiht already done18:51
TheJuliaOM NOM NOM18:51
TheJuliare-running tests locally18:51
* JayF waits for this to fix our tests /s18:54
TheJuliait wont18:55
TheJuliaand I got it wrong it seems18:55
TheJuliaoh.. wait18:55
TheJuliaengine.events.ConnectionEvents19:00
TheJuliaI'll have to pull down the sqlalchemy code and look at the docs19:19
TheJuliaI've changed it as needed but I'm still getting hit with the error and I don't quite understand why at present19:19
opendevreviewJulia Kreger proposed openstack/ironic master: Fix SQLAlchemy engine connection listener  https://review.opendev.org/c/openstack/ironic/+/88579719:19
ydei have another issue now, which i dont know if its a normal situation or not. when booting instances from nova. i can ping their ip once active, but i cant ssh into them, just as if the ssh service wasnt started on the host. But, if i boot another instance, and flag the "use-config-drive", it works and i can ssh into the box, using my keypair. any idea ?20:07

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