Back to bug 1303132
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Vladimir Astafiev | 2016-01-30 03:06:44 UTC | CC | v.astafiev | |
| Shirly Radco | 2016-01-31 08:34:56 UTC | Target Milestone | --- | ovirt-3.6.6 |
| oVirt Team | --- | Reports | ||
| Flags | ovirt-3.6.z? planning_ack? testing_ack? | |||
| Yedidyah Bar David | 2016-01-31 15:07:13 UTC | CC | alex | |
| Flags | needinfo?(alex) | |||
| Alexander Wigen | 2016-01-31 21:50:55 UTC | Flags | needinfo?(alex) | |
| Yedidyah Bar David | 2016-02-01 07:34:21 UTC | Summary | engine-setup js-ant failed to execute | engine-setup js-ant failed to execute with java 1.8 |
| Shirly Radco | 2016-02-01 14:22:32 UTC | Assignee | sradco | didi |
| Yedidyah Bar David | 2016-02-21 15:21:16 UTC | Link ID | oVirt gerrit 53773 | |
| Status | NEW | POST | ||
| See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1140746 | |||
| Doron Fediuck | 2016-02-23 08:25:51 UTC | CC | dfediuck | |
| Shirly Radco | 2016-02-25 10:17:16 UTC | CC | sradco | |
| Target Milestone | ovirt-3.6.6 | ovirt-3.6.5 | ||
| Yaniv Lavi | 2016-02-25 12:45:11 UTC | CC | ydary | |
| Flags | planning_ack? | planning_ack+ | ||
| Pavel Novotny | 2016-02-25 13:53:50 UTC | QA Contact | pstehlik | pkubica |
| Flags | testing_ack? | testing_ack+ | ||
| Red Hat Bugzilla Rules Engine | 2016-02-25 13:53:57 UTC | Flags | ovirt-3.6.z? | ovirt-3.6.z+ |
| Yedidyah Bar David | 2016-03-02 10:19:18 UTC | Status | POST | MODIFIED |
| Yedidyah Bar David | 2016-03-07 08:18:10 UTC | Doc Text | Cause: jaseperreports does not work well with java 1.8. The reports package required java 1.7 but did not conflict with 1.8. Consequence: If a machine had both java 1.7 and 1.8 installed, and 1.8 was the default, jasperreports would fail during engine-setup. Fix: The Reports package was changed to conflict with java 1.8. Result: jasperreports does not fail. A workaround for previous versions is to change the default back to 1.7 using 'update-alternatives --config java'. |
|
| Yedidyah Bar David | 2016-03-07 13:22:11 UTC | CC | v.badalyan | |
| Shirly Radco | 2016-03-08 09:46:14 UTC | Blocks | 1315631 | |
| David | 2016-03-30 11:53:08 UTC | CC | dmc | |
| Sandro Bonazzola | 2016-03-31 07:49:11 UTC | Status | MODIFIED | ON_QA |
| Target Release | --- | 3.6.5 | ||
| Petr Kubica | 2016-04-01 08:54:15 UTC | Status | ON_QA | VERIFIED |
| Yedidyah Bar David | 2016-04-03 09:30:30 UTC | Status | VERIFIED | ASSIGNED |
| Red Hat Bugzilla Rules Engine | 2016-04-03 09:30:37 UTC | Target Release | 3.6.5 | --- |
| Yedidyah Bar David | 2016-04-03 13:36:19 UTC | Link ID | oVirt gerrit 55618 | |
| Link ID | oVirt gerrit 55619 | |||
| Status | ASSIGNED | POST | ||
| Link ID | oVirt gerrit 55606 | |||
| Shirly Radco | 2016-04-04 07:10:47 UTC | CC | nsednev | |
| Gil Klein | 2016-04-04 08:59:35 UTC | CC | gklein | |
| Severity | medium | urgent | ||
| Gil Klein | 2016-04-04 09:02:09 UTC | Keywords | Regression | |
| Yedidyah Bar David | 2016-04-04 11:35:46 UTC | Status | POST | MODIFIED |
| Status | MODIFIED | POST | ||
| Yedidyah Bar David | 2016-04-04 12:38:33 UTC | Link ID | oVirt gerrit 55648 | |
| Link ID | oVirt gerrit 55649 | |||
| Link ID | oVirt gerrit 55650 | |||
| Status | POST | MODIFIED | ||
| Yedidyah Bar David | 2016-04-04 12:41:42 UTC | Doc Text | Cause: jaseperreports does not work well with java 1.8. The reports package required java 1.7 but did not conflict with 1.8. Consequence: If a machine had both java 1.7 and 1.8 installed, and 1.8 was the default, jasperreports would fail during engine-setup. Fix: The Reports package was changed to conflict with java 1.8. Result: jasperreports does not fail. A workaround for previous versions is to change the default back to 1.7 using 'update-alternatives --config java'. | Cause: jaseperreports does not work well with java 1.8. The engine works with both 1.7 and 1.8. There is a single script to choose which java to use, used by both the engine and reports, and it accepts both. The reports package required java 1.7 but did not conflict with 1.8. Consequence: If a machine had both java 1.7 and 1.8 installed, and 1.8 was the default, jasperreports would fail during engine-setup. Fix: The code was changed to allow different java versions for engine and reports - 1.7 or 1.8 for the engine and only 1.7 for reports. Result: jasperreports does not fail. A workaround for previous versions is to change the default back to 1.7 using 'update-alternatives --config java'. |
| Shirly Radco | 2016-04-04 12:41:43 UTC | Target Release | --- | 3.6.5 |
| Doc Text | Cause: jaseperreports does not work well with java 1.8. The engine works with both 1.7 and 1.8. There is a single script to choose which java to use, used by both the engine and reports, and it accepts both. The reports package required java 1.7 but did not conflict with 1.8. Consequence: If a machine had both java 1.7 and 1.8 installed, and 1.8 was the default, jasperreports would fail during engine-setup. Fix: The code was changed to allow different java versions for engine and reports - 1.7 or 1.8 for the engine and only 1.7 for reports. Result: jasperreports does not fail. A workaround for previous versions is to change the default back to 1.7 using 'update-alternatives --config java'. | Cause: jaseperreports does not work well with java 1.8. The reports package required java 1.7 but did not conflict with 1.8. Consequence: If a machine had both java 1.7 and 1.8 installed, and 1.8 was the default, jasperreports would fail during engine-setup. Fix: The Reports package was changed to conflict with java 1.8. Result: jasperreports does not fail. A workaround for previous versions is to change the default back to 1.7 using 'update-alternatives --config java'. |
||
| Yedidyah Bar David | 2016-04-04 12:54:25 UTC | Doc Text | Cause: jaseperreports does not work well with java 1.8. The reports package required java 1.7 but did not conflict with 1.8. Consequence: If a machine had both java 1.7 and 1.8 installed, and 1.8 was the default, jasperreports would fail during engine-setup. Fix: The Reports package was changed to conflict with java 1.8. Result: jasperreports does not fail. A workaround for previous versions is to change the default back to 1.7 using 'update-alternatives --config java'. | Cause: jaseperreports does not work well with java 1.8. The engine works with both 1.7 and 1.8. There is a single script to choose which java to use, used by both the engine and reports, and it accepts both. The reports package required java 1.7 but did not conflict with 1.8. Consequence: If a machine had both java 1.7 and 1.8 installed, and 1.8 was the default, jasperreports would fail during engine-setup. Fix: The code was changed to allow different java versions for engine and reports - 1.7 or 1.8 for the engine and only 1.7 for reports. Result: jasperreports does not fail. A workaround for previous versions is to change the default back to 1.7 using 'update-alternatives --config java'. |
| Shirly Radco | 2016-04-06 05:46:32 UTC | Status | MODIFIED | ON_QA |
| Target Release | 3.6.5 | 3.6.5.1 | ||
| Gil Klein | 2016-04-06 06:35:39 UTC | Priority | unspecified | urgent |
| Yedidyah Bar David | 2016-04-06 12:11:43 UTC | Blocks | 1324473 | |
| Yedidyah Bar David | 2016-04-06 12:13:01 UTC | Blocks | 1324473 | |
| Depends On | 1324473 | |||
| Yedidyah Bar David | 2016-04-10 09:11:58 UTC | CC | jbelka | |
| Lukas Svaty | 2016-04-14 08:50:17 UTC | Status | ON_QA | VERIFIED |
| CC | lsvaty | |||
| Sandro Bonazzola | 2016-04-21 14:35:24 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2016-04-21 10:35:24 UTC |
Back to bug 1303132