<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:10:54 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-7668] permanently remove deactivated OSTs from configuration log</title>
                <link>https://jira.whamcloud.com/browse/LU-7668</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;When an OST is permanently removed from the filesystem, the current process is to store a conf_param that marks the OSC permanently inactive in the configuration log, but it doesn&apos;t remove the actual OSC records from the config llog.  That is needed for clients already mounting the filesystem so that they don&apos;t wait for the OST to be recovered, since only new records added to the end of config llog are processed by already-mounted clients.&lt;/p&gt;

&lt;p&gt;However, for clients newly mounting the filesystem it may be desirable, if the OST is permanently deleted, to remove the OST record from the configuration log completely so that new client mounts don&apos;t even try to connect to it.  This can be done relatively easily by cancelling the llog record(s) for the removed OST(s) so that the client doesn&apos;t process them at all.&lt;/p&gt;

&lt;p&gt;The other area that may need fixing is &lt;tt&gt;lfs df&lt;/tt&gt;, since it currently iterates over OST and MDT indices sequentially until it gets a &lt;tt&gt;-ENODEV&lt;/tt&gt; return code that indicates no more OST/MDT devices are available.  This will result in temporarily inactive OSTs to be printed, since the admin should know when there are offline OSTs, but it should not result in unconfigured OSTs being printed.  It looks like &lt;tt&gt;-EAGAIN&lt;/tt&gt; being returned from &lt;tt&gt;IOC_OBD_STATFS&lt;/tt&gt; will result in the OST/MDT being silently skipped as we would want in this case.  This needs to be verified.&lt;/p&gt;

&lt;p&gt;It looks like &lt;tt&gt;lov_iocontrol()&lt;/tt&gt; is returning &lt;tt&gt;-EAGAIN&lt;/tt&gt; correctly, but &lt;tt&gt;lmv_iocontrol()&lt;/tt&gt; is incorrectly returning &lt;tt&gt;-ENODATA&lt;/tt&gt; for tgt == NULL instead of &lt;tt&gt;-EAGAIN&lt;/tt&gt;, and not handling the &lt;tt&gt;OBD_STATFS_NODELAY&lt;/tt&gt; flag in &lt;tt&gt;uarg&lt;/tt&gt; at all.&lt;/p&gt;</description>
                <environment></environment>
        <key id="34119">LU-7668</key>
            <summary>permanently remove deactivated OSTs from configuration log</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="sthiell">Stephane Thiell</assignee>
                                    <reporter username="adilger">Andreas Dilger</reporter>
                        <labels>
                    </labels>
                <created>Thu, 14 Jan 2016 18:46:25 +0000</created>
                <updated>Sun, 19 Nov 2023 00:24:43 +0000</updated>
                            <resolved>Fri, 12 Aug 2022 22:02:28 +0000</resolved>
                                                    <fixVersion>Lustre 2.16.0</fixVersion>
                                        <due></due>
                            <votes>2</votes>
                                    <watches>15</watches>
                                                                            <comments>
                            <comment id="215078" author="ndauchy" created="Thu, 30 Nov 2017 23:59:36 +0000"  >&lt;p&gt;We are currently draining multiple OSTs from one of our file systems (to use as spare hardware) and are interested in this work.  We have used both methods of &quot;lctl --device XX deactivate&quot; and &quot;lctl conf_param lfs-OST-00XX.osc.active=0&quot;, and are still seeing the targets show up on client remount.&lt;/p&gt;

&lt;p&gt;Has anything changed in the last ~2 years such that this task is still relevant, or (hopefully) easier to implement?&lt;/p&gt;

