<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:53:39 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-5689] need correct group definitions in el7 test clients</title>
                <link>https://jira.whamcloud.com/browse/LU-5689</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;certain tests in our test framework assume that user &apos;daemon&apos; is a defined member of more than one group.  In particular test_103a of sanity.sh assumes that user &apos;daemon&apos; is a member of group &apos;bin&apos;.  This has been true on all our supported versions up until now.  It isn&apos;t true on a default install of el7.  Failure of this assumption causes test failure.  see &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5641&quot; title=&quot;sanity.sh test_103a &amp;quot;acl test&amp;quot; fails on el7&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5641&quot;&gt;&lt;del&gt;LU-5641&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I think it&apos;s a TEI responsibility to setup users and groups on installed test nodes that conform to our embedded assumptions.&lt;/p&gt;</description>
                <environment>el7 test nodes</environment>
        <key id="26647">LU-5689</key>
            <summary>need correct group definitions in el7 test clients</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</priority>
                        <status id="6" iconUrl="https://jira.whamcloud.com/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="success"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="bogl">Bob Glossman</reporter>
                        <labels>
                    </labels>
                <created>Thu, 18 Sep 2014 20:42:31 +0000</created>
                <updated>Tue, 30 Sep 2014 20:51:22 +0000</updated>
                            <resolved>Tue, 30 Sep 2014 20:51:22 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="94452" author="mdiep" created="Thu, 18 Sep 2014 20:56:45 +0000"  >&lt;p&gt;I think it&apos;s the other way around, Lustre tests can not assume such strange setup. TEI setup never do anything to change user (except create test users). the fix should be in lustre test&lt;/p&gt;</comment>
                            <comment id="94455" author="joshua" created="Thu, 18 Sep 2014 21:33:32 +0000"  >&lt;p&gt;Minh is correct. We do not mess with user-level users. The only user we fiddle with are things like sanity user and the like.  We do not create or edit system users.  I would assume this is a change made in RHEL 7, so the code needs to be changed to reflect that.&lt;/p&gt;</comment>
                            <comment id="94456" author="bogl" created="Thu, 18 Sep 2014 21:40:09 +0000"  >&lt;p&gt;still thinking it should be fixed in the environment, not in the test, but willing to consider other opinions.  yes, it is something different on el7 from anything earlier.  The problem is I don&apos;t know how to fix it in lustre tests in such a way that it will do the right thing in new distros yet not mess up old distros.  maybe it just needs somebody a bit more clever.&lt;/p&gt;</comment>
                            <comment id="95341" author="joshua" created="Tue, 30 Sep 2014 19:10:05 +0000"  >&lt;p&gt;A lustre test can query the distro on which it is running, no?&lt;/p&gt;

&lt;p&gt;Also, we don&apos;t want to have a special EL7 setup for just our tests, because if the tests pass on our setup, they may then fail when somebody runs the tests (or worse, the software) on stock EL7 that hasn&apos;t had the custom modifications.&lt;/p&gt;</comment>
                            <comment id="95344" author="joshua" created="Tue, 30 Sep 2014 19:11:22 +0000"  >&lt;p&gt;Moving to an LU ticket per &lt;a href=&quot;https://jira.whamcloud.com/secure/ViewProfile.jspa?name=jlevi&quot; class=&quot;user-hover&quot; rel=&quot;jlevi&quot;&gt;jlevi&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="95356" author="bogl" created="Tue, 30 Sep 2014 20:51:22 +0000"  >&lt;p&gt;addressed by fix for &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5641&quot; title=&quot;sanity.sh test_103a &amp;quot;acl test&amp;quot; fails on el7&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5641&quot;&gt;&lt;del&gt;LU-5641&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="26649">LU-5641</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|hzwwof:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>15800</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>