https://bugzilla.novell.com/show_bug.cgi?id=736715 https://bugzilla.novell.com/show_bug.cgi?id=736715#c0 Summary: OBS Web Interface Error when $multiaction_notify_support = 0 Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: OBS Request AssignedTo: mrueckert@suse.com ReportedBy: andrzej.lisowski@ericsson.com QAContact: adrian@suse.com Found By: --- Blocker: --- Created an attachment (id=467380) --> (http://bugzilla.novell.com/attachment.cgi?id=467380) Screenshot with OBS Web Interface Error in jpg format User-Agent: Mozilla/5.0 (Windows NT 6.0) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2 Private instance of OBS is being prepared. The OBS software has been downloaded as virtual appliance from openSUSE and is running on VMWare ESXi 4.0 host. During the work on the integration of this private Open Build Service instance with Hermes http://en.opensuse.org/openSUSE:Hermes the parameter $multiaction_notify_support = 0 has been enabled in the /usr/lib/obs/server/BSConfig.pm file. Unfortunately after enabling this parameter and restarting the private OBS instance the web interface for OBS became dysfunctional and was continuously responding with the following notification on all attempt to access the OBS. ========================================= OBS Web Interface Error: Error Details: Errorcode: unknown Message: <?xml version="1.0" encoding="UTF-8"?> <status code="unknown"> <summary>uncaught exception: Failed to establish connect ======================================================= The screenshot with the reported error message has been attached to this report. After commenting out the parameter $multiaction_notify_support = 0 back and restarting the private OBS instance again the OBS comes back to normal. The issue is 100% reproducible. Identical behavior has been observed with Google Chrome, Internet Explorer and Mozilla Firefox and both Linux and Windows client machines. The following OBS packages have been installed on the host where the issue occures: obs-private-server:~ # rpm -qa | grep obs obs-service-verify_file-0.1-4.1.noarch obs-service-download_src_package-0.1-3.1.noarch obs-signd-2.1.2-1.1.x86_64 obs-service-set_version-0.1-5.1.noarch obs-service-download_url-0.1-12.1.noarch obs-worker-2.1.11-4.7.noarch obs-server-2.1.11-4.7.x86_64 obs-productconverter-2.1.11-4.7.x86_64 obs-utils-2.1.11-4.7.x86_64 obs-api-2.1.11-4.7.x86_64 obs-source_service-2.1.11-4.7.x86_64 obs-common-2.1.0-1.1.x86_64 obs-service-recompress-0.1-8.1.noarch obs-service-extract_file-0.1-6.1.noarch obs-service-tar_scm-0.2.1-16.1.noarch obs-private-server:~ # rpm -qa | grep osc osc-0.132.6-61.3.noarch Reproducible: Always Steps to Reproduce: 1. Enable the parameter $multiaction_notify_support = 0 in the /usr/lib/obs/server/BSConfig.pm file 2. Restart the OBS instance 3. Access the OBS web interface using the web browser Actual Results: The following error message is reported in the OBS web interface: OBS Web Interface Error: Error Details: Errorcode: unknown Message: <?xml version="1.0" encoding="UTF-8"?> <status code="unknown"> <summary>uncaught exception: Failed to establish connect Expected Results: The OBS should work normally after enabling the parameter $multiaction_notify_support = 0 in the /usr/lib/obs/server/BSConfig.pm file. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.