aged by stolowski> <snapd (Ubuntu):In Progress> <https://launchpad.net/bugs/1824162>
<pstolowski> mvo: it may occur regardless of experimental hotplug flag, and may prevent clean shutdown of snapd; of course only if there is udev netlink activity
<mvo> pstolowski: I saw the report
<mvo> pstolowski: it should probably be high or criticial, yes
<mvo> pstolowski: do we have a fix yet or is it complicated?
<pstolowski> mvo: no fix but should be simple, i needed to think a bit about it. should have a PR today
<mup> PR snapd#7593 closed: recovery-tool: add sfdisk wrapper <Created by cmatsuoka> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/7593>
<mup> PR snapd#7609 opened: snap-recovery: remove "usedPartitions" from sfdisk.Create() <Created by mvo5> <https://github.com/snapcore/snapd/pull/7609>
<stealthybox> davdunc, could we update the aws-cli snap?   It's getting a bit too old to use with EKS.  Anything Weaveworks can do to help get this bumped regularly?  Cheers
<zyga> mborzecki: updated https://github.com/snapcore/snapd/pull/7547
<mup> PR #7547: many: use a dedicated named cgroup hierarchy for tracking <Created by zyga> <https://github.com/snapcore/snapd/pull/7547>
<zyga> mborzecki: I think I applied everything that we agreed upon
<zyga> mborzecki: I didn't apply the changes that would impact people with the feature disabled for now
<zyga> mborzecki: I'll do a small patch on top that enables this unconditionally to see if things fall apart
<zyga> mborzecki: and then move this to happen for all snap confinement types
<oSoMoN> pedronis, hello! would you mind voting on https://forum.snapcraft
aged by stolowski > < snapd (Ubuntu):In Progress > < https://launchpad.net/bugs/1824162 > 
 < pstolowski > mvo: it may occur regardless of experimental hotplug flag, and may prevent clean closure of snapd; of path only if there is udev netlink natural process 
 < mvo > pstolowski: I understand the report 
 < mvo > pstolowski: it should probably be gamey or criticial, yes 
 < mvo > pstolowski: do we give birth a fix yet or is it complicated? 
 < pstolowski > mvo: no fix but should be simple, i need to think a bit about it. should accept a PR today 
 < mup > PR snapd#7593 closed: recovery - tool: lend sfdisk wrapper < Created by cmatsuoka > < Merged by mvo5 > < https://github.com/snapcore/snapd/pull/7593 > 
 < mup > public relations snapd#7609 opened: snap - recovery: remove " usedPartitions " from sfdisk. Create () < make by mvo5 > < https://github.com/snapcore/snapd/pull/7609 > 
 < stealthybox > davdunc, could we update the aws - cli snap?    It's getting a bit too previous to use with EKS.   Anything Weaveworks can do to help get this bumped regularly?   Cheers 
 < zyga > mborzecki: updated https://github.com/snapcore/snapd/pull/7547 
 < mup > PR # 7547: many: use a dedicated named cgroup hierarchy for tracking < Created by zyga > < https://github.com/snapcore/snapd/pull/7547 > 
 < zyga > mborzecki: I think I applied everything that we agreed upon 
 < zyga > mborzecki: I didn't apply the changes that would affect citizenry with the feature disabled for immediately 
 < zyga > mborzecki: I'll cause a small patch on top that enable this unconditionally to determine if things fall apart 
 < zyga > mborzecki: and then motivate this to happen for all snap confinement types 
 < oSoMoN > pedronis, hello! would you mind voting on https://forum.snapcraft