&lt;p&gt;What workarounds are available while this task is waiting in the wings?  Are there tricks to mount as ldiskfs and tweak the config files directly?  Can we use a &quot;writeconf&quot; procedure to at least in part clean up the OST entry?&lt;/p&gt;</comment>
                            <comment id="215086" author="adilger" created="Fri, 1 Dec 2017 02:17:38 +0000"  >&lt;p&gt;I landed a patch for &#8220;lfs df&#8221; in 2.10 (&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-8920&quot; title=&quot;don&amp;#39;t print permanently deactivated OSTs in lfs df output&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-8920&quot;&gt;&lt;del&gt;LU-8920&lt;/del&gt;&lt;/a&gt;) to skip printing of deactivated OSTs. This is where most users see inactive targets. It does not cancel the configuration records permanently. &lt;/p&gt;</comment>
                            <comment id="281138" author="adilger" created="Wed, 30 Sep 2020 21:32:33 +0000"  >&lt;p&gt;To permanently remove one or more OSTs from the configuration logs, there are two possible approaches.&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;rewrite the configuration with &quot;&lt;tt&gt;tunefs.lustre &amp;#45;&amp;#45;writeconf&lt;/tt&gt;&quot; on all the filesystem targets, and then the regenerated config llog will not even list the OSTs that are not connected.  This has the benefit of being relatively straight forward to do, but needs a filesystem outage to unmount, run &lt;tt&gt;&amp;#45;&amp;#45;writeconf&lt;/tt&gt;, and remount all of the remaining the targets.&lt;/li&gt;
	&lt;li&gt;use &quot;&lt;tt&gt;lctl &amp;#45;&amp;#45;device MGS llog_print $fsname&amp;#45;client&lt;/tt&gt;&quot; (and also &quot;&lt;tt&gt;... $fsname&amp;#45;MDTxxxx&lt;/tt&gt;&quot; for all the MDTs) to list all &lt;tt&gt;attach&lt;/tt&gt;, &lt;tt&gt;setup&lt;/tt&gt;, &lt;tt&gt;add_osc&lt;/tt&gt;, &lt;tt&gt;add_pool&lt;/tt&gt;, and other records related to the removed OST(s), as well as potentially &lt;tt&gt;add_uuid&lt;/tt&gt; records for the removed OSS nodes (if any):
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;mgs# lctl --device MGS llog_print testfs-client | egrep &quot;192.168.10.99@tcp|OST0003&quot;
- { index: 135, event: add_uuid, nid: 192.168.10.99@tcp(0x20000c0a80a63), node: 192.168.10.99@tcp }
- { index: 136, event: attach, device: testfs-OST0003-osc, type: osc, UUID: testfs-clilov_UUID }
- { index: 137, event: setup, device: testfs-OST0003-osc, UUID: testfs-OST0003_UUID, node: 192.168.10.99@tcp }
- { index: 138, event: add_osc, device: testfs-clilov, ost: testfs-OST0003_UUID, index: 3, gen: 1 }
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/li&gt;
	&lt;li&gt;use &quot;&lt;tt&gt;lctl &amp;#45;&amp;#45;device MGS llog_cancel $fsname-client --i &amp;lt;index&amp;gt;&lt;/tt&gt;&quot; for each of those OST records in each of the config llogs to disable the processing, e.g. for each of the &lt;tt&gt;$fsname-client&lt;/tt&gt; and &lt;tt&gt;$fsname-MDTxxxx&lt;/tt&gt; config logs the appropriate record indices need to be cancelled (they will be different between the client and MDTs):
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;mgs# lctl --device MGS llog_cancel testfs-client -i 138
mgs# lctl --device MGS llog_cancel testfs-client -i 137
mgs# lctl --device MGS llog_cancel testfs-client -i 136
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The second option is a bit more effort to do today, but could be done while the filesystem is mounted as it only affects records that the mounted clients have already processed. The next time that a client or MDT are mounted, they should skip those OST records completely, and not try to connect to them at all.&lt;/p&gt;

