solo-io / gloo-portal-issues

Public tracker for issues related to Gloo Portal
https://docs.solo.io/gloo-portal/latest/
1 stars 3 forks source link

Empty portal spec displaying no web UI #151

Closed jameshbarton closed 2 years ago

jameshbarton commented 2 years ago

Describe the bug I have an empty Portal spec with no published environments. The portal is accepted and generates nothing unusual in the logs, just this expected entry in the portal controller logs after the Portal yaml is applied:

{"level":"info","ts":"2021-12-21T18:45:41.639Z","logger":"gloo_portal","msg":"updated Portal status","portal":"example-portal.default","status":{"observed_generation":1,"state":4}}

However, navigating a browser to http://portal.solo.io (address resolved via local /etc/hosts) just gives a blank interface. Here are the results of View Source from Chrome:

<!doctype html>
<html lang="en">
   <head>
      <meta charset="utf-8"/>
      <link rel="icon" id="favicon" href="default-favicon.png"/>
      <meta name="viewport" content="width=device-width,initial-scale=1"/>
      <meta name="theme-color" content="#000000"/>
      <meta name="description" content="A portal for your Gloo'd together APIs"/>
      <link rel="apple-touch-icon" href="/logo192.png"/>
      <link rel="manifest" href="/manifest.json"/>
      <title id="page-title">Solo.io Gloo Portal</title>
      <link href="/static/css/2.a1951d86.chunk.css" rel="stylesheet">
      <link href="/static/css/main.9f4fffb6.chunk.css" rel="stylesheet">
   </head>
   <body>
      <noscript>You need to enable JavaScript to run this app.</noscript>
      <div id="root"></div>
      <script>!function(e){function r(r){for(var n,i,l=r[0],f=r[1],a=r[2],c=0,s=[];c<l.length;c++)i=l[c],Object.prototype.hasOwnProperty.call(o,i)&&o[i]&&s.push(o[i][0]),o[i]=0;for(n in f)Object.prototype.hasOwnProperty.call(f,n)&&(e[n]=f[n]);for(p&&p(r);s.length;)s.shift()();return u.push.apply(u,a||[]),t()}function t(){for(var e,r=0;r<u.length;r++){for(var t=u[r],n=!0,l=1;l<t.length;l++){var f=t[l];0!==o[f]&&(n=!1)}n&&(u.splice(r--,1),e=i(i.s=t[0]))}return e}var n={},o={1:0},u=[];function i(r){if(n[r])return n[r].exports;var t=n[r]={i:r,l:!1,exports:{}};return e[r].call(t.exports,t,t.exports,i),t.l=!0,t.exports}i.m=e,i.c=n,i.d=function(e,r,t){i.o(e,r)||Object.defineProperty(e,r,{enumerable:!0,get:t})},i.r=function(e){"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},i.t=function(e,r){if(1&r&&(e=i(e)),8&r)return e;if(4&r&&"object"==typeof e&&e&&e.__esModule)return e;var t=Object.create(null);if(i.r(t),Object.defineProperty(t,"default",{enumerable:!0,value:e}),2&r&&"string"!=typeof e)for(var n in e)i.d(t,n,function(r){return e[r]}.bind(null,n));return t},i.n=function(e){var r=e&&e.__esModule?function(){return e.default}:function(){return e};return i.d(r,"a",r),r},i.o=function(e,r){return Object.prototype.hasOwnProperty.call(e,r)},i.p="/";var l=this.webpackJsonpui=this.webpackJsonpui||[],f=l.push.bind(l);l.push=r,l=l.slice();for(var a=0;a<l.length;a++)r(l[a]);var p=f;t()}([])</script><script src="/static/js/2.71cc5e45.chunk.js"></script><script src="/static/js/main.0871e48e.chunk.js"></script>
   </body>
</html>

Based on that message, I confirmed that JavaScript is enabled in Chrome. In addition to Chrome (regular and incognito), I also tried this from Safari with the same result.

To Reproduce

  1. Unpack attached portal-none.yaml.gz
  2. Point local /etc/hosts for portal.solo.io to your glooctl proxy address
  3. kubectl apply -f portal-none.yaml
  4. Point browser to http://portal.solo.io
  5. Observe blank UI.

Expected behavior I expect to see a proper Portal UI shell interface containing no published APIs.

Additional context

jameshbarton commented 2 years ago

Wiped out Edge and Portal installations and re-installed same versions from scratch. Problem has magically vanished. Closing out the issue.