Wednesday, 2025-08-13

*** mhen_ is now known as mhen01:32
jbernard#startmeeting cinder14:04
opendevmeetMeeting started Wed Aug 13 14:04:14 2025 UTC and is due to finish in 60 minutes.  The chair is jbernard. Information about MeetBot at http://wiki.debian.org/MeetBot.14:04
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:04
opendevmeetThe meeting name has been set to 'cinder'14:04
jbernardjungleboyj rosmaita smcginnis tosky whoami-rajat m5z e0ne geguileo eharney jbernard hemna fabiooliveira yuval tobias-urdin adiare happystacker dosaboy hillpd msaravan sp-bmilanov Luzi sfernand simondodsley: courtesy reminder14:04
jbernard#link https://etherpad.opendev.org/p/cinder-flamingo-meetings14:04
Luzio/14:04
jbernard#topic roll call14:04
mheno/14:04
gireesho/14:04
hillpdo/14:04
pedrovlfo/14:04
jungleboyjo/14:04
toskyo/14:05
vivek__o/14:05
anthonygamboao/14:05
jayaanando/14:06
sp-bmilanovo/14:06
Anoop_Shuklao/14:06
yuvalo-/14:06
hvlcchao1o/14:06
jbernardhello everyone14:07
jbernardi see a nova spec being added to the agenda, while that happens some quick reminders14:08
jbernardMonday, Aug 18 is our midcycle/review session at 1400 UTC (this slot)14:08
jbernard#link https://releases.openstack.org/flamingo/schedule.html14:09
* sp-bmilanov is adding things at the last moment14:09
sp-bmilanov(I can elaborate a bit more when I have the floor)14:10
jbernardsp-bmilanov: sure, go ahead14:10
sp-bmilanovhi, thanks, so we hit a case where, during a live migration of an instance, the OOM killer kills the nova agent at the source, but in just the right moment so that the instance is now running at the destination14:11
sp-bmilanovbut it is not reflected in OpenStack's state14:11
sp-bmilanovand when you boot the instance again, it gets started on the source hypervisor14:12
sp-bmilanovleading to data corruption for the volumes that are attached at both the source and destination14:12
jbernardyikes14:12
sp-bmilanovI've brought this up with Nova, hence the spec, but I was wondering if there is something more we can do to eliminate double-attachments as a whole14:13
sp-bmilanovthe StorPool storage system can force-detach from all but the instance that is being powered on (the linked change), so you don't at least have data corruption14:14
sp-bmilanov(https://review.opendev.org/c/openstack/os-brick/+/940245)14:14
sp-bmilanovwhat I wanted to discuss is does it make sense to generalize this a bit and ship it as something other drivers can implement?14:14
sp-bmilanov(something like an invariant that storage systems, where possible, to check that some invariants hold)14:15
sp-bmilanovok, wrong link -- https://review.opendev.org/c/openstack/os-brick/+/95711714:16
sp-bmilanovand the context in which it can be called -- https://review.opendev.org/c/openstack/nova/+/95711914:17
sp-bmilanovcurrently, it makes a lot of assumptions, might not cover edge cases, etc, but the spirit of the change is "consult the storage system that it's ok to boot"14:18
jbernardthis will certainly require nova's input,14:19
jbernardthe source of the bug is restarting on the source when an instance is in a trasitional state, no?14:19
sp-bmilanovin a transitional state from the PoV of OpenStack, yes, from what I've gathered, the instance was fully migrated on the destination, there was just some bookeeping and cleanup left on the source14:20
jbernardwe support multiattach, so there are at least some cases where eliminating this would not be desired... (im reading as fast as i can, there's quite a bit to think about)14:21
sp-bmilanovyep, no rush, I just wanted to get the idea out there14:21
sp-bmilanovand yes, I am not sure how this will mesh with multi-attach14:21
jbernardsp-bmilanov: if finalizing cleanup is necessary, wouldn't bringing up the instance again on the source be the wrong thing to do?14:22
sp-bmilanovyep, but from what I gathered, a restart was issued, which made OpenStack recreate the instance at the source14:23
sp-bmilanov(there are also discussions to look into maybe adding more obstacles if OpenStack detects that a migration has failed)14:24
sp-bmilanovmore obstacles to get a VM restarted14:24
jbernardbut i would hope a restart on a migrated instance would be able to correct for this case14:24
sp-bmilanovit's a known defect, the source doesn't check if the instance is running on the destination14:24
jbernardim resisitant to adding additional logic to cinder if nova is capable of improving the restart logic (as a general idea)14:25
sp-bmilanov(the spec will aim to address this and maybe describe that the source checking the destination for running instances is the way to go)14:25
jbernardi think the source of the problme is the best place to address it, instead of adding safeguards in cinder to work around it (if possible)14:25
sp-bmilanovmakes sense14:26
jbernardi want to hear nova's take on it14:26
sp-bmilanovI will bring it up again on the Nova weekly next week14:28
jbernardsp-bmilanov: what is the lp bug for this? im not seeing it'14:28
sp-bmilanovhttps://bugs.launchpad.net/nova/+bug/209239114:29
jbernardahh, sean has some comments on the spec, need to look at that closer14:29
jbernardsp-bmilanov: thanks14:29
sp-bmilanovyou're welcome, yes, and https://meetings.opendev.org/irclogs/%23openstack-nova/%23openstack-nova.2025-07-29.log.html https://meetings.opendev.org/irclogs/%23openstack-nova/%23openstack-nova.2025-07-22.log.html14:30
sp-bmilanovI need to update the spec proposal with what we've discussed in the meets, but the focus in the spec is the cleanup enhancement14:31
jbernard#action sp-bmilanov to raise restart/migration issue in nova meeting and report back14:31
jbernardsp-bmilanov: it could be that nova cannot handle it any better, i just want to understand14:32
sp-bmilanovit can, and in that specific case it will solve the issue, but I was wondering if a more general approach would be even better14:32
sp-bmilanovin order to avoid a potential next double-attach-start situation14:33
sp-bmilanov"in that specific case it will solve the issue" it = a potential enhancement to the cleanup14:33
jbernardok, im interested in addressing the immediate issue first14:35
sp-bmilanovack14:35
jbernardim skeptical of solutions in need of problems, but it's certainly something we can dicuss, perhaps you have a reproducer some additional analysis14:36
jbernard#topic open discussion14:37
yuvalhey14:37
yuvalwhen is feature freeze for 2025.2?14:37
jbernardhttps://releases.openstack.org/flamingo/schedule.html#f-ff14:38
yuvaldid I missed it already?14:38
vivek__Hello, 14:38
jbernardR-5 i believe14:38
vivek__https://review.opendev.org/c/openstack/cinder/+/95182914:38
Luzihi i just wanted to know: how is the review state for the image encryption patches? Is there anything we still need to do?14:38
jbernardyuval: not yet14:38
yuval28.8?14:38
LuziAug 25 - Aug 2914:38
jbernardLuzi: i need another core reviewer14:38
anthonygamboaHey everyone, I have what I think is a basic question here but is there detailed documentation on how to modify an existing gerrit merge request submitted by someone else for cinder specifically?  I've checked here https://docs.openstack.org/project-team-guide/review-the-openstack-way.html#modifying-a-change and here https://docs.opendev.org/opendev/infra-manual/latest/developers.html#updating-a-change but con14:39
jayaanandhttps://review.opendev.org/c/openstack/cinder/+/955054 raised patch 10 days back. Please help with review 14:39
jbernardLuzi: i was hoping to get it merged early so that we could address any regressions should they arise, but everyone is quite busy this cycle.  im still hoping to get it merged, ill try to raise it in Monday's meeting14:39
pedrovlffolks we will talk about the https://review.opendev.org/c/openstack/os-brick/+/955379 (agenda) ? 14:39
Luzithank you jbernard 14:40
vivek__Need review for CINDER plugin registration https://review.opendev.org/c/openstack/cinder/+/951829. As I have updated the patch and removed the OS version as it was having GDPR implications. 14:40
jbernardanthonygamboa: merge request, as in: a patch submitted for review?14:41
jbernardanthonygamboa: anyone can update an existing patch, you can use git-review and the author and uploader will then show different values14:42
jbernardanthonygamboa: but it will kindof overwrite someone elses work, so make sure you're being helpful and it's the right action to take14:43
jbernardpedrovlf: sure, what's up?14:44
pedrovlfHi jbernard we would like a review on the that patch we submit cc: hillpd 14:45
hillpdWe found a an issue in os-brick where multiple iSCSI logins per path aren’t handled correctly. The current logic stops after finding the first session. In practice, we found that this can prevent the clean-up of devices configured under other sessions.14:45
jbernardpedrovlf: yes, im aware, i haven't had time to look at it yet14:46
hillpdWe have a proposed fix and were looking for feedback on this solution. Re: https://review.opendev.org/c/openstack/os-brick/+/95537914:46
hillpdokay, thanks14:46
pedrovlfalso we described the full situation on the https://bugs.launchpad.net/os-brick/+bug/211655314:47
jbernardok, the patch may well be in fine shape, it just needs someone with time to take a look14:47
SandipHello Joe, Can you please review this CINDER plugin registration https://review.opendev.org/c/openstack/cinder/+/951829.14:48
jbernardpedrovlf, hillpd: we can raise this in Monday's session14:48
* jungleboyj is looking at that one.14:48
SandipWe have dropped mail regarding previous review comments.14:49
pedrovlfthank you jbernard let us know if you need any other detail 14:49
jbernardyep, i see it, it's in the review queue as well14:49
jbernardSandip: ^14:49
jbernardpedrovlf: ok, thanks for reaching out14:49
vivek__Thanks Joe.14:49
jbernardok, last call for problems, issues, dumpster fires, etc14:54
jbernardgood news is alwasy welcome too :)14:54
jbernardthanks everyone!14:56
jbernard#endmeeting14:56
opendevmeetMeeting ended Wed Aug 13 14:56:30 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2025/cinder.2025-08-13-14.04.html14:56
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2025/cinder.2025-08-13-14.04.txt14:56
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2025/cinder.2025-08-13-14.04.log.html14:56
sp-bmilanovthanks jbernard!14:56
jungleboyjThanks!14:56
hillpdThanks!14:56
anthonygamboajbernard: thank you. I've tried using git review to check out the change and amend the commit but always get an error "commit 38c9d0d: not Signed-off-by author/committer/uploader in message footer." The thing is, commit 38c9d0d is not the current commit, it's one back15:03
anthonygamboaIf I try to sign off on that merge by squashing, I get an error that it is closed and cannot be edited15:04
jbernardanthonygamboa: what is the current commit in that case?15:05
jbernardanthonygamboa: and what is the review number?15:05
anthonygamboaReview number is 869991. Current commit is 1b447e7a8911668fc0062025d045a3cc6f2b66e215:06
jbernardanthonygamboa: this is the hitachi replication patch?15:10
anthonygamboajbernard: yes15:11
jbernardyou're doing something wrong, start with a clean cinder checkout15:11
jbernardand then: git review -d 86999115:11
jbernardyou should very probably not be trying to squash anything15:12
jbernardand do make sure you have permission from the author before you overwrite anything15:12
anthonygamboasure thing, I've already started clean a few times lol15:12
jbernardit worked fine for me15:13
anthonygamboathen just make any change, add it, and amend the current commit to include sign-off?15:14
jbernardyep, that should do it15:14
anthonygamboadid you have to resolve a merge conflict?15:17
jbernardno15:17
jbernardthere is no merge conflict15:17
jbernardthe review command give you the patch15:18
jbernardmake whatever changes15:18
jbernardammend the commit15:18
jbernardpush the changes15:18
jbernardif you're seeing merge conflict, something not right is happening15:18
jbernardthere should be no merge operation at all15:19
jbernardor squashing, etc15:19
anthonygamboaI do changes, amend, git review, and get error:15:19
anthonygamboaAuto-merging releasenotes/notes/hitachi-fix-gad-vol-compatibility-e9c62c18f7a12bc7.yaml CONFLICT (add/add): Merge conflict in releasenotes/notes/hitachi-fix-gad-vol-compatibility-e9c62c18f7a12bc7.yaml error: could not apply ff2ebfef3... Hitachi: Fix to have compatibility of GAD volumes15:19
jbernardcan you paste all of the terminal interaction to a pastebin?15:20
jbernardstart from the beginning15:20
anthonygamboawill do15:20
anthonygamboapastebin was giving me trouble, hope this works: https://justpaste.it/afkyo15:26
jbernardall of the rev-parse/chmod can be omitted, git-review will do that for you15:28
jbernardjust git clone15:28
jbernardgit-review -d15:28
jbernard<make edits>15:28
jbernardgit commit --amend ...15:28
jbernardthere should not be a rebase operation, can you paste your gitconfig?15:29
anthonygamboagit config: https://justpaste.it/emgtb15:31
anthonygamboagot it, I'll try it again with a clean repo15:31
jbernardno, i need to see ~/.gitconfig or ~/.config/git/config15:32
jbernardgit config --list shows the repository configuration, i need to see the command configuration15:32
jbernardif you have some auto-rebase thing happening, that could be the cause of this15:33
jbernardin which case a clean repo will not help15:33
anthonygamboaonly have a ~/.gitconfig file and here's all that's in it: https://justpaste.it/ah3mp15:34
jbernardtry commenting out the [gitreivew] part15:34
jbernardyou shoulnd't need additional configuration15:34
jbernardbeyond just email and name15:34
jbernardi dont understand what is asking git to rebase when you amend a commit, that is unusual15:35
jbernardyeah, i wonder if the remote=origin causes this15:36
jbernardit comes from your git-review command15:37
anthonygamboaI removed the remote origin and all the extra stuff at checkout https://justpaste.it/gj0g415:46
jbernardtry recloning the cinder repo15:47
jbernardnetwork unreachable is a different problem15:48
jbernardbut lets start with a clean repo15:48
jbernardyou have a ssh key setup in the gerrit interface?15:49
jbernardit guess it doesn't matter yet, connect to host fails15:49
jbernardlets see15:50
anthonygamboait's connected before.. yes, ssh set up15:51
anthonygamboanow git review -d is timing out15:51
jbernardsame error?15:51
jbernardok, that's a networking issue likely15:52
jbernardtry this:15:52
jbernardtelnet review.opendev.org 2941815:52
jbernardthat should show you the gerrit-ssh ident string15:52
anthonygamboaTrying 162.253.55.233... Trying 2604:e100:1:0:f816:3eff:fe31:926a... telnet: Unable to connect to remote host: Network is unreachable15:55
anthonygamboayeah, looks like network issue15:55

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