&lt;p&gt;It would definitely be useful to have a wrapper script/command (something like &quot;&lt;tt&gt;lctl &lt;span class=&quot;error&quot;&gt;&amp;#91;--device MGS&amp;#93;&lt;/span&gt; del_ost &amp;lt;$fsname-OSTxxxx&amp;gt;&lt;/tt&gt;&quot;) to do the &lt;tt&gt;llog_cancel&lt;/tt&gt; commands with a minimum of user interaction.  For safety, it would be best to cancel the config records from the higher to lower index, so that there are no errors if a client mounts in the middle of the changes.&lt;/p&gt;</comment>
                            <comment id="291498" author="gerrit" created="Tue, 9 Feb 2021 06:50:56 +0000"  >&lt;p&gt;Stephane Thiell (sthiell@stanford.edu) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/41449&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/41449&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7668&quot; title=&quot;permanently remove deactivated OSTs from configuration log&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7668&quot;&gt;&lt;del&gt;LU-7668&lt;/del&gt;&lt;/a&gt; utils: add lctl del_ost&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 85f353cefe428eb0c9c0e183f3475853a6324523&lt;/p&gt;</comment>
                            <comment id="291533" author="gerrit" created="Tue, 9 Feb 2021 16:35:39 +0000"  >&lt;p&gt;Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/41454&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/41454&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7668&quot; title=&quot;permanently remove deactivated OSTs from configuration log&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7668&quot;&gt;&lt;del&gt;LU-7668&lt;/del&gt;&lt;/a&gt; admin: reference the del_ost command&lt;br/&gt;
Project: doc/manual&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: eae54ec42263b49de8358706d76cdcfd3d05cf8f&lt;/p&gt;</comment>
                            <comment id="291534" author="adilger" created="Tue, 9 Feb 2021 16:39:56 +0000"  >&lt;p&gt;Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/41453&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/41453&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7668&quot; title=&quot;permanently remove deactivated OSTs from configuration log&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7668&quot;&gt;&lt;del&gt;LU-7668&lt;/del&gt;&lt;/a&gt; admin: remove OST from config logs&lt;br/&gt;
Project: doc/manual&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 4e66495d8bc07dc7714e3f300c06b9390d3271c0&lt;/p&gt;</comment>
                            <comment id="293212" author="castagnede" created="Fri, 26 Feb 2021 15:34:13 +0000"  >&lt;p&gt;Hello Andreas,&lt;/p&gt;

&lt;p&gt;Instead of writing the Lustre Configuration Logs using &quot;tunefs.lustre --writeconf&quot;, we could proceed using llog_cancel to completely remove OST from the configuration and get the same results for our case.&lt;/p&gt;

&lt;p&gt;Am I understanding properly here ?&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="293373" author="adilger" created="Sun, 28 Feb 2021 00:53:00 +0000"  >&lt;p&gt;Essentially, yes. The &lt;tt&gt;llog_cancel&lt;/tt&gt; command doesn&apos;t actually remove the records from the config log, but they are marked as &quot;already processed&quot; so they are skipped by the client and MDS during mount. &lt;/p&gt;</comment>
                            <comment id="294075" author="eaujames" created="Fri, 5 Mar 2021 10:50:44 +0000"  >&lt;p&gt;Hello Andreas,&lt;/p&gt;

&lt;p&gt;What are the consequences to keep the &quot;add_uuid&quot; records when removing all the OSTs of a node?&lt;/p&gt;

&lt;p&gt;Should we add an option to lctl del_ost&quot; to remove &quot;add_uuid&quot; records if all the OSTs of a node have been deleted?&lt;/p&gt;</comment>
                            <comment id="294187" author="adilger" created="Sun, 7 Mar 2021 20:57:46 +0000"  >&lt;p&gt;Etienne, I haven&apos;t looked into the details, but it would leave an unused network connection to that OSS, which &lt;em&gt;may&lt;/em&gt; cause spurious connection attempts, though it may be the connection is never used if there are no targets on it.  Definitely worthwhile to test out at least. &lt;/p&gt;</comment>
                            <comment id="295751" author="sthiell" created="Mon, 22 Mar 2021 23:47:59 +0000"  >&lt;p&gt;I&apos;m still working on this, but we hit an unusual problem with llog_cancel / del_ost prototype. It worked fine at first, but after a few days, we restarted a MDS while the MGS was down, and two MDTs used a cached version of their config to start, trying to connect to the old OSTs again and we hit a MDS crash same as &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-9699&quot; title=&quot;osp_obd_connect()) ASSERTION( osp-&amp;gt;opd_connects == 1 ) failed&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-9699&quot;&gt;&lt;del&gt;LU-9699&lt;/del&gt;&lt;/a&gt;. This cached version didn&apos;t even have the latest OSTs that we added to the filesystem. I&apos;m wondering if there is a way to make sure the MDTs have up-to-date versions of their config, especially after adding or removing OSTs.&lt;/p&gt;</comment>
                            <comment id="295776" author="eaujames" created="Tue, 23 Mar 2021 07:52:28 +0000"  >&lt;p&gt;Hello Stephane,&lt;/p&gt;

