You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2026/01/29 03:20:00 UTC
[jira] [Resolved] (YUNIKORN-3214) Web UI not functional in 1.8.0-RC1
[ https://issues.apache.org/jira/browse/YUNIKORN-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wilfred Spiegelenburg resolved YUNIKORN-3214.
---------------------------------------------
Fix Version/s: 1.8.0
Resolution: Fixed
Change tested locally and committed to master and backported into branch-1.8
Master testing is failing due to YUNIKORN-3200, local testing passed
tanks [~ccondit] for finding the solution quickly
> Web UI not functional in 1.8.0-RC1
> ----------------------------------
>
> Key: YUNIKORN-3214
> URL: https://issues.apache.org/jira/browse/YUNIKORN-3214
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: webapp
> Affects Versions: 1.8.0
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.8.0
>
>
> After upgrading to yunikorn-1.8.0-RC1, the yunikorn web UI is non-functional. This appears to have been introduced in YUNIKORN-3073 during the upgrade to Angular 20, as the web content now gets written to a "browser" subdirectory. The solution appears to be adding a "browser": "" section to the "outputPath" angular configuration to force generation in the root directory as before. See [https://stackoverflow.com/a/78047247] for more information.
> Content of dist/yunikorn-web:
> {noformat}
> 3rdpartylicenses.txt
> browser/ <-- contents of this should be at root
> prerendered-routes.json
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org