<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:29:25 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 add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-3613] reference env builds are failing 14.10.2022</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-3613</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;See the discussion on #hosted-reference-env &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-project.slack.com/archives/CFQU1MF61/p1665759083072169&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-project.slack.com/archives/CFQU1MF61/p1665759083072169&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="82362">FOLIO-3613</key>
            <summary>reference env builds are failing 14.10.2022</summary>
                <type id="10005" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium">Story</type>
                                            <priority id="10001" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p2.svg">P2</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="5ee89462f7aa140abd82d11d">Julian Ladisch</assignee>
                                                                <reporter accountid="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d">Jakub Skoczen</reporter>
                                    <labels>
                    </labels>
                <created>Mon, 17 Oct 2022 12:18:06 +0000</created>
                <updated>Thu, 17 Nov 2022 09:55:10 +0000</updated>
                            <resolved>Wed, 26 Oct 2022 09:45:22 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                <comments>
                                                            <comment id="198254" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Mon, 17 Oct 2022 12:20:36 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt; Guys, is it possible to get logs for mod-inventory-storage? E.g if there is. a stack trace related to the &quot;500 Timeout&quot; messages. &lt;/p&gt;</comment>
                                                            <comment id="198255" author="63e2a2771b13d42998e4e706" created="Mon, 17 Oct 2022 13:16:59 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The &lt;a href=&quot;https://jenkins-aws.indexdata.com/job/Automation/job/build-platform-complete-snapshot/13040/consoleFull&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;last successful&lt;/a&gt; platform complete build included mod-inventory-storage-25.0.0-SNAPSHOT.737.&lt;/p&gt;

&lt;p&gt;That version came from &lt;a href=&quot;https://jenkins-aws.indexdata.com/job/folio-org/job/mod-inventory-storage/job/master/737/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;this build&lt;/a&gt;, it was based upon &lt;a href=&quot;https://github.com/folio-org/mod-inventory-storage/commit/f52c6f70b99dede726d7bda2fed9230b574718c7&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;this revision&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This was the change immediately prior to the merges around &lt;a href=&quot;https://github.com/folio-org/mod-inventory-storage/pull/825&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;RMB 35.x upgrade&lt;/a&gt; and &lt;a href=&quot;https://github.com/folio-org/mod-inventory-storage/pull/823&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;new Batch APIs&lt;/a&gt;.&lt;/p&gt;</comment>
                                                            <comment id="198257" author="5f9abc1eb45b2e007453f423" created="Mon, 17 Oct 2022 14:34:15 +0000"  >&lt;p&gt;I&apos;ve submitted a PR to pin mod-inventory-storage to v25.0.0-SNAPSHOT.737.    The build-platform-complete-snapshot now passes.   I&apos;ve started a rebuild of folio-snapshot-2.    There are Okapi logs available from the previous, failed build-platform-complete-snapshot jobs in the Jenkins UI.    If these logs are not sufficient to troubleshoot the RMB issue,  I can create a separate, one-off build-complete-snapshot job that retains the ec2 instance after it fails. &lt;/p&gt;

</comment>
                                                            <comment id="198259" author="5f9abc1eb45b2e007453f423" created="Mon, 17 Oct 2022 21:31:52 +0000"  >&lt;p&gt;I&apos;ve unpinned mod-inventory-storage snapshot after receiving word the breaking changes had been rolled back in mod-inventory-storage and the build-platform-complete-snapshot Jenkins job passes.    Changes should be reflected in this evening&apos;s folio-snapshot build. &lt;/p&gt;

</comment>
                                                            <comment id="198261" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Tue, 18 Oct 2022 12:44:46 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; we talked with &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; about setting up a build that includes MIS with RMB 35 for debugging purposes. Would that be useful to have?&lt;/p&gt;</comment>
                                                            <comment id="198263" author="5f9abc1eb45b2e007453f423" created="Tue, 18 Oct 2022 15:43:24 +0000"  >&lt;p&gt;I&apos;ve got an ec2 FOLIO instance running that fails tenant init exactly as it did previously -  with mod-inventory-storage version mod-inventory-storage-25.0.0-SNAPSHOT.740.  This was the version prior to the RMB 35 changes that were reverted.  &lt;/p&gt;

