Tuesday, 2022-04-26

fzzf[m]hi folks. I use nodepool connect openstack provider. in openstack, nova build instance failed. and nova list show instance is in BUILD state. and I can't delete it.... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/JmBToOhokPkttSFIalLvbSEy)01:00
opendevreviewJorhson Deng proposed openstack/nova master: Reset the instance's task_state to None when the status is error  https://review.opendev.org/c/openstack/nova/+/83899101:33
fzzf[m] * hi folks. I use nodepool connect openstack provider. in openstack, nova build instance failed. and nova list show instance is in BUILD state. and I can't delete it.... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/nhRIVjZthAjNvxgkNkdUczzV)03:28
*** mfo is now known as Guest283205:39
*** mfo_ is now known as mfo05:39
*** amoralej|off is now known as amoralej07:11
UgglaGood morning. o/07:18
bauzasUggla: good morning07:37
gibio/08:31
sean-k-mooneygmann: dansmith care to readd your +w for moving the fips job to c9s https://review.opendev.org/c/openstack/nova/+/831844/708:56
fzzf[m]hi folks. I use nodepool connect openstack provider. nova build instance failed. and nova list show instance is in BUILD state like follow.  I delete it  prompt No server with a name or ID. and in dashboard show have use these two instance, 8 vcpu, 16g memory, openstack is packstack train ,nova is 15.1.1... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/cXVvKGZbhOphiZZcinYshnCe)09:30
opendevreviewBalazs Gibizer proposed openstack/nova stable/train: Reproduce bug 1953359  https://review.opendev.org/c/openstack/nova/+/83935310:30
opendevreviewBalazs Gibizer proposed openstack/nova stable/train: Extend the reproducer for 1953359 and 1952915  https://review.opendev.org/c/openstack/nova/+/83935410:30
opendevreviewBalazs Gibizer proposed openstack/nova stable/train: [rt] Apply migration context for incoming migrations  https://review.opendev.org/c/openstack/nova/+/83935510:30
gibibauzas: I'm not when you clean up the nova meeting agenda but I now added a topic for Open Discussion for this week's meeting11:03
gibi* I'm not sure11:03
sean-k-mooneyartom: by the way while you are fixing revert if you feel like updating https://review.opendev.org/c/openstack/nova/+/750217/2 i would not object. i should really get back to that but have not had the time11:10
opendevreviewAndrew Bonney proposed openstack/nova master: Fix segment-aware scheduling permissions error  https://review.opendev.org/c/openstack/nova/+/83936111:22
sean-k-mooneywoot! just tested cold migration with vdpa on real hardware with my WIP patch and it indeed worked as the func tests said it should11:57
sean-k-mooneyi need to test every thing else and then reivew the logs but this is a good sign11:58
sean-k-mooneyshelve and resize work too12:01
*** dasm|off is now known as dasm12:04
*** amoralej is now known as amoralej|lunch12:05
sean-k-mooneyevacuate works too and the device is correctly released if/when the source host is started after the evac12:09
sean-k-mooneyso that is all the move ops that should work exluding live-migration which qemu does not support12:10
sean-k-mooneyok suspend is broken but that fine that is going to be split into another patch anyway and i am pretty sure i know why that is broken anyway. im using the generic pci device detach function and i shoudl be using the interface detach version since vdpa devices ues the interface not host dev elements like normal sriov vfs12:12
gibisean-k-mooney: nice!12:14
sean-k-mooneyim really happy i was able to more or less prove this out with the functional tests ahead of time12:16
sean-k-mooneyi kindof expected suspend to fail too which is why i wanted to test this on real hardware12:16
Ugglasean-k-mooney, I guess you manage to install ceph on top of Centos Stream. Any hints to fix that: nothing provides "libpython3.6m.so.1.0()(64bit) needed by ceph-mgr-2:16.2.7-0.el8.x86_64"12:25
sean-k-mooneyUggla: how are you isntalling ceph? with the devstack plugin or by hand?12:32
sean-k-mooneyby the way that looks like you are just missin python3-devel12:33
sean-k-mooneyalso are you using centos stream 812:34
sean-k-mooneythat is not supported anymore12:34
Ugglasean-k-mooney, devstack plugin (from manila local.conf example : https://docs.openstack.org/manila/latest/_downloads/e31f39ce83daac60c4348fde522cee1e/cephfs_local.conf)12:34
sean-k-mooneyyou should be using centos stream 912:34
sean-k-mooneyopenstack nolonger support python 3.612:34
Ugglasean-k-mooney, it is a stream912:34
sean-k-mooneylibpython3.6 is python 3.612:34
sean-k-mooneycentos stream 9 uses 3.912:35
Ugglafor anyreason it seems the plugin is trying to install a pkg from centos 812:35
UgglaProblem: package ceph-2:16.2.7-0.el8.x86_64 requires ceph-mgr = 2:16.2.7-0.el8  but it is clearly a stream 9. I'm gonna have a look where the ceph package comes from.12:37
sean-k-mooneyi dont think they have added centos stream 9 support to the devstack plugin yet12:38
sean-k-mooneyjust looking at the code12:38
sean-k-mooneyi was using ubutnu 20.04 for my ceph testing12:38
sean-k-mooneyyou can set CEPH_CONTAINERIZED=True in your local.conf12:39
sean-k-mooneythat might fix the issue for you12:39
Ugglasean-k-mooney, it install this repo : https://download.ceph.com/rpm-pacific/el8/$basearch12:39
sean-k-mooneyyes12:40
sean-k-mooneyhttps://opendev.org/openstack/devstack-plugin-ceph/src/branch/master/devstack/lib/ceph#L3112:40
sean-k-mooneythat is contolled by  that ^12:40
sean-k-mooneyUggla: you should have hit this check https://opendev.org/openstack/devstack-plugin-ceph/src/branch/master/devstack/lib/ceph#L271-L2812:41
sean-k-mooneyyou ar enot running a supported os12:41
Ugglasean-k-mooney, yep I had to add FORCE_CEPH_INSTALL=yes12:43
sean-k-mooneyya that is why this is failing12:43
sean-k-mooneyso the repo config is contoled by https://opendev.org/openstack/devstack-plugin-ceph/src/branch/master/devstack/lib/ceph#L913-L94312:43
bauzasgibi: ack, thanks12:43
sean-k-mooneyUggla: that is currently hardcoded to el812:44
sean-k-mooneyhttps://opendev.org/openstack/devstack-plugin-ceph/src/branch/master/devstack/lib/ceph#L114412:44
Ugglasean-k-mooney, yep but in the repo there is no el9.12:44
sean-k-mooneyya i see that12:45
Ugglasean-k-mooney, CEPH_CONTAINERIZED=True, will install ceph in a container ?12:46
sean-k-mooneyyep12:46
sean-k-mooneyhttps://opendev.org/openstack/devstack-plugin-ceph/src/branch/master/devstack/lib/ceph#L157-L17412:46
Ugglasean-k-mooney, do you think it will work ?12:47
sean-k-mooneyso it will install ceph in a container and dinstall just the ceph client on the host form ceph_common12:47
Ugglasean-k-mooney, I'm going to try...12:47
sean-k-mooneyi think it will be the only way to install ceph currently on centos 9 stream12:47
sean-k-mooneyUggla: they are currently in the process or rewriting this plugin to use cephadm by the way12:48
sean-k-mooneythat might add centos 9 support as a result12:48
Ugglasean-k-mooney, centos stream9 is currently a bit too more bleeding edge. :)12:49
sean-k-mooneythat is generally not a good thing12:49
sean-k-mooneyam so the way to work around this for centos 9 stream would be to use ceph form disto packages instead fo from upstream ceph12:49
sean-k-mooneyhttps://buildlogs.centos.org/centos/9-stream/storage/x86_64/ceph-quincy/12:49
Ugglasean-k-mooney, require docker of course any preference in between docker or podman ?12:50
sean-k-mooneyit will install it12:51
sean-k-mooneyit will use docker12:52
sean-k-mooneythe simplest thing to do might be to implemtn centos 9 stream support int he plugin12:52
Ugglasean-k-mooney, I don't really like your "simplest" solution. :D12:53
sean-k-mooneyUggla: well we all maintian devstack together :) but ill talk to the devstack/qa folk and see if i can find time to add centos 9 support12:55
sean-k-mooneyUggla: must people dont use centos by the way12:55
sean-k-mooneyso if a feature does not work on centos it generally falls to use to add it if we want to use it12:56
Ugglasean-k-mooney, I was kidding. That could be an interesting thing to do and learn. But not the simplest I think.12:57
Ugglasean-k-mooney, at least for me.12:57
sean-k-mooneytry usign it form contianer for now12:59
sean-k-mooneymanilla does not strictly need ceph and you do not need ceph for your manilla share work13:00
sean-k-mooneyso you can go back to just using cinder lvm for now until you ahve the basic supprot working13:00
sean-k-mooneyand look at using ceph later13:00
sean-k-mooneyi.e. deploy manila with cinder lvm and use nfs shares initally13:01
sean-k-mooneythen when we figure out how to deploy ceph on centos 9 and add supprot to devstack we can then extend the nova supprot to work with cephfs although   that really should not need much code change in nova just mounting the share13:02
Ugglasean-k-mooney, yes and no. So for I focus on NFS. There are still things to fix but it seems I manage to mount the share into the VM using virtiofs + NFS.13:03
Ugglasean-k-mooney, I wanted to do the same for CEPHFS. 13:03
sean-k-mooneyack13:04
Ugglasean-k-mooney, and yes from nova perspective, that sounds like not a major change.13:05
Ugglasean-k-mooney, however I'm not blocked.13:06
fzzf[m]> <@fzzfh:matrix.org> hi folks. I use nodepool connect openstack provider. nova build instance failed. and nova list show instance is in BUILD state like follow.  I delete it  prompt No server with a name or ID. and in dashboard show have use these two instance, 8 vcpu, 16g memory, openstack is packstack train ,nova is 15.1.1... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/oDINtdoeiJnrakEWVAWwmwho)13:11
*** amoralej|lunch is now known as amoralej13:15
* Uggla root@demo2:/nene# mount | grep virtiofs13:39
Uggla44bf4c5e-b6ae-463d-9ed2-3d0177c1ee80 on /nene type virtiofs (rw,relatime)   \o/ (I still have to fix stuff, but that's a milestone for me)13:39
artom*snerk* /nene13:41
bauzasgibi: good idea of creating an etherpad for https://etherpad.opendev.org/p/nova-bug-triage-2022041914:05
bauzasgibi: do you want to discuss about this on the meeting ?14:05
gibibauzas: I planned to link that to on the meeting for reference14:44
bauzasok14:44
gibibauzas: and I will ask if we want to make it a mail or keep it an etherpad14:45
bauzasmho is that etherpad is just enough14:45
gibiyeah I'm OK with this being a pads14:47
*** lbragstad8 is now known as lbragstad15:05
bauzasgentle reminder : nova meeting in 45 mins by now here at #openstack-nova15:16
*** xek_ is now known as xek15:23
opendevreviewribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (db)  https://review.opendev.org/c/openstack/nova/+/83119315:30
opendevreviewribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (manila abstraction)  https://review.opendev.org/c/openstack/nova/+/83119415:30
opendevreviewribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (drivers)  https://review.opendev.org/c/openstack/nova/+/83309015:30
opendevreviewribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (api)  https://review.opendev.org/c/openstack/nova/+/83683015:30
opendevreviewribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs (objects)  https://review.opendev.org/c/openstack/nova/+/83940115:30
bauzasUggla: bravo ^15:40
* bauzas needs to do a review round15:40
Ugglabauzas, still work to do... but I'm slowly progressing. ;)15:41
gibiUggla: it is not slow at all :D15:42
gibithis is a major feature15:42
bauzasgibi: I may need to leave at 6:30pm our time, ie. 30 mins after the beginning of the meeting15:50
bauzasgibi: are you ok if I can pass you the meeting baton if I need to quit ?15:51
gibisure I can take it15:52
Ugglagibi, thanks to reassure me.15:58
bauzasgibi: thanks15:59
bauzasgosh, forgot the 2nd reminder for the meeting15:59
bauzastoo late15:59
bauzas#startmeeting nova16:00
opendevmeetMeeting started Tue Apr 26 16:00:04 2022 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'nova'16:00
gibio/16:00
bauzasehlo compute-ers16:00
bauzas#link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting16:00
Ugglao/16:01
elodilleso/16:01
bauzasokay, let's start, people could come, once they're undragged from some internal big meeting :)16:03
gmanno/16:03
bauzas #topic Bugs (stuck/critical) 16:03
bauzasdamn16:03
bauzas#topic Bugs (stuck/critical) 16:03
bauzas#info No Critical bug16:03
bauzas#link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 28 new untriaged bugs (-7 since the last meeting)16:03
bauzaskudos to gibi for this hard work16:03
bauzas#link https://storyboard.openstack.org/#!/project/openstack/placement 26 open stories (0 since the last meeting) in Storyboard for Placement 16:03
bauzas#info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster16:04
bauzasgibi: wanted to discuss about the bugs you triaged before we look at next week bug baton owner ?16:04
gibijust a small link16:04
gibihttps://etherpad.opendev.org/p/nova-bug-triage-2022041916:04
gibiI collected the triaged bugs here16:04
gibiI think the only interesting information is the bugs in triaged state without assignee16:04
bauzasas I said before, this is a good idea to keep some references, mostly about the incomplete 16:05
gibiwe have one this week16:05
gibi    [Needs Assignee] Concurrent migration of vms with the same multiattach volume fails https://bugs.launchpad.net/nova/+bug/196864516:05
bauzaswell, we have around 950 open bugs16:05
gibiyeah, but at least this is a fresh one :)16:05
gibiprobably the reporter is still around if we have questions :)16:05
bauzasgibi: what we could agree on is to find some volunteer for only high bugs that just got triaged16:06
gibiI think it is worth to advertise these bugs but I agree that we don't have to forcefully assign it16:06
bauzassounds a low hanging fruit 16:06
bauzasif this is about adding a retry loop16:07
gibiyeah, it does not seem super hard16:07
gibiyepp it is a retry loop16:07
gibifor cinder attachment create16:07
gibianyhow we can move on :)16:07
gibiI'm ready to pass the baton16:08
bauzasgibi: I'll then add the low-hanging-fruit tag16:08
gibibauzas: works of me16:08
bauzasthis may help16:08
gibi*for16:09
bauzasgibi: nah, it worked *of* you as you proposed the solution :)16:10
bauzasanyway, this leads to the last point16:10
bauzasmelwitt: around ?16:10
melwittyes16:11
bauzasmelwitt: you're next in the bug triage roster16:11
bauzasmelwitt: do you feel brave enough to get the bug baton ?16:11
melwittbauzas: haha, yes. sounds cool16:12
bauzasas a reminder for everyone, this baton doesn't imply any matter of ownership or responsibility16:12
bauzasanyone wanting to help is welcome, based on his or her free time16:12
bauzasand others may help if they want16:13
bauzasmelwitt: which leads to me saying you can ping me if you need help for upstream triage16:13
melwittcool, thanks16:13
bauzas#info Next bug baton is passed to melwitt16:13
bauzasmelwitt: thanks, very much appreciated16:13
bauzasnext topic then,16:13
bauzas#topic Gate status 16:14
bauzas#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:14
bauzas#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:14
bauzas#link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status 16:14
bauzas#link https://zuul.opendev.org/t/openstack/builds?job_name=nova-emulation&pipeline=periodic-weekly&skip=0 Emulation periodic job runs16:14
bauzas#info Please look at the gate failures and file a bug report with the gate-failure tag.16:14
bauzasthat's been a while we got a new gate failure16:14
gibiI saw some intermittent one but had not time to dig in16:15
gmannfor centos-8-stream, non voting job is failing 100% now. 16:15
gmannAs testing runtime for Zed is centos-9-stream and in QA we agreed to drop the c8s support in devstack as well as in Tempest, I have proposed the changes there and will notify it on ML also. also moving c8s job to c9s, please review it - https://review.opendev.org/c/openstack/nova/+/83927516:15
bauzasthanks gmann16:15
gmannthis series #link https://review.opendev.org/q/topic:drop-c8s-testing16:15
bauzasgmann: on my list, will vote on it later today or tomorrow16:16
gmannthanks, meanwhile I will get tempest depends-on merge16:16
bauzascool16:17
bauzasI have to sit down and consider all the implications but your patch seems good to me16:17
bauzasand either way, ship is sailed16:17
bauzascentos9 is targeted for zed16:17
gmannyeah16:17
bauzasdo we have any tracking LP bug about the centos8 failures ?16:18
bauzasideally, I'd want those to be wontfix if we decide we move on16:18
gmannno bug as of now, we are going as per the testing runtime. and as we drop the py36 from projects then it is broken like for nova as of now16:19
bauzasok16:19
bauzasthen no paperwork to fill in16:19
gmannit is failing as in nova we made nova require >=py3.8 and other projects will do the same16:19
bauzas:)16:19
bauzasoh16:19
bauzasright16:19
bauzasanyway, I guess we can continue16:20
gmannyeah16:20
bauzas#info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures16:21
bauzasjust as a weekly periodic reminder (which includes me, stupid bias)16:21
bauzasnext topic,16:21
bauzas#topic Release Planning 16:21
bauzas#link https://releases.openstack.org/zed/schedule.html16:22
bauzas#info Zed-1 is due in 3 weeks16:22
bauzastick-tock16:22
artom♫ on the clock ♫16:22
* melwitt knows the reference and feels embarrassed :)16:22
bauzasI said last week I should ask this week for a spec review day, but do people feel good about considering it for in two weeks ?16:23
gibibah, I have to allocate  some time to the placement PCI tracking spec16:23
artomNo shame, those pop songs are earworms by design16:23
bauzasartom: but the party don't stop16:23
artomgibi, you have sean-k-mooney's original spec to work from, so not starting from scratch16:23
gibiartom: true true16:24
* bauzas appreciates the english grammar mistake, btw.16:24
gibibauzas: I'm OK to have a review day next week or the week after16:24
melwitt:)16:24
bauzasgibi: I have to write some spec for deprecating the keypair generation, you know16:24
bauzasso16:24
gibi:)16:24
bauzasmaybe saying a spec review day not next tuesday, but tuesday after that ?16:25
bauzasie. May 10th ?16:25
sean-k-mooneythe 10 ya that would be ok i think16:25
bauzasI see no objections16:26
gibigood for me16:26
bauzas#agreed first spec review day will happen on May 10th, bauzas to communicate thru the mailing list16:26
bauzasthis leaves 2 weeks for people writing specs, you are warned16:27
bauzas(again, this includes me)16:27
* gibi feels warned16:27
* bauzas feels gibi overfeels more than he should :)16:27
bauzaswe'll have another round of spec reviews, as we agreed last PTG, either way16:28
bauzasok, next 16:28
bauzas#topic Review priorities 16:29
bauzas#link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+label:Review-Priority%252B116:29
bauzasthe vIOMMU change probably needs paperwork16:29
bauzastl;dr: https://review.opendev.org/c/openstack/nova/+/830646 requires at least a blueprint, and maybe a spec16:30
sean-k-mooneyya i started to review it i kind of think it shoudl have a mini spec16:30
melwitt+116:30
bauzasI can use my hammer16:31
bauzasbut I could soften it 16:31
bauzasexplaining we require a blueprint and some discussion at a nova meeting before we can pursue reviewing it16:31
bauzasricolin: are you around ?16:31
sean-k-mooneyim not againt the proposaly in fact i have wanted to add supprot for a while but we need to agree on the extra_specs/image propeties and define the scope16:32
sean-k-mooneyi was recommening keeping it small for now16:32
bauzasyeah, and that's why we need a debate 16:32
bauzasnot about which paper stamp we should use16:32
sean-k-mooneythere is viommu supprot with the limited chagne required for there acclerator to work16:33
bauzasbut whether we all agree on the design16:33
sean-k-mooneyand then there is full supprot with security and isolation16:33
bauzascorrect, that's why we need to discuss this correctly and address the design scope16:33
sean-k-mooneyi would suggest we split it like that and only do the former this cycle16:33
bauzassean-k-mooney: well, we need a owner, at first :)16:34
bauzaseven if we agree on the direction, we need gears16:34
sean-k-mooneyyep mnaser also expressed interest. im not sure that stephenfin will work on it this cycle16:34
bauzasI'm sure stephenfin said he was okay to leave it for others to continue :)16:35
bauzashence the gerrit hammer16:35
bauzasthis may help people to react and assign some time for this16:35
bauzasI'll also drop the review-prio flag which is meaningless in this case as we can't merge it as it is16:36
bauzasok, moving on if nobody yells16:37
bauzas#topic Stable Branches 16:38
bauzaselodilles: your turn16:38
elodilles#info ussuri and older branches are blocked until 'l-c drop' patches merge - https://review.opendev.org/q/I514f6b337ffefef90a0ce9ab0b4afd083caa277e16:38
elodilles#info other branches should be OK16:38
elodilles#info nova projects' stable/victoria transitioned to Extended Maintenance - no further releases will be produced from victoria, but branch remains open to accept bug fixes16:38
elodillesand that's all I think ^^^16:38
melwittwe need second core wink wink16:39
elodilles:]16:39
gibiI would be happy to approve... ;)16:39
gibi(has some blocked train backports :D)16:39
bauzasI can do things16:40
bauzasmy brain fsck'd me 16:40
gibibauzas: ask elodilles to add me into the stable-core group16:40
gibithen I can help16:40
bauzasgibi: I think we said at the PTG I should propose your name against the stable team16:40
gibiyeah I think so16:41
gibiso lets do it :D16:41
bauzasso,16:41
bauzas#1 I'll do my homework and review such l-c patches16:41
bauzas#2 I'll do my duty and engage discussions about reconciling the nova team and the nova-stable team in some intelligent manner16:41
bauzaslast topic in the agenda,16:43
bauzas#topic Open discussion 16:43
bauzas(gibi) Allow claiming PCI PF if child VF is unavailable https://review.opendev.org/c/openstack/nova/+/838555 16:43
bauzasgibi: take the mic16:43
gibithanks16:43
gibiso16:43
gibiit is a bug16:43
gibiwe saw DB inconsistencies at customers 16:43
gibithe pci_devices table contains available PF and unavailable children VF rows16:44
gibithis basically an impossible situation16:44
gibithe VF should be available if the PF is available 16:44
gibior the VF should be allocated16:45
gibianyhow16:45
gibiI propsed a fix https://review.opendev.org/c/openstack/nova/+/83855516:45
gibiit removes some of the strictness of the state check during the PCI claim16:45
gibibasically allows allocating the available PF if the children VFs are unavailable16:45
gibithis would heal the inconsistent DB state16:46
gibiartom had a good point in the review16:46
gibithat we tend to handle DB healing via nova-manage CLI instead16:46
bauzasnot true16:46
sean-k-mooney we heal some things on object load form the db16:46
bauzaswe had db healing made thru data migrations16:47
artomRight, but those fixes are from "we had thing X a long time ago, and it might still be in the DB, so now when we load it we convert to thing X"16:47
sean-k-mooneywe do have the heal allcoation type commands but i think healing this on agent start is the right thing16:47
bauzaswe only heal things thru the CLI if this is for example something due to some relationship between two DBs16:48
artomvs examples like placement-audit and Lee's connection_info update16:48
sean-k-mooneyas we are also fixing the in memroy representation 16:48
bauzassean-k-mooney: correct, because two DBs were involved16:48
artomMy other point was - the DB somehow got into an inconsistent state, wouldn't it be wiser to at least let the operator know, vs siltently fixing it?16:48
bauzasin the case of placement audit, this was about reconciling two datastores kept from two different projects16:48
sean-k-mooneyartom: i dont think so16:49
bauzasI agree with sean-k-mooney16:49
bauzaswe could log such thing16:49
sean-k-mooneyartom: i think this happened beacue of how the custoemr recreated the compute node after the hdd died16:49
bauzasbut no need to claim it loud16:49
artomOK :) Not a hill I want to die on, but wanted to at least raise the question16:49
gibiI've added a WARNING log in the patch16:49
sean-k-mooneyi dont think this is something that most operators would hit16:49
artomSeems like I'm outnumbered :)16:49
bauzasartom: I won't ask you how many divisions you have16:50
gibisean-k-mooney: one more thing, you said it should be fixed at agent restart. Now my patch fixes it during PCI claim16:50
artombauzas, divisions o_O?16:50
bauzasgibi: I like the pci claim approach 16:50
sean-k-mooneyi have not reviewd the third patch yet16:51
gibisean-k-mooney: and I have a separate patch for the agent restart + remove VF + inconsistent state case16:51
gibisean-k-mooney: ahh, OK, let me know you opininon once you reviewed it16:51
bauzasartom: sorry, I'll DM you the reference :)16:51
sean-k-mooneyack we can proceed on the gerrit review16:51
artomIt's going to be an obscure French thing, isn't it :P16:51
gibiartom, sean-k-mooney, bauzas: thanks, we can move on16:52
bauzas++16:52
bauzassounds we got a consensus : review gibi's patch16:52
gibiI will comment on the patch linking to the meeting logs16:52
bauzas#agreed let's continue to review gibi's work with pci claims fixing the inconstitency16:53
bauzasthat's all we had for the meeting16:53
bauzasany last minute item people wanna raise ?16:53
bauzaslooks not,16:54
gibi-16:54
bauzasthanks all !16:54
gibithanks!16:54
bauzas#endmeeting16:54
opendevmeetMeeting ended Tue Apr 26 16:54:46 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:54
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2022/nova.2022-04-26-16.00.html16:54
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2022/nova.2022-04-26-16.00.txt16:54
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2022/nova.2022-04-26-16.00.log.html16:54
elodillesthanks o/16:54
gibibauzas: I hope you did not forget to leave around 18:30 :)16:54
bauzasgibi: well, I chose to stay :)16:55
artomHe replaced himself with a very small shellscript16:55
bauzasSophie will stare at me when I go off the office room16:55
artomTurns out we was getting bash'ed this whole time16:56
gibiartom: lol16:56
bauzasartom: I wish I could16:56
bauzasartom: but I've been told any IA bot turns crazy after you let people discussing with it16:57
gibiit is our, humans, fault to make AI bots crazy16:58
artomSo we're to AIs what demons are to us, The Corruptors?16:58
sean-k-mooneylol16:58
sean-k-mooneybut yes16:58
gibiat least the naming sounds badass16:58
artom"I'm a Corruptor" "What does that mean?" "Oh I make chatbots says rude words and stuff"16:59
* bauzas leaves by now17:02
bauzasor I could sleep on the couch17:02
opendevreviewMerged openstack/nova master: Move centos stream testing to centos-9-stream  https://review.opendev.org/c/openstack/nova/+/83927520:36
melwittbauzas: could you also add https://review.opendev.org/c/openstack/nova/+/821348 to your stable review list please? the -2 from zuul is bc I accidentally voted on it earlier21:15
*** dasm is now known as dasm|off21:40

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