Open Bug 556612 Opened 16 years ago Updated 1 year ago

Unable to edit build field in the Test Runs (tr_show_plan.cgi) page

Categories

(Testopia :: General, defect, P1)

x86
Windows XP

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: danf0207, Assigned: gregaryh)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100202 Firefox/3.5.8 (.NET CLR 3.5.30729) Build Identifier: 2.2 After double clicking the build to edit in the run the following error is displayed. I looked at the table data and all look okay. There was an error loading the data: {"success":false,"error":"testopia-missing-parameter","message":"Missing required parameter product_id"} Reproducible: Always Steps to Reproduce: 1. Select a plan the a run. 2. Double click on the build in any run to edit and the following error is displayed. This system was upgraded from bugzilla 3.0.6 / testopia 2.2 to bugzilla 3.4.4 / testopia 2.3. The upgrade was almost painless. I had to resize some column id's to get the foreign keys to pass but after that I had no issues with the upgrade. Actual Results: can't edit the build Expected Results: the build would be editable
Priority: -- → P1
Version: unspecified → 2.3
This also fails on a fresh Bugzilla 3.4.5 / Testopia 2.3 installation
Checking perl modules... Checking for CGI.pm (v3.21) ok: found v3.48 Checking for Digest-SHA (any) ok: found v5.48 Checking for TimeDate (v2.21) ok: found v2.24 Checking for DateTime (v0.28) ok: found v0.55 Checking for DateTime-TimeZone (v0.71) ok: found v1.14 Checking for DBI (v1.41) ok: found v1.609 Checking for Template-Toolkit (v2.22) ok: found v2.22 Checking for Email-Send (v2.00) ok: found v2.198 Checking for Email-MIME (v1.861) ok: found v1.903 Checking for Email-MIME-Encodings (v1.313) ok: found v1.313 Checking for Email-MIME-Modifier (v1.442) ok: found v1.903 Checking for URI (any) ok: found v1.35 Checking for JSON (v2.10) ok: found v2.18 Checking for Text-Diff (v0.35) ok: found v0.35 Checking for GD-Graph3d (v0.63) ok: found v0.63 Checking available perl DBD modules... Checking for DBD-Pg (v1.45) not found Checking for DBD-mysql (v4.00) ok: found v4.00 Checking for DBD-Oracle (v1.19) not found The following Perl modules are optional: Checking for GD (v1.20) ok: found v2.44 Checking for Chart (v1.0) ok: found v2.4.1 Checking for Template-GD (any) ok: found v1.56 Checking for GDTextUtil (any) ok: found v0.86 Checking for GDGraph (any) ok: found v1.44 Checking for XML-Twig (any) ok: found v3.34 Checking for MIME-tools (v5.406) ok: found v5.427 Checking for libwww-perl (any) ok: found v2.033 Checking for PatchReader (v0.9.4) ok: found v0.9.5 Checking for PerlMagick (any) ok: found v6.5.7 Checking for perl-ldap (any) ok: found v0.4001 Checking for Authen-SASL (any) ok: found v2.14 Checking for RadiusPerl (any) ok: found v0.17 Checking for SOAP-Lite (v0.710.06) not found Checking for HTML-Parser (v3.40) ok: found v3.55 Checking for HTML-Scrubber (any) ok: found v0.08 Checking for Email-MIME-Attachment-Stripper (any) ok: found v1.316 Checking for Email-Reply (any) ok: found v1.202 Checking for TheSchwartz (any) ok: found v1.10 Checking for Daemon-Generic (any) ok: found v0.61 Checking for mod_perl (v1.999022) ok: found v2.000002 Checking for Text-CSV (v1.06) ok: found v1.17 Checking for XML Schema Validator (v1.10) ok: found v1.10 Checking for XML Schema Parser (any) ok: found v1.01 Checking for XML Twig (any) ok: found v3.34
As a work around. Try going to the product dashboard and selecting the product you want to work with from the folder list on the left.
I tried this as I saw it recommended for another issue. It worked to the other issue which I beleive was a problem with create new test run. Selecting the product resolved this but not my issue.
I tried this as I saw it recommended for another issue. It worked to the other issue which I beleive was a problem with create new test run. Selecting the product resolved this but not my issue.

It looks like you are encountering an issue with Testopia, an extension for Bugzilla, after upgrading from version 2.2 to version 2.3. The error message indicates a missing parameter "product_id" when trying to edit a build.

Here are some steps you can take to troubleshoot and resolve this issue:

Check Configuration Settings:
Ensure that your Testopia configuration settings are correct, especially those related to product and product version. Check if the product_id parameter is set correctly in the configuration.

Review Database Schema:
Since you've upgraded the system, make sure that the database schema has been updated correctly. Verify that all the required fields and tables are present in the new version of Testopia.

Logs and Debugging:
Check the Bugzilla and Testopia logs for any additional error messages or warnings. Enable debugging if necessary to get more detailed information about the error. This can often provide insights into what's going wrong.

Database Integrity:
Verify the integrity of your Bugzilla and Testopia databases. Ensure that foreign key relationships are maintained and that there are no missing or corrupted records.

Re-run Upgrade Scripts:
Check if there are any additional upgrade scripts that need to be run after the main upgrade. Sometimes, there are post-upgrade steps that need to be performed to finalize the upgrade process.

Community Support:
Reach out to the Bugzilla and Testopia community for support. You can check forums, mailing lists, or other community resources to see if others have encountered similar issues and if there are known solutions or workarounds.

Check for Updates:
Ensure that you are using the latest version of Testopia compatible with Bugzilla 3.4.4. Developers often release updates and patches to address issues in newer versions.

Customizations:
If you have made any customizations to Testopia, review them carefully to see if they might be causing the issue. Sometimes, custom code or configurations can lead to unexpected behavior after an upgrade.

By going through these steps, you should be able to identify the root cause of the problem and take appropriate action to resolve the issue. If the problem persists, reaching out to the https://checkricepurity.com/ community or the maintainers of the software may provide additional assistance.

<p>Reproducible: Always</p>
<p><a href="http://handmade-uae.com/">Steps</a> to Reproduce:<br />1. Select a plan the a run.<br />2. Double click on the build in any run to <a href="https://shrt.autos/oppo88-lk1">edit</a> and the following <a href="https://ysance-media.prestashop.com/">error</a> is <a href="https://shrt.autos/oppo-lk2">displayed</a>.</p>
<p>This system was <a href="https://shrt.autos/oppo88clocking">upgraded</a> from bugzilla 3.0.6 / testopia 2.2 to <a href="https://imeelee.gouwu.vip.xunlei.com/">bugzilla</a> 3.4.4 / testopia 2.3. The upgrade was almost painless. I had to resize some column id's to get the foreign keys to pass but after that I had no <a href="https://shortgo.click/vjafrn">issues</a> with the <a href="https://shrt.autos/JvMFFV">upgrade</a>.<br />Actual Results: <br />can't edit the build</p>
<p>Expected Results: <br />the build would be editable</p>

You need to log in before you can comment on or make changes to this bug.