<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:04:16 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-151] Test cases fail if the $RUNAS_ID does not have executable permissions</title>
                <link>https://jira.whamcloud.com/browse/LU-151</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;If the $RUNAS_ID user does not have executable permissions on the lustre source tree, certain tests cases will fail with obscure error messages.&lt;/p&gt;

&lt;p&gt;For example, with a user id of 0, runas id of 99, and a umask of 0077.. sanity.sh test 33a fails because the $LUSTRE_SRC/lustre/tests/openfile is not executable by user 99.&lt;/p&gt;

&lt;p&gt;Although, if our umask if 0000, then of course user 99 has executable permissions on the openfile binary and the test passes.&lt;/p&gt;

&lt;p&gt;To top it off, the tests will fail without reporting the permissions issue. From the outside, it appears that Lustre is failing these specific test cases when that is not the real problem at all.&lt;/p&gt;

&lt;p&gt;Perhaps, there needs to be a way to check the permissions and then skip the tests it cannot run based on this check? Also, displaying a human readable message explaining to the user why these tests are being skipped could provide useful.&lt;/p&gt;</description>
                <environment></environment>
        <key id="10487">LU-151</key>
            <summary>Test cases fail if the $RUNAS_ID does not have executable permissions</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="chris">Chris Gearing</assignee>
                                    <reporter username="prakash">Prakash Surya</reporter>
                        <labels>
                    </labels>
                <created>Tue, 22 Mar 2011 14:27:52 +0000</created>
                <updated>Tue, 4 Mar 2014 01:27:25 +0000</updated>
                            <resolved>Tue, 4 Mar 2014 01:27:25 +0000</resolved>
                                    <version>Lustre 2.1.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="11298" author="pjones" created="Wed, 23 Mar 2011 06:11:07 +0000"  >&lt;p&gt;Prakash&lt;/p&gt;

&lt;p&gt;I spoke with Chris Gearing, who is leading the efforts to revamp the whole Lustre test infrastructure. It sounds like this specific instance - and other similar instances which you alluded to in yesterday&apos;s meeting - should be tackled as part of the larger clean up plans.&lt;/p&gt;

&lt;p&gt;Regards&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="11303" author="prakash" created="Wed, 23 Mar 2011 08:07:34 +0000"  >&lt;p&gt;Thanks Peter.&lt;/p&gt;

&lt;p&gt;On a related note, as more issues with the test suite are uncovered, is opening individual JIRA tickets for each issue the accepted way to go about reporting them?&lt;/p&gt;

&lt;p&gt;Prakash&lt;/p&gt;</comment>
                            <comment id="24825" author="pjones" created="Thu, 15 Dec 2011 10:00:45 +0000"  >&lt;p&gt;Prakash&lt;/p&gt;

&lt;p&gt;Sorry I missed your question previously. I would say that opening a new ticket is the best way to go. It can always be closed as a duplicate if it is addressed as part of a larger cleanup exercise&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="78302" author="jfc" created="Tue, 4 Mar 2014 01:27:25 +0000"  >&lt;p&gt;JIRA cleanup project.&lt;br/&gt;
Looks like this has been dealt with, so I&apos;m marking it as resolved &amp;#8211; but do shout if you want me to keep it open.&lt;br/&gt;
Thanks,&lt;br/&gt;
~ jfc.&lt;/p&gt;</comment>
                    </comments>
                    <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|hzw0p3:</customfieldvalue>

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