Bug 1130926

Summary:	Entering RHEL7 kernel bug without choosing kernel subcomponent results in a traceback error
Product:	[Community] Bugzilla	Reporter:	Pasi Karkkainen <pasik>
Component:	Creating/Changing Bugs	Assignee:	Matt Tyson 🤬 <mtyson>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4	CC:	jmcdonal, mtyson, pasik, qgong, szhou
Target Milestone:	4.4
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.4.5025	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-10 02:47:42 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:

Description Pasi Karkkainen 2014-08-18 08:15:22 UTC

Description of problem:

Filing a new RHEL7 kernel bug without selecting a kernel sub-component results in a traceback error (below).


Version-Release number of selected component (if applicable):
Current version of redhat bugzilla as of August 2014.

How reproducible:
Always.

Steps to Reproduce:
1. Start filing a new RHEL7 bug.
2. Component: kernel
3. Do *NOT* choose a sub-component for kernel.
4. Fill in other details
5. Submit -> traceback error.

Actual results:
You get a traceback crash instead of normal warning about missing selection in kernel sub-category.

Expected results:
Works normally, so you get a normal warning about missing selection in kernel sub-category, when it's a required field.


Additional info:

traceback:

An unexpected error occurred. This could be a temporary problem, or some code is behaving incorrectly. If this problem persists, please email this page to bugzilla-owner with details of what you were doing at the time this message appeared.

URL: https://bugzilla.redhat.com/post_bug.cgi
Invalid parameter passed to Bugzilla::Extension::SubComponents::RHSubComponent::_init: It must be numeric.

Traceback:

 at /var/www/html/bugzilla/Bugzilla/Object.pm line 76
        Bugzilla::Object::_init(...) called at /var/www/html/bugzilla/Bugzilla/Object.pm line 48
        Bugzilla::Object::new(...) called at /var/www/html/bugzilla/extensions/SubComponents/Extension.pm line 793
        Bugzilla::Extension::SubComponents::bug_before_create(...) called at /var/www/html/bugzilla/Bugzilla/Hook.pm line 18
        Bugzilla::Hook::process(...) called at /var/www/html/bugzilla/Bugzilla/Bug.pm line 754
        Bugzilla::Bug::create(...) called at /var/www/html/bugzilla/post_bug.cgi line 153
        ModPerl::ROOT::Bugzilla::ModPerl::ResponseHandler::var_www_html_bugzilla_post_bug_2ecgi::handler(...) called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 204
        eval {...} called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 204
        ModPerl::RegistryCooker::run(...) called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 170
        ModPerl::RegistryCooker::default_handler(...) called at /usr/lib64/perl5/vendor_perl/ModPerl/Registry.pm line 31
        ModPerl::Registry::handler(...) called at /var/www/html/bugzilla/mod_perl.pl line 134
        Bugzilla::ModPerl::ResponseHandler::handler(...) called at -e line 0
        eval {...} called at -e line 0

Comment 1 Pasi Karkkainen 2014-08-18 08:18:28 UTC

And the URL I used to enter the bug was:
https://bugzilla.redhat.com/enter_bug.cgi

Comment 4 Matt Tyson 🤬 2014-08-25 00:59:04 UTC

The solution to this will be to allow the bug to be created without a sub component.

Comment 6 Shirley Zhou 2014-08-26 02:18:02 UTC

Thanks for Matt's clarification. 

Tested this bug with javascript enabled, redhat and non-redhat user can create bug with sub component specify, and there is warning message "You must be specify kernel sub component"  show out when try to create kernel bug without sub component selected.

So moving this bug to verified.

Comment 7 Matt Tyson 🤬 2014-09-10 02:47:42 UTC

This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.