Wednesday, 2022-06-15

rpittaugood morning ironic! o/06:55
ajyaGood morning, anyone looked at why this job has started failing  - https://zuul.opendev.org/t/openstack/builds?job_name=openstack-tox-py36&project=openstack/sushy-tools ? Before I try to do that.07:34
rpittauajya: it looks like an incompatibility between py3.6 and the coverage version in upper-constraints, not sure we can do much, I'll check if we can cap that in some way07:52
rpittauajya: removing the lower bound breaks the requirements check btw07:53
ajyayes, there is one patch that tries to fix it along with other changes - https://review.opendev.org/c/openstack/sushy-tools/+/844284 07:54
rpittauyep, that needs to be reverted07:55
ajyaI left the comment about it there07:55
rpittauack07:55
ajyaupper-constraints 2 weeks ago removed python3.6 specific line - coverage===6.2;python_version=='3.6'07:59
rpittauajya: coverage removed support for python3.6 in 6.3, upper-constraints now uses 6.4.1, in yoga it was capped to 6.2 for py3.607:59
ajyaafter 6.2 coverage dropped 3.6 support07:59
rpittauyes because they dropped support for py3.607:59
rpittauzed does not support 3.6 at all07:59
ajyayeah, is there any way to fix this in sushy-tools without dropping 3.6.. 07:59
rpittauheh if we need toi keep retro compatibility we have to find a way08:00
rpittaumaybe a custom job08:00
rpittaulet me see, we're not the only project keeping some stuff with py3.608:00
ajyaok, thanks08:00
dtantsurit may be a question for #openstack-requirements08:01
dtantsurwe're not the only ones with branchless projects08:01
rpittaudtantsur: yep, IW as going to ask there :)08:01
dtantsurkeeping in mind, their recommendation may end up dropping 3.6 and capping sushy-tools/vbmc on stable branches08:01
rpittauat some point we'll have to08:02
rpittaumore and more libs are dropping py3.608:02
dtantsuryeah. we may issue the last release and Just Do It08:02
rpittauheh :/08:06
rpittauit goes without saying that removing u-c the tests pass perfectly :/08:39
rpittaudtantsur: ehmmm apparently projects with py36 are using separate py36 constraints, e.g. https://opendev.org/openstack/swift/src/branch/master/py36-constraints.txt08:42
rpittauhow bad do we want to keep py36 support?08:43
dmelladodoes that even work? I couldn't even install on cs808:52
dmelladoso...08:52
dmelladoI'd say burn in hell xD08:52
rpittaualways ready to splash napalm on something08:54
dtantsurrpittau: I don't think keeping sushy-tools or vbmc working on 3.6 is critical.09:37
dtantsurI hoped we could do it.. but if it takes additional effort, rather nope.09:37
rpittaudtantsur: I agree, flamethrower it is then09:37
*** tosky_ is now known as tosky09:42
iurygregoryyay for jetlag (6:48...)09:48
iurygregorymorning Ironic o/09:48
opendevreviewRiccardo Pittau proposed openstack/sushy-tools master: Remove support for Python 3.6 and 3.7  https://review.opendev.org/c/openstack/sushy-tools/+/84591409:52
rpittauhey iurygregory :)09:52
iurygregoryhey hey rpittau =)10:00
opendevreviewRiccardo Pittau proposed openstack/virtualbmc master: Remove support for Python 3.6 and 3.7  https://review.opendev.org/c/openstack/virtualbmc/+/84591510:07
opendevreviewFiona Allen proposed openstack/ironic-inspector master: Removed blacklisted to blocked  https://review.opendev.org/c/openstack/ironic-inspector/+/84591910:41
dtantsurrpittau: do you plan on a couple of releases before we remove the support?11:12
dtantsurso that we can cap the stable branches to them?11:12
dmelladoiurygregory: jetlag is AWESOME11:19
dmelladofor me, getting 'back to east' is the worse ever11:19
dmelladoxD11:19
iurygregorydmellado, NOOOOOOOOO =D11:19
dmelladogetting back from Vancouver was... challenging xD11:20
iurygregoryagree it would be good to pin some releases to support py36/py37 in sushy-tools11:20
dmellado+111:20
iurygregorydmellado, next year you can tell me =P11:20
dmelladolol11:21
dmelladoa release note would be awesome, in any case11:21
rpittaudmellado: I realized I forgot the release note right after the push, I will add them11:33
rpittaudtantsur: yeah, I'll propose releases for both before merging the py36 drop11:34
rpittaueven though if both of them are broken in py3.6 :)11:35
*** tosky_ is now known as tosky11:55
dtantsurrpittau: the code is not broken if used with the right constraints?12:07
rpittaudtantsur: no, I forgot to add "tests" in the phrase12:07
dmelladorpittau: heh, no worries!12:51
opendevreviewDmitry Tantsur proposed openstack/ironic-lib master: Resolve symlinks when comparing device names  https://review.opendev.org/c/openstack/ironic-lib/+/84598613:06
dtantsura good idea that came out of the today's discussion ^^13:06
opendevreviewDmitry Tantsur proposed openstack/ironic-lib master: Resolve symlinks when comparing device names  https://review.opendev.org/c/openstack/ironic-lib/+/84598613:07
dtantsurhmm, I need to think about implications for inspector..13:08
*** tosky__ is now known as tosky13:17
TheJuliao/13:26
TheJuliadtantsur: I don't think device names would change.. but I feel like the unit tests don't really provide a solid view into it13:27
TheJuliatruthfully :(13:27
*** tosky is now known as Guest216913:29
*** tosky__ is now known as tosky13:29
rpittauTheJulia, dtantsur, iurygregory, the issue with swift in the grenade job seems not moving forward, definitely need advice as I doubt it depends on us, please check discussion in https://review.opendev.org/c/openstack/devstack/+/84567513:48
iurygregoryrpittau, ack 13:49
*** tosky__ is now known as tosky13:58
TheJuliarpittau: ugh, yeah https://review.opendev.org/c/openstack/python-swiftclient/+/845157 is goign to be needed13:58
TheJuliahidden usage in python-swiftclient13:59
rpittauoh! thanks TheJulia :)13:59
TheJuliarealistically, they shouldn't have pulled support out13:59
rpittausame thought13:59
TheJuliaat least, before fixing tempurl client support13:59
TheJuliaI can't seem to login right now, andI'm out of spoons to deal with things after traveling13:59
TheJuliaso feel free to copy/paste my thoughts14:00
TheJuliaI can chime in tomorrow, my immediate focus is tryign to get an appt with the eye doctor14:00
rpittauTheJulia: no worries and thanks again, I linked the swiftclient patch to the devstack backport and +1ed it14:01
ameya49iurygregory: Hi! Hope you guys had a good time in Berlin :)14:19
ameya49iurygregory : Requesting to go through few of these patches for review : https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/838462 and https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/843590. Can we please consider these patches for review this week14:22
iurygregoryameya49, Berlin was awesome =)14:24
iurygregorysure I'll add to the list14:24
ameya49Thanks a ton! :)14:24
rpittaugood night! o/16:10
iurygregoryrpioso, hey o/ in the R740 even with latest FW we still see the issue with the clear_job_queue, this is the output we have from redfish https://BMC/redfish/v1/Managers/iDRAC.Embedded.1  https://paste.opendev.org/show/baV3qJJmVCYE3NSutzds/ 16:23
iurygregoryThe attribute Links/Oem/Dell/DellJobService is missing from the resource /redfish/v1/Managers/iDRAC.Embedded.1'16:23
opendevreviewSamuel Zuk proposed openstack/ironic master: First implementation of the Redfish proxy for Ironic node power states.  https://review.opendev.org/c/openstack/ironic/+/84563916:57
rpiosoajya: ^^^ re: clear_job_queue issue reported by iurygregory.17:39
cbouchar_dtantsur: Would you happen to have aarch template file to reference? 18:22
cbouchar_dtantsur: for use as grub.cfg / pxe_config_template_by_arch18:29
cbouchar_dtantsur: I'm asking because 'default' or 'label' is an error in grub. Not sure of substitute if any.  Doing PXE not iPXE BTW. 18:35
jandersrpioso ajya when I added support for verify steps, I put decorators around clear_job_queue, reset_idrac and known_good_state so this will run on any machine with a drac driver: https://review.opendev.org/c/openstack/ironic/+/804032/20/ironic/drivers/modules/drac/management.py. Is it expected to work only on certain iDRAC generations? Should this21:24
janderscode only run conditionally, when Links/Oem/Dell/DellJobService? 21:24
janders(this is further to iurygregory 's earlier comment)21:25
jandersSample error from an iDRAC8 with latest firmware: https://paste.openstack.org/show/bCDEhKlNTsQOY6Z1VhrT/ ( iurygregory likely already shared this with you)21:26
jandersIt would be great to hear your insights rpioso ajya21:27
opendevreviewSteve Baker proposed openstack/metalsmith master: metalsmith list handle missing port  https://review.opendev.org/c/openstack/metalsmith/+/84606721:47
iurygregoryjanders, yeah I'm start to wonder if only iDRAC9 supports clear_job_queue21:56
iurygregorymaybe we should try to add something that would check if we can find the Links/Oem/Dell/DellJobService =(21:57
iurygregoryand if we get this response (ok we can ignore errors when running clear_job_queue)21:58
opendevreviewSteve Baker proposed openstack/ironic master: Allocation candidates prefer matching name  https://review.opendev.org/c/openstack/ironic/+/84585622:33
jandersiurygregory thinking along the same lines - just wondering if verify steps should handle it or the clear_job_queue step specifically. I think the latter, cause it can also be a clean/deploy step so if we fix it in the step itself we will fix it for all the workflows23:30
jandersfor now I am trying to reproduce this on bifrost, having moderate success23:30
iurygregoryjanders, I would say this would need to go in the clear_job_queue directly (like you said, it's also a clean/deploy step)23:31
opendevreviewSteve Baker proposed openstack/ironic master: Docs: replace nova cli calls with openstack  https://review.opendev.org/c/openstack/ironic/+/84607223:41

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