| Anonymous | Login | 2024-04-26 03:20 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0013641 | ClearOS | app-base - Base System | public | 2017-03-10 22:37 | 2017-03-14 11:58 | ||||
| Reporter | dloper | ||||||||
| Assigned To | user2 | ||||||||
| Priority | urgent | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 7.3.1 | ||||||||
| Target Version | 7.3.1 Updates | Fixed in Version | 7.3.1 Updates | ||||||
| Summary | 0013641: During wizard, long package update times out and appears stalled | ||||||||
| Description | When there is a significant amount of packages during the wizard, the progress bars will appear to hang. The updates finish normally and a required refresh of the page will show the true status. | ||||||||
| Steps To Reproduce | Install 7.2.0 ISO image, run wizard and the updates in Chrome | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
||||||
|
||||||
 Relationships |
|
Notes |
|
|
(0005121) user2 2017-03-13 10:55 |
The asynchronous webconfig restart event is coming along and restarting webconfig. Will fix. |
|
(0005131) user2 2017-03-13 11:56 |
Correction. The asynchronous event is just fine... webconfig does indeed get restarted after the software update process. The software-updates Ajax call gets caught in a bit of a chicken/egg scenario. There's a change in the clearos-admin-theme that causes a 500 error - see attached. That's not surprising and in fact should be expected in some cases. |
|
(0005141) user2 2017-03-13 12:09 |
It's the change in the location of the upstream proxy app: PHP Fatal error: Class 'clearos\\apps\\network\\Proxy' not found in /usr/clearos/apps/base/libraries/Shell.php on line 180 There's a circular dependency that we want to avoid (app-network <-> app-base), but we can detect and workaround this use case. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2017-03-10 22:37 | dloper | New Issue | |
| 2017-03-13 10:55 | user2 | Note Added: 0005121 | |
| 2017-03-13 10:55 | user2 | Assigned To | => user2 |
| 2017-03-13 10:55 | user2 | Status | new => confirmed |
| 2017-03-13 11:56 | user2 | Note Added: 0005131 | |
| 2017-03-13 11:57 | user2 | Priority | low => urgent |
| 2017-03-13 12:09 | user2 | Note Added: 0005141 | |
| 2017-03-13 13:28 | user2 | Issue cloned: 0013731 | |
| 2017-03-13 13:28 | user2 | Relationship added | related to 0013731 |
| 2017-03-13 13:56 | user2 | Status | confirmed => resolved |
| 2017-03-13 13:56 | user2 | Fixed in Version | => 7.3.1 Updates |
| 2017-03-13 13:56 | user2 | Resolution | open => fixed |
| 2017-03-14 11:58 | user2 | Status | resolved => closed |
|
Issue History |