Red Hat Bugzilla – Bug 833652
add new make feature does't work from show.cgi
Last modified: 2012-11-15 22:03:42 EST
new make can't be added through the "Add a New Make"
Vendor entered make as "SuperStorage Server", and catalog reported it as "invalid make"
When I try to add this new make name with edit function:
1. click edit link at the right hand;
2. click "Add a New Make" option button and input "SuperStorage Server" in text field;
3. click "save change" button;
4. not happned, catalog still reported "invalid make"
(In reply to comment #0)
> new make can't be added through the "Add a New Make"
> Vendor entered make as "SuperStorage Server", and catalog reported it as
> "invalid make"
> When I try to add this new make name with edit function:
> 1. click edit link at the right hand;
> 2. click "Add a New Make" option button and input "SuperStorage Server" in
> text field;
> 3. click "save change" button;
> 4. not happned, catalog still reported "invalid make"
If you add a new make via the cert's page, it just adds the new make to that cert only. Then catalog will check if the newly added make is valid make name based on the make list in hwcert db. In order to make the "invalid make" disappear, you need to use "admin" page to add the new make for the vendor (in your case, you need to add "SuperStorage Server" make to "Super Micro Computer, Inc." vednor via admin page.)
I think we can improve the UI by allowing reviewers to confirm the addition of a make directly in the certification. As it sits, add new make in the certify doesn't actually add a new make it only sets the whiteboard. This will simplify and clarify the experience.
Add a feature to allow reviewers to approve the new make as invalid make (add the new make into makes table) in show.cgi page.
Move this bug to hybrid5.
Created attachment 593373 [details]
add a checkbox for reviewers to approve a new make as a valid make via cert page
Reviewers can select "Approve it as a valid make" checkbox to mark a make as a valid make
*** Bug 836128 has been marked as a duplicate of this bug. ***
Is there a test site with this patch?
Verified in web2