&lt;p&gt;I think that the &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-14090&quot; title=&quot;lctl replace_nids and starting target with local copy of logs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-14090&quot;&gt;&lt;del&gt;LU-14090&lt;/del&gt;&lt;/a&gt; describes your issue.&lt;/p&gt;

&lt;p&gt;The patch &lt;a href=&quot;https://review.whamcloud.com/40448&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/40448&lt;/a&gt; (&quot;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-14090&quot; title=&quot;lctl replace_nids and starting target with local copy of logs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-14090&quot;&gt;&lt;del&gt;LU-14090&lt;/del&gt;&lt;/a&gt; mgs: no local logs flag&quot;) add a tunefs.lustre option to ignore local log.&lt;/p&gt;</comment>
                            <comment id="299104" author="gerrit" created="Sat, 17 Apr 2021 18:51:34 +0000"  >&lt;p&gt;Andreas Dilger (adilger@whamcloud.com) merged in patch &lt;a href=&quot;https://review.whamcloud.com/41453/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/41453/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7668&quot; title=&quot;permanently remove deactivated OSTs from configuration log&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7668&quot;&gt;&lt;del&gt;LU-7668&lt;/del&gt;&lt;/a&gt; admin: remove OST from config logs&lt;br/&gt;
Project: doc/manual&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: c7a2886198b7273165d90d5054e7da669ba97843&lt;/p&gt;</comment>
                            <comment id="326742" author="eaujames" created="Fri, 18 Feb 2022 19:06:29 +0000"  >&lt;p&gt;It appears that the method describes in &lt;a href=&quot;https://review.whamcloud.com/41453/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/41453/&lt;/a&gt; is not safe (for now) .&lt;/p&gt;

&lt;p&gt;lctl llog_cancel remove/cancel directly the record inside llog bitmap header. This creates index gaps in the llog config. llog_backup() is used to create a local copy of the MGS config when mounting a target. This function does not keep the index gaps in llog copy. &lt;br/&gt;
So indexes mismatch between the copy and the original, it mess up the config update mechanism (e.g: adding a new target). &lt;/p&gt;

&lt;p&gt;For more information see &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-15000&quot; title=&quot;MDS crashes with (osp_dev.c:1404:osp_obd_connect()) ASSERTION( osp-&amp;gt;opd_connects == 1 ) failed&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-15000&quot;&gt;&lt;del&gt;LU-15000&lt;/del&gt;&lt;/a&gt;. &lt;/p&gt;</comment>
                            <comment id="340012" author="gerrit" created="Mon, 11 Jul 2022 06:50:04 +0000"  >&lt;p&gt;&quot;Oleg Drokin &amp;lt;green@whamcloud.com&amp;gt;&quot; merged in patch &lt;a href=&quot;https://review.whamcloud.com/41449/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/41449/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7668&quot; title=&quot;permanently remove deactivated OSTs from configuration log&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7668&quot;&gt;&lt;del&gt;LU-7668&lt;/del&gt;&lt;/a&gt; utils: add lctl del_ost&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 1121816c4a4e1bb2ef097c4a9802362181c43800&lt;/p&gt;</comment>
                            <comment id="343532" author="gerrit" created="Fri, 12 Aug 2022 22:02:11 +0000"  >&lt;p&gt;&quot;Andreas Dilger &amp;lt;adilger@whamcloud.com&amp;gt;&quot; merged in patch &lt;a href=&quot;https://review.whamcloud.com/41454/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/41454/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7668&quot; title=&quot;permanently remove deactivated OSTs from configuration log&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7668&quot;&gt;&lt;del&gt;LU-7668&lt;/del&gt;&lt;/a&gt; admin: reference the del_ost command&lt;br/&gt;
