Hot reload of plugin is broken in 4.14

[iocanel]

After 4.14 release of OpenShift I started experiencing issues with hot reloading of console plugin when developing.
After any change in my plugin code, I was getting a 404 when trying to access the plugin, so I had to do the full (yarn run start and yarn run start-console thing again).

Logs seems clear with no indication of a problem. After exploring the browser console I noticed that the second time browser tries to fetch the console manifest (e.g. http://localhost:9000/api/plugins/quarkus-openshift-console-plugin/plugin-manifest.json) it gets a blank response back.

After rolling back to 4.13 (by changing the start-console.sh script to use 4.13 instead of latest) the issue seems fixed.

[spadgett]

/cc @vojtechszocs @jhadvig

This could be the same as https://issues.redhat.com/browse/OCPBUGS-24607

[Javatar81]

Had the same experience with hot reload. Changing from latest to 4.13 solved the problem.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[spadgett]

/lifecycle frozen

@vojtechszocs FYI since you own the JIRA issue.

I was testing a new plugin created with the template and the origin-console:latest image yesterday, and hot reloading was working for me. @iocanel Do you have a reproducer for us?