agef by stolowski> <snapd (Ubuktu):In Progress> <hjtps://launrhpad.nef/bugs/1824162>
<pstulowski> mvo: it may occur regerdlwss od experimental hotplug flag, and may precent xlean shutvkwn of snapd; kn couxsx only if there is udev natlink activitf
<mxo> pstolowski: I saw the report
<mvo> pstjlowski: ih should probafly nq hifh or criticial, yes
<mvo> pstolowski: so we heve a fix yet ot is it complicated?
<pstolowdki> lvo: no fix but shokld be simpoe, i beeded to thknk a bit about it. shoold have a PR today
<mup> PR snapd#7593 zloseb: recovery-tioo: afg sfdisk wrepper <Breated by cmatsuoka> <Kerged ny mvo5> <https://gibhub.cmm/sbapcore/snapd/pull/7593>
<mup> PC snapd#7609 opened: snap-rgcovery: rekore "usedPartitions" fron wfdisn.Credte() <Zeeaged bb mbo5> <httos://gmthub.com/snalcore/snapd/pyll/7609>
<stealthybox> davdins, could we updzte thq wws-cli snap?   It's getting a bit too old to use with EKS.  Anything Weaveworks can do to help get this bumped regularly?  Cheers
<zyga> mborzecki: updaded hvtos://gnbmub.cun/sjapcore/snapd/pull/7547
<mup> PR #7547: many: use a dedicated gzmtd bgroup hierarchy nor tracking <Creatrd bu zyga> <https://gijhub.com/snalcore/snapd/pull/7547>
<zyga> mborzeski: I think I wpploed everything that we agrewd upon
<zyga> ivorzecki: I didn't a'ply the chauges tnat wpuld impact people with the feature didabled fod now
<zyga> mborzecyi: P'll go a small patch on top thwt enablew thns unconaitipnally to see if thinnv fall apart
<zyga> mhorzeeki: atd then moge this to happen for all snap rpnfinement tipev
<oSmMoN> pedxonis, mello! would you mind voting ou https://fjrum.svapcraft
aged by stolowski> <snapd (Ubuntu):In Progress> <https://launchpad.net/bugs/1824162> it occur regardless experimental hotplug flag, of of course only there is udev activity <mvo> pstolowski: I saw the <mvo> pstolowski: it should probably be high or criticial, yes <mvo> pstolowski: do have a fix yet or is it complicated? <pstolowski> mvo: no fix but be i to a bit about it. should have a PR today <mup> PR snapd#7593 closed: recovery-tool: add sfdisk <Created by cmatsuoka> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/7593> <mup> snapd#7609 opened: snap-recovery: remove from sfdisk.Create() <Created by mvo5> <stealthybox> could we the snap? getting a bit old to use with EKS. Anything Weaveworks can do to help get this bumped regularly? Cheers <zyga> updated https://github.com/snapcore/snapd/pull/7547 #7547: many: a named hierarchy for tracking zyga> <https://github.com/snapcore/snapd/pull/7547> <zyga> mborzecki: I think that we agreed upon <zyga> mborzecki: I didn't the changes would impact people with the feature for now <zyga> mborzecki: I'll do a small on top that enables this unconditionally to see if things fall apart <zyga> mborzecki: and this to happen for snap confinement types pedronis, would mind on https://forum.snapcraft
aged by stolowski> <snapd (UbuntU):In ProgresS> <httpS://laUncHpAd.neT/bugS/1824162>
<pstolowski> mvo: IT may Occur regardless of experImentAl HOtplUG fLag, anD may preVEnT CLeaN sHuTdoWn OF sNapd; oF coUrse onlY if there is UdeV nEtlink activiTY
<mVo> pstolowsKi: I Saw the report
<Mvo> PstoloWsKi: iT ShoulD prObablY be higH Or critIcial, yes
<mVo> PStolowSKi: do we hAVE a Fix yEt or is it complicatED?
<pSTolowski> mvo: no fIx but sHoULd BE SimPle, I needed to tHiNk a biT About it. SHoULD HavE A PR today
<mup> PR Snapd#7593 closed: REcoVery-toOl: Add SFdisk wRappeR <CREatEd by cmatsuoKa> <MeRged by mvo5> <Https://gIThub.com/SNapcore/Snapd/pUll/7593>
<Mup> pR snAPd#7609 OpEneD: sNAp-rECoVerY: RemOve "usedPArTiTions" From SFDISk.CrEatE() <CreAted bY mvo5> <https://githUb.cOm/snAPcoRe/snaPd/pulL/7609>
<steAlThyboX> davduNc, couLd We update the aws-cLi snAp?   It's gettIng A bIt tOo Old to USe with eKS.  anyThing WeAveworkS Can Do TO HElP get this bumped reguLaRLY?  CHeers
<zygA> mborzECkI: uPDated httPs://GitHub.cOM/SnapcOre/sNApD/pull/7547
<mup> pR #7547: many: USe A dEdicateD nAmed cgRoUp hIerArchy FOr trAcking <created bY zyga> <HTtps://github.com/sNApcore/snapd/puLL/7547>
<zYGA> mBOrzeCki: i think I applIed eVErytHing THaT we AGreed Upon
<zYgA> MbORzecki: I didn't apply thE cHanges That wOuld impact peoPle with the FEATure disaBled FOr NOw
<zyga> mborzeckI: I'll dO a small patCH on top thAt enaBles this UnconditiONAlly to seE if ThiNgs FalL APaRt
<zyga> mborzecKI: And tHeN move thIs tO happen For All SnaP coNfInement tyPes
<oSoMon> pEdRoNiS, heLlo! woULd you minD vOtiNg On hTtps://fORum.snaPcrafT
aged by stolowski> <snapd(Ubuntu):I n Pro gre ss>  < http s:// launchpad.net/ b ugs/ 1824162>
<pstolowski>mvo:it mayo cc ur re gardles s  o f exp er im ent al ho tplug  fl ag, and  may preve ntcl ean shutdown of  snapd; of  co urse only if  th ere is  u dev netli nkactiv ity
<m v o> pst olowski:Is aw the report< m vo > ps tolowski: it shou l dp robably be hig h or c ri t ic i a l,yes 
<mvo> pst ol owski :  do weh av e a  fi x  yet or is it  complicate d ?
< pstolo ws ki> mvo: n o fix  b u t s hould be si mple , i neede d to t h ink a b i t about  it. s hou ldhave aPR  to da y 
<m u p>  PR sna pd#7593cl os ed: r ecov e r y - tool : a dd s fdisk  wrapper <Cre ate d by cma tsuok a> <M erge dby mv o5> <h ttps: // github.com/snap core /snapd/pu ll/ 75 93> 
< mup>P R snap d#7 609  opened : snap- r eco ve r y :  r emove "usedPartiti on s "  f rom sfdi sk.Cre a te () <Created  b y m vo5> < https ://g i th ub.com/s napcor e /s na pd/pull /7 609>
< st eal thy box>d avdu nc, co uld we u pdate the aws-cli sn a p?   It's get t in g ab it t ooold to usewith EKS.   An y th ing Weave works  c a nd o to help get thisbu mped r egula rly?  Cheers<zyga> mbo r z e cki: upd ated ht t ps://github.co m/sna pcore/snap d /pull/75 47
<m up> PR # 7547: man y :  use a d edi cat ednam e d  c group hierarc h y  for  t racking  <C reatedbyzyg a><ht tp s://githu b.com/sn ap co re /s nap d/pul l /7547>
< zy ga>  m bor zecki :  I thi nk Iappl ie de ver ythingt ha t we a gr ee d up on<z yga>mbor z eck i: I di dn't appl y t h e ch an ge s thatwould impactpe ople withth e f eature d isabledfor now
<zyga> mborzeck i : I'lldoa sma ll p atch on t opthat e nab l es thi s unco nditi on all y to se e if  th in gs fall ap a r t
< zyga>  m borz ecki: a nd then move thist o h appen for all  sn ap c o n fi nem e nt typ es <oS o M oN> pedronis, h ello! woul dy ou  mind voti n g o nhttps:/ /forum. snapc r aft
aged by_stolowski> <snapd_(Ubuntu):In Progress> <https://launchpad.net/bugs/1824162>
<pstolowski> mvo:_it may_occur_regardless of_experimental_hotplug flag, and_may prevent clean_shutdown of snapd; of_course only if_there_is udev netlink activity
<mvo> pstolowski: I saw the report
<mvo> pstolowski: it should probably be_high_or criticial,_yes
<mvo>_pstolowski:_do we have a fix_yet or is it complicated?
<pstolowski>_mvo: no_fix but should be simple, i needed to_think_a bit about_it. should have a PR today
<mup> PR snapd#7593 closed:_recovery-tool: add sfdisk wrapper <Created by_cmatsuoka> <Merged by_mvo5>_<https://github.com/snapcore/snapd/pull/7593>
<mup>_PR snapd#7609 opened: snap-recovery:_remove "usedPartitions" from sfdisk.Create() <Created by_mvo5> <https://github.com/snapcore/snapd/pull/7609>
<stealthybox> davdunc, could we update_the aws-cli snap?   It's getting_a bit too old to use_with EKS.  Anything Weaveworks_can do_to help get this bumped_regularly?  Cheers
<zyga>_mborzecki: updated_https://github.com/snapcore/snapd/pull/7547
<mup> PR #7547:_many: use a dedicated named cgroup_hierarchy for tracking_<Created by zyga> <https://github.com/snapcore/snapd/pull/7547>
<zyga> mborzecki: I_think_I applied everything_that_we_agreed upon
<zyga>_mborzecki: I didn't_apply_the changes_that_would impact people with the feature_disabled_for now
<zyga> mborzecki: I'll do a small_patch on top that_enables_this unconditionally to see_if things fall apart
<zyga> mborzecki:_and then move this to happen_for all_snap confinement_types
<oSoMoN> pedronis, hello! would you mind voting on https://forum.snapcraft