&lt;p&gt;Ansible reports the error as the following: &lt;/p&gt;

&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;fatal: [10.36.1.105]: FAILED! =&amp;gt; {&quot;changed&quot;: false, &quot;connection&quot;: &quot;close&quot;, &quot;content&quot;: &quot;Tenant operation failed for module mod-inventory-storage-25.0.0-SNAPSHOT.740: GET http://10.36.1.105:9133/identifier-types/1795ea23-6856-48a5-a772-f356e16a8a6c returned status 500: Timeout POST http://10.36.1.105:9133/identifier-types returned status 400: duplicate key value violates unique constraint \&quot;identifier_type_pkey\&quot;: Key (id)=(1795ea23-6856-48a5-a772-f356e16a8a6c) already exists.&quot;, &quot;content_length&quot;: &quot;390&quot;, &quot;content_type&quot;: &quot;text/plain&quot;, &quot;elapsed&quot;: 499, &quot;msg&quot;: &quot;Status code was 500 and not [200]: HTTP Error 500: Internal Server Error&quot;, &quot;redirected&quot;: false, &quot;status&quot;: 500, &quot;url&quot;: &quot;http://10.36.1.105:9130/_/proxy/tenants/diku/install?deploy=true&amp;amp;tenantParameters=loadSample%3Dtrue%2CloadReference%3Dtrue%2CrunReindex%3Dtrue&quot;}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I&apos;ve DM&apos;ed Julian information pertinent to connecting to the system. &lt;/p&gt;</comment>
                                                            <comment id="198266" author="5c706fbb47a54a6728e59df2" created="Tue, 18 Oct 2022 18:27:33 +0000"  >&lt;p&gt;FWIW I note that the UUID referred to above is referenced in both the reference data for the module:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/folio-org/mod-inventory-storage/blob/master/reference-data/identifier-types/UPC.json&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/mod-inventory-storage/blob/master/reference-data/identifier-types/UPC.json&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And in a db script:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/folio-org/mod-inventory-storage/blob/master/src/main/resources/templates/db_scripts/addIdentifierTypesUpcIsmn.sql&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/mod-inventory-storage/blob/master/src/main/resources/templates/db_scripts/addIdentifierTypesUpcIsmn.sql&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="198267" author="63e2a2771b13d42998e4e706" created="Tue, 18 Oct 2022 20:38:46 +0000"  >&lt;blockquote&gt;&lt;p&gt;FWIW I note that the UUID referred to above is referenced in both the reference data for the module And in a db script&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Typically, those scripts are intended to create reference records in situations where the reference record was after the initial installation and reference record loading is disabled yet the record is still desired.&lt;/p&gt;

&lt;p&gt;If that script is interfering in an initial load with reference records enabled, then that suggests a flaw in that script.&lt;/p&gt;
</comment>
                                                            <comment id="198269" author="5ee89462f7aa140abd82d11d" created="Wed, 19 Oct 2022 14:04:16 +0000"  >&lt;p&gt;Environment variables in mod-inventory-storage container:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
                &lt;span class=&quot;code-quote&quot;&gt;&quot;DB_HOST=10.36.1.175&quot;&lt;/span&gt;,
                &lt;span class=&quot;code-quote&quot;&gt;&quot;DB_HOST_READER=postgres-read&quot;&lt;/span&gt;,
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;But the hostname postgres-read is not configured.&lt;br/&gt;
The GET /identifier-types/1795ea23-6856-48a5-a772-f356e16a8a6c is the first request that uses the DB_HOST_READER and not DB_HOST. It times out because the DNS lookup of the non-existing hostname takes too long.&lt;/p&gt;</comment>
                                                            <comment id="198270" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Thu, 20 Oct 2022 07:59:29 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; thanks for figuring this out. &lt;/p&gt;

&lt;p&gt;Before we simply define these env variables: I would expect that the system fails more gracefully here and either refuses to start or continues to work without read/write seperation.&lt;/p&gt;

&lt;p&gt;Note: Julian has already created a PR for more graceful error reporting: &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-949&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/RMB-949&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="198272" author="5ee89462f7aa140abd82d11d" created="Thu, 20 Oct 2022 08:08:23 +0000"  >&lt;p&gt;I don&apos;t think that we should silently use the writer db if the reader db config is wrong because sysOps configure a reader db for reasons.&lt;br/&gt;
Instead a better error message should be provided in the log and the POST /_/tenant HTTP response:&lt;br/&gt;

    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;RMB-939&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-939&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;failOnConflictUnlessSuppressed for optimistic locking&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium&quot; /&gt;
            RMB-939
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 &quot;Report PostgreSQL URI on timeout&quot; = &lt;a href=&quot;https://github.com/folio-org/raml-module-builder/pull/1095&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/raml-module-builder/pull/1095&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I don&apos;t see a reason why the database read/write splitting feature (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;RMB-348&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-348&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Add support for database read/write splitting to RAML Module Builder&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-348
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
) should be removed from RMB 35.&lt;/p&gt;</comment>
                                                            <comment id="198274" author="5ee89462f7aa140abd82d11d" created="Thu, 20 Oct 2022 08:13:30 +0000"  >&lt;blockquote&gt;&lt;p&gt;Before we simply define these env variables&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;There is no need to define the DB_HOST_READER value. If no reader db exists simply don&apos;t define the DB_HOST_READER value.&lt;/p&gt;</comment>
                                                            <comment id="198276" author="5ee89462f7aa140abd82d11d" created="Thu, 20 Oct 2022 08:17:46 +0000"  >&lt;p&gt;Simply undefine the DB_HOST_READER value and the hosted reference environments (snapshot, snapshot-2) will build successfully with all RMB 35 modules.&lt;/p&gt;</comment>
                                                            <comment id="198281" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Thu, 20 Oct 2022 08:25:44 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; I agree, if the variable is defined the system should fail, loud and clear so your fix is great. And the feature should be de-activated when no env var is specified, as it seems to be the case as you say.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; Guys, can we remove the  DB_HOST_READER parameters and revert the RMB35 revert and kick off a new snapshot build?&lt;/p&gt;</comment>
                                                            <comment id="198284" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Thu, 20 Oct 2022 08:39:07 +0000"  >&lt;p&gt;Btw, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt;, any idea why the &quot;DB_HOST_READER&quot; has been configured for this deployment? Where is it defined?&lt;/p&gt;</comment>
                                                            <comment id="198289" author="63e2a2771b13d42998e4e706" created="Thu, 20 Oct 2022 11:24:49 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;can we remove the DB_HOST_READER parameters and revert the RMB35 revert and kick off a new snapshot build?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I initially thought this would be defined in the &lt;a href=&quot;https://github.com/folio-org/mod-inventory-storage/blob/58a16f19978563a51498c5645922a2fe12ea8f01/descriptors/ModuleDescriptor-template.json#L2845-L2861&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;launch descriptor&lt;/a&gt; section of the module descriptor at the point of the RMB 35.x upgrade, as I believe this is used for defaulting a bunch of configuration. However, this environment variable is not defined there.&lt;/p&gt;

