Bug 899223 (JBEWS-206)
| Summary: | EWS - rpm install on RHEL5: installation command from Release Notes takes tomcat5 packages from RHEL5 base channel | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Web Server 1 | Reporter: | Ivo Studensky <istudens> | ||||||
| Component: | unspecified | Assignee: | Permaine Cheung <pcheung> | ||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | EWS 1.0.1 | CC: | istudens, rajesh.rajasekaran, rebecca.jboss | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | EWS 1.0.2 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://jira.jboss.org/jira/browse/JBEWS-206 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: |
RHEL5 i386, x86_64
|
|||||||
| Last Closed: | 2011-06-09 13:31:47 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Ivo Studensky
2010-02-10 17:32:44 UTC
Ivo, does this mean that the first two paragraphs here can be removed from the release notes? Should all users commend out exactarch, or does this option not have an effect? --- On Red Hat Enterprise Linux 5 check that the Tomcat 5 packages are not already installed, if not then install the packages by executing: yum install tomcat6 tomcat6-webapps tomcat6-admin-webapps tomcat5 tomcat5-webapps tomcat5-admin-webapps tomcat-native httpd mod_jk-ap20 Otherwise, in order to install the Tomcat 5 packages, you need to make the following modification to the /etc/yum.conf file. Comment out the option: exactarch=1 Then install the packages: yum install tomcat6 tomcat6-webapps tomcat6-admin-webapps tomcat5.noarch tomcat5-webapps.noarch tomcat5-admin-webapps.noarch tomcat-native httpd mod_jk-ap20 I do not know the yum so much to be able to say that. It's rather a question for someone else I think. However, on my RHEL5 testing machines exactarch does not have any effect for EWS installation. Before documenting, we need to investigate what the issue is and how it can be fixed or worked around, Assigning to Permaine. I re-tested this issue on a clean RHEL5 i386 machine from RHTS again and it worked as expected by release notes. All "main" packages were installed from EWS channel correctly. It seems it is a problem of my own testing boxes. Still need to re-test it on a RHEL5 x86_64 from RHTS and then I will close this issue with 'Cannot reproduce bug'. It looks good also for RHEL5 x86_64 taken from RHTS. So I am closing this issue as non-reproducible. The issue was reproduced again on RHTS testing system. Please look at this test run: http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=12277108 And look at the install.log which is bundled to the jboss-ews.126632_341990_2753467.tar.gz archive in the Binary Logs of this run and which corresponds to these steps of the test: :: [ PASS ] :: Installing EWS packages from live. ... :: [ FAIL ] :: Checking whether the packages have been installed from EWS channel (Expected 1, got 0) For more information see source code of the test: http://cvs.devel.redhat.com/cgi-bin/cvsweb.cgi/tests/jboss-ews/Releasecriterium/jboss-qa-rpm-common/runtest.sh?rev=1.15;content-type=text%2Fplain Attaching the log file in case you are not able to access rhts. tomcat5 and other packages are being fetched from rhel-i386-server-5 channel. Attachment: Added: install.log Please advise me of the changes required to the release notes; this goes out on Tuesday. At present I assume that the instructions are limited to commenting out "exactarch=1" in /etc/yum.conf and executing the following command: yum install tomcat6 tomcat6-webapps tomcat6-admin-webapps tomcat5.noarch tomcat5-webapps.noarch tomcat5-admin-webapps.noarch tomcat-native httpd mod_jk-ap20 Laura, the installation command you wrote works fine on all tested RHEL5 system. I am not sure about that exactarch, it is set up by default on testing machines of RHTS. Just to be more specific, the installation fails only on RHEL5-Server-U4 servers chosen from Released Distros on Single Workflow RHTS page, it works fine on RHEL5.5-Server-20100218.nightly servers chosen from Distros on that page. You can see link for that page below. I hope it could be helpful for anyone. Link to Single Workflow RHTS page: https://rhts.redhat.com/cgi-bin/rhts/single_workflow.cgi I cannot reproduce this issue, with or without tomcat5 installed from base. BTW, The install.log shows that you're updating packages to EWS 1.0.0, not 1.0.1, looks like the setup is not correct. The two packages of interest here are: tomcat5 i386 5.5.23-0jpp.7.el5_3.2 rhel-i386-server-5 tomcat5 noarch 5.5.23-0jpp.9.6.ep5.el5 jb-ews-1-i386-server-5-rpm When installing EWS 1.0.0 on RHEL5-U4 which is the released version. tomcat5 package from base RHEL5 channel rhel-i386-server-5 gets installed instead on EWS. When installing EWS 1.0.0 on a nightly build RHEL5.5-Server-20100218.nightly tomcat5 package from EWS channel jb-ews-1-i386-server-5-rpm gets installed. One thing to check is if the rhel-i386-server-5 on RHEL5-U4 and RHEL5.5-Server-20100218.nightly systems are the same. In any case when EWS 1.0.1 is pushed out live, tomcat will be at 5.5.28 which should always take dominance than 5.5.23 version. We can currently verify this by first subscribing to RHN stage and DIRECTLY installing 1.0.1 from stage. Ivo, please give this a try. It looks bad even for direct installation of 1.0.1 from stage. When first subscribing to RHN stage and trying to directly install packages from stage, the installation fails too. Full installation log attached. I checked that for both i386 and x86_64 of RHEL5-U4. See below. # grep redhat\.com /etc/sysconfig/rhn/up2date serverURL=http://xmlrpc.rhn.stage.redhat.com/XMLRPC # grep exactarch /etc/yum.conf exactarch=1 # yum install tomcat6 tomcat6-webapps tomcat6-admin-webapps tomcat5 tomcat5-webapps tomcat5-admin-webapps tomcat-native httpd mod_jk-ap20 ... Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: httpd i386 2.2.14-1.2.1.ep5.el5 jb-ews-1-i386-server-5-rpm 1.0 M mod_jk-ap20 i386 1.2.28-4.1.ep5.el5 jb-ews-1-i386-server-5-rpm 222 k tomcat-native i386 1.1.19-2.0.1.ep5.el5 jb-ews-1-i386-server-5-rpm 63 k tomcat5 i386 5.5.23-0jpp.7.el5_3.2 rhel-i386-server-5 338 k tomcat5-admin-webapps i386 5.5.23-0jpp.7.el5_3.2 rhel-i386-server-5 3.0 M tomcat5-webapps i386 5.5.23-0jpp.7.el5_3.2 rhel-i386-server-5 1.2 M tomcat6 noarch 6.0.24-2.1.ep5.el5 jb-ews-1-i386-server-5-rpm 111 k tomcat6-admin-webapps noarch 6.0.24-2.1.ep5.el5 jb-ews-1-i386-server-5-rpm 32 k tomcat6-webapps noarch 6.0.24-2.1.ep5.el5 jb-ews-1-i386-server-5-rpm 87 k ... After the installation: # yum list tomcat5 Loaded plugins: rhnplugin, security Installed Packages tomcat5.i386 5.5.23-0jpp.7.el5_3.2 installed Available Packages tomcat5.noarch 5.5.28-7.1.ep5.el5 jb-ews-1-i386-server-5-rpm Am I doing something wrong or missing some configuration? Attachment: Added: install_rhel5_u4_i386.log Output of 'yum list' before the installation: # yum list tomcat5 Loaded plugins: rhnplugin, security Available Packages tomcat5.i386 5.5.23-0jpp.7.el5_3.2 rhel-i386-server-5 tomcat5.noarch 5.5.28-7.1.ep5.el5 jb-ews-1-i386-server-5-rpm I tried it again on clean RHEL5-U4 system with exactarch set to '0' and it still took tomcat5 from RHEL base channel. It seems that for RHEL5-U4 the only successful method is: yum install tomcat5.noarch tomcat5-webapps.noarch tomcat5-admin-webapps.noarch If 'yum install tomcat5.noarch tomcat5-webapps.noarch tomcat5-admin-webapps.noarch' always work, then let's have that as the instructions in the Release Notes as adding the .noarch doesn't hurt the installation, that way we can have the same set of instructions for installation (with or without tomcat5 from base install). That would be a workaround for now. I still view this as a bug and would like to understand how the .arch extensions work and how our EWS tomcat packages should be designed to handle them. This actually has to do with how yum handles different arch packages, how it detects what is latest for a certain package. When that packages is not installed, in this case the 5.5.28 should always win over 5.5.23 in base and EWS 1.0.0. When a packages is already installed, and it is to be upgraded, the exactarch affects what is upgraded. If you look up info on yum, when exactarch is 1, yum update only update the architectures of packages that you have installed, so if you have the base packages installed, you need to comment that out in order to update the .noarch packages. As we have no control over the yum package, what we can do is to update the instructions in the Release Notes. Just two cents. Even when the packages are not yet installed, yum takes tomcat5 from RHEL base channel, i.e. takes tomcat-5.5.23.i386 and not tomcat-5.5.28.noarch, as you can see in my previous comments. And even if exactarch is set to 1 and tomcat5 packages from RHEL base channel are already installed, yum does update them to the .noarch ones from EWS channel correctly. I checked this on all versions of RHEL5 which I mentioned above. Despite of how yum/exactarch should or really work I think that the installation command with .noarch packages is safer choice. Oops, my latter statement is not fully true. I re-checked results of my test and saw that on RHEL5-U4 'yum update' failed with some unresolved dependencies and that only 'yum install <packages>.noarch' worked in that case (with prior installation of tomcat5 pkgs from RHEL5 base channel). I am sorry for little confusion. After discussing with Permaine, this seems to occur due to a bug in yum. https://bugzilla.redhat.com/show_bug.cgi?id=502401 Users should be recommended to install the .noarch packages for all tomcat5 packages. Please modify the install instructions to include the .noarch packages. and we should also leave a small NOTE explaining the problem. Turning over to docs. I have altered the RHEL5 installation notes and documented this issue in the EWS 1.0.1 release notes. Verified. I cannot see any update in the RHEL5 installation instructions for this issue. There are still just package names without the .noarch suffix in the Installation Guide. Ivo, do you explicitly mention the .noarch in our testing? Good point, Rajesh. I will check this and eventually fix it. Thanks. Hi all, is this issue resolved with section 3.3.3 Installing Enterprise Web Server from RPM Files in the Installation Guide? http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Web_Server/1.0/html/Installation_Guide/sec-Subscribing_to_RHN_Channels_and_Installing_EWS_from_RPM_Files-Linux.html If so, please resolve :) Thanks. Pavel, can you take a look at this jira/documentation? QA verified, documentation correctly specified tomcat5.noarch tomcat5-webapps.noarch tomcat5-admin-webapps.noarch as requested. |