Project: doc/manual&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 805e8a34afc5002bb1d843faeb067dfc4d70444b&lt;/p&gt;</comment>
                            <comment id="343786" author="gerrit" created="Wed, 17 Aug 2022 00:31:24 +0000"  >&lt;p&gt;&quot;Andreas Dilger &amp;lt;adilger@whamcloud.com&amp;gt;&quot; uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/48237&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/48237&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7668&quot; title=&quot;permanently remove deactivated OSTs from configuration log&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7668&quot;&gt;&lt;del&gt;LU-7668&lt;/del&gt;&lt;/a&gt; misc: add support for versions 2.17/2.18&lt;br/&gt;
Project: doc/manual&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 6632007c3a4b9ce912593133df6546fc128433ff&lt;/p&gt;</comment>
                            <comment id="343790" author="gerrit" created="Wed, 17 Aug 2022 00:42:28 +0000"  >&lt;p&gt;&quot;Andreas Dilger &amp;lt;adilger@whamcloud.com&amp;gt;&quot; merged in patch &lt;a href=&quot;https://review.whamcloud.com/48237/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/48237/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7668&quot; title=&quot;permanently remove deactivated OSTs from configuration log&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7668&quot;&gt;&lt;del&gt;LU-7668&lt;/del&gt;&lt;/a&gt; misc: add support for versions 2.17/2.18&lt;br/&gt;
Project: doc/manual&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 5313e6797fdf7e861fe01fc1885f966ca6d86ed7&lt;/p&gt;</comment>
                            <comment id="365034" author="gerrit" created="Tue, 7 Mar 2023 01:02:47 +0000"  >&lt;p&gt;&quot;Andreas Dilger &amp;lt;adilger@whamcloud.com&amp;gt;&quot; uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/c/fs/lustre-release/+/50221&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/c/fs/lustre-release/+/50221&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7668&quot; title=&quot;permanently remove deactivated OSTs from configuration log&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7668&quot;&gt;&lt;del&gt;LU-7668&lt;/del&gt;&lt;/a&gt; tests: skip conf-sanity test_33a for old MGS&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: ed0dc54cb946884ff2d5225a56146ff15ffce51d&lt;/p&gt;</comment>
                            <comment id="366773" author="gerrit" created="Tue, 21 Mar 2023 23:16:55 +0000"  >&lt;p&gt;&quot;Oleg Drokin &amp;lt;green@whamcloud.com&amp;gt;&quot; merged in patch &lt;a href=&quot;https://review.whamcloud.com/c/fs/lustre-release/+/50221/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/c/fs/lustre-release/+/50221/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7668&quot; title=&quot;permanently remove deactivated OSTs from configuration log&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7668&quot;&gt;&lt;del&gt;LU-7668&lt;/del&gt;&lt;/a&gt; tests: skip conf-sanity test_33a for old MGS&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: ba5346b050fb395844252a706d4dba2ef0e0d8dc&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10120">
                    <name>Blocker</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="65994">LU-15000</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="22210">LU-4295</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="22516">LU-4397</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="30075">LU-6601</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="71186">LU-16024</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="31014">LU-6818</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="42298">LU-8920</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="34435">LU-7731</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="61424">LU-14090</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="62770">LU-14403</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="39080">LUDOC-352</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="79002">LU-17299</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="74002">LU-16475</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="57439">LU-12998</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzxy8f:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>