&lt;p&gt;The definition of this environment variable was &lt;a href=&quot;https://github.com/folio-org/mod-inventory-storage/commit/3ab73f8800c16ad8710671338f9ae4177c327213#diff-447a26c098aa9f236a852f39464c3149d97a871c75f5b9e8ee6e968bdebe319dR2903&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;included&lt;/a&gt; in the PR for the new unsafe batch APIs.&lt;/p&gt;

&lt;p&gt;A &lt;a href=&quot;https://github.com/search?q=org%3Afolio-org+DB_HOST_READER&amp;amp;type=code&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;search&lt;/a&gt; of the whole folio-org github organisation does not find any definitions of this environment variable outside of RMB, so I think this is localised.&lt;/p&gt;

&lt;p&gt;That suggests we should be able to upgrade to RMB 35.x without this issue recurring. We should not re-apply those API changes as is, instead that work needs to be altered before adding back in.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; does this fit with your understanding?&lt;/p&gt;</comment>
                                                            <comment id="198294" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Thu, 20 Oct 2022 11:42:02 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; I talked with &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; and he will re-open PRs with the reverted commits but remove the DB_*_READER envvars. Does this sound good? We will ask you and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=62ceeb5f078104d0866d40f8&quot; class=&quot;user-hover&quot; rel=&quot;62ceeb5f078104d0866d40f8&quot; data-account-id=&quot;62ceeb5f078104d0866d40f8&quot; accountid=&quot;62ceeb5f078104d0866d40f8&quot; rel=&quot;noreferrer&quot;&gt;Kevin Day&lt;/a&gt; to review, OK?&lt;/p&gt;</comment>
                                                            <comment id="198296" author="63e2a2771b13d42998e4e706" created="Thu, 20 Oct 2022 11:49:26 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;I talked with &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; and he will re-open PRs with the reverted commits but remove the DB_*_READER envvars. Does this sound good?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Sure, that is totally ok with me.&lt;/p&gt;

