The settings file for heat-ui contains a syntax error which prevents Horizon from starting up properly. Can not exec settings snippet _1699_orchestration_settings.py Traceback (most recent call last): File "/usr/share/openstack-dashboard/openstack_dashboard/settings.py", line 272, in <module> exec(f.read()) File "<string>", line 29 'level': 'INFO', ^ SyntaxError: invalid syntax
The issue was introduced by puppet-horizon changes which were backported to solve bz 1938217 . The same issue exists in the three dashboard plugins(heat-ui, manila-ui and octavia-ui).
(In reply to Takashi Kajinami from comment #3) > The issue was introduced by puppet-horizon changes which were backported to > solve bz 1938217 . > > The same issue exists in the three dashboard plugins(heat-ui, manila-ui and > octavia-ui). The issue with horizon-dashboard was somehow fixed between stable/victoria and stable/ussuri, so the issue does not affect RHOSP16.2. However the syntax error in octavia-dashboard and manila-dashboard is present in stable/train, which makes RHOSP16.2 affected by the issue when Manila or Octavia is enabled...
(In reply to Takashi Kajinami from comment #4) > (In reply to Takashi Kajinami from comment #3) > ... > > However the syntax error in octavia-dashboard and manila-dashboard is > present in stable/train, > which makes RHOSP16.2 affected by the issue when Manila or Octavia is > enabled... Fortunately the patches[1] to enable these implementations are not included in upcoming RHOSP16.2.2, so RHOSP16.2 is not yet affected. So what we need is to ensure the fix for puppet-horizon is included in RHOSP16.2.3.
Reposting to fix the missing link [1] [1] https://review.opendev.org/q/topic:puppet-horizon-dashboards-stable%252Ftrain
https://review.opendev.org/c/openstack/puppet-horizon/+/834745/ is merged, what's the next step here?
@ykaul I can see the patch is imported to our rhos-17.0-trunk-patches, so there is nothing left for us to do — it will be included in the next build.
(In reply to Radomir Dopieralski from comment #8) > @ykaul I can see the patch is imported to our > rhos-17.0-trunk-patches, so there is nothing left for us to do — it will be > included in the next build. Need to make sure they do get in (comment #8 is a month old) and delivered to QE.
It's included in RHOS-17.0-RHEL-8-20220520.n.1 according to LADA.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2022:6543
This comment was flagged as spam, view the edit history to see the original text if required.