Bug 1890070
| Summary: | MTC web console can NOT be accessed after deloying MTC 1.3.1 stage images | ||
|---|---|---|---|
| Product: | Migration Toolkit for Containers | Reporter: | whu |
| Component: | General | Assignee: | Jason Montleon <jmontleo> |
| Status: | VERIFIED --- | QA Contact: | Xin jiang <xjiang> |
| Severity: | urgent | Docs Contact: | Avital Pinnick <apinnick> |
| Priority: | unspecified | ||
| Version: | 1.3.z | CC: | jmontleo, sregidor, whu, xjiang |
| Target Milestone: | --- | ||
| Target Release: | 1.3.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This is due to errors in the downstream Dockerfile from updating to nodejs 1.12 and aligning it better to upstream. Verified using 1.3.2 stage
openshift-migration-rhel7-operator@sha256:2eafc06e24cf1b815906f3eb4ba5ddd3362b607d26605d594a7ef17a51059d7e
- name: MIG_UI_REPO
value: openshift-migration-ui-rhel8@sha256
- name: MIG_UI_TAG
value: 44c9be260fcfa6e2a854f58d3498c620483ac6c360e811811401de266e895e43
We can access the UI without problems.
Moved to VERIFIED
|
Description of Problem: After deloying MTC 1.3.1 stage images, MTC web console can NOT be accessed Version-Release number of selected component (if applicable): MTC 1.3.1 stage image: registry.redhat.io/rhmtc/openshift-migration-rhel7-operator@sha256:012be3e63822bdc28de249edc118cc40a6fdced9645aa3a97c5b600bc85a2c9d name: MIG_UI_TAG value:6550d490a36a31e68c039f1fe6c23bb77fd3d9b71798beb1ea71d90461308b81 How Reproducible: Always Steps to Reproduce: 1 install MTC from stage repository 2 check MTC migration-ui pod logs Actual Results: 1 when open MTC web concole from browser, get error message 2 check MTC migration-ui pod logs, get the same error Expected Results: MTC web console can be accessed successfully Additional info: $ oc logs migration-ui-6fc9b88fc5-rmvk2 -n openshift-migration migMetaFile: /etc/mig-ui/migmeta.json viewsDir: /opt/app-root/src/staticroot staticDir: /opt/app-root/src/staticroot migMeta: {"clusterApi": "https://api.whu46gcp4.qe.gcp.devcluster.openshift.com:6443", "namespace": "openshift-migration", "discoveryApi": "https://discovery-openshift-migration.apps.whu46gcp4.qe.gcp.devcluster.openshift.com", "configNamespace": "openshift-config", "hookRunnerImage": "registry.redhat.io/rhmtc/openshift-migration-hook-runner-rhel7@sha256:779af420a02683fc8288b56d70e1d026fdc790f7248d4aa68a256b811c20608e", "oauth": {"redirectUrl": "https://migration-openshift-migration.apps.whu46gcp4.qe.gcp.devcluster.openshift.com/login/callback", "clientSecret": "MzBjMDEwNWEtZmE1NS01YjE5LTkyMDMtYTdkYjAyM2Y2N2Qy", "userScope": "user:full", "clientId": "migration"}} App listening on port 9000 Error: Failed to lookup view "index.ejs" in views directory "/opt/app-root/src/staticroot" at Function.render (/opt/app-root/src/node_modules/express/lib/application.js:580:17) at ServerResponse.render (/opt/app-root/src/node_modules/express/lib/response.js:1012:7) at /opt/app-root/src/main.js:32:7 at Layer.handle [as handle_request] (/opt/app-root/src/node_modules/express/lib/router/layer.js:95:5) at next (/opt/app-root/src/node_modules/express/lib/router/route.js:137:13) at Route.dispatch (/opt/app-root/src/node_modules/express/lib/router/route.js:112:3) at Layer.handle [as handle_request] (/opt/app-root/src/node_modules/express/lib/router/layer.js:95:5) at /opt/app-root/src/node_modules/express/lib/router/index.js:281:22 at param (/opt/app-root/src/node_modules/express/lib/router/index.js:354:14) at param (/opt/app-root/src/node_modules/express/lib/router/index.js:365:14)