&lt;p&gt;I think we should upgrade to RMB 35.x completely separately to this work and make sure that runs through at least one platform core snapshot build before we merge that work.&lt;/p&gt;

&lt;p&gt;I&apos;ve already raised a &lt;a href=&quot;https://github.com/folio-org/mod-inventory-storage/pull/829&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;pull request&lt;/a&gt; for that change.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;We will ask you and Kevin Day to review, OK?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Ok, my review will be limited to only checking for changes relating to those environment variables and RMB versions etc. I won&apos;t review the functional changes.&lt;/p&gt;</comment>
                                                            <comment id="198298" author="63e2a2771b13d42998e4e706" created="Thu, 20 Oct 2022 12:03:07 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Unfortunately, builds for that PR are consistently failing.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=62ceeb5f078104d0866d40f8&quot; class=&quot;user-hover&quot; rel=&quot;62ceeb5f078104d0866d40f8&quot; data-account-id=&quot;62ceeb5f078104d0866d40f8&quot; accountid=&quot;62ceeb5f078104d0866d40f8&quot; rel=&quot;noreferrer&quot;&gt;Kevin Day&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; please can you work together to figure out how to address that.&lt;/p&gt;</comment>
                                                            <comment id="198300" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Thu, 20 Oct 2022 12:13:26 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; I am all for first bringing back RMB 35 and then rolling back the revert for batch update work cc &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="198302" author="63e2a2771b13d42998e4e706" created="Thu, 20 Oct 2022 17:08:46 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;I am all for first bringing back RMB 35 and then rolling back the revert for batch update work&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Following these comments, I think there has been some confusion around how we would resolve the issues with the RMB 35.x upgrade as &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; has already submitted a new &lt;a href=&quot;https://github.com/folio-org/mod-inventory-storage/pull/830&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;pull request&lt;/a&gt; for reinstating the unsafe APIs and raised 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODINVSTOR-973&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODINVSTOR-973&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Undo revert MODINVSTOR-972 (RMB 35, batch without OL)&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            MODINVSTOR-973
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 and 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODINVSTOR-974&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODINVSTOR-974&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Remove DB_*_READER env var from ModuleDescriptor&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            MODINVSTOR-974
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 as separate issues.&lt;/p&gt;

&lt;p&gt;To avoid further confusion, I think it is better if the Prokopovych team step away from this work and let the Core Platform team undertake the changes in the way they want. Unless I am told otherwise, I am going to assume that the Core Platform team are taking over resolution of this issue.&lt;/p&gt;

&lt;p&gt;I think it could have been better for us all to have had a conversation about this.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="56493">MODINVSTOR-972</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="56495">MODINVSTOR-974</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="56496">MODINVSTOR-975</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="56512">MODINVSTOR-976</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="56513">MODINVSTOR-977</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="57486">RMB-949</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="56988">RMB-348</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="56492">MODINVSTOR-971</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="57513">RMB-946</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="57484">RMB-947</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10155"><![CDATA[FOLIO DevOps]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10106" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>RCA Group</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10367"><![CDATA[TBD]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i05lu3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="642">CP: Sprint 150</customfieldvalue>
    <customfieldvalue id="2010">DevOps Sprint 151</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 17 Oct 2022 13:16:59 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>