Configuration-based installation of OpenShift and Cloud Pak for Data/Integration/Watson AIOps on various private and public cloud infrastructure providers. Deployment attempts to achieve the end-state defined in the configuration. If something fails along the way, you only need to restart the process to continue the deployment.
Describe the bug
When running the deployer in the wizard mode, it crashes after the downloading oc with the following error message
Starting Deployer web UI and backend service...
Traceback (most recent call last):
File "webapp.py", line 1, in <module>
from flask import Flask, send_from_directory,request,make_response,send_file
File "/usr/local/lib/python3.8/site-packages/flask/__init__.py", line 7, in <module>
from .app import Flask as Flask
File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 28, in <module>
from . import cli
File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 18, in <module>
from .helpers import get_debug_flag
File "/usr/local/lib/python3.8/site-packages/flask/helpers.py", line 16, in <module>
from werkzeug.urls import url_quote
ImportError: cannot import name 'url_quote' from 'werkzeug.urls' (/usr/local/lib/python3.8/site-packages/werkzeug/urls.py)
To Reproduce
Steps to reproduce the behavior:
Build the container
Run with docker run --rm -it -p 8080:8080 deployer bash
Run the following command in the container: /cloud-pak-deployer/cp-deploy.sh env wizard -v
Observe the crash
Expected behavior
The wizard should work as intended
Desktop (please complete the following information):
OS: MacOS Ventura 13.5.2 / Rancher Desktop
Additional context
Appears to be caused by a new release of Werkzeug, which Flask depends on, and older versions of Flask appear to not specify their dependencies properly
Describe the bug When running the deployer in the wizard mode, it crashes after the downloading
oc
with the following error messageTo Reproduce Steps to reproduce the behavior:
docker run --rm -it -p 8080:8080 deployer bash
/cloud-pak-deployer/cp-deploy.sh env wizard -v
Expected behavior The wizard should work as intended
Desktop (please complete the following information):
Additional context Appears to be caused by a new release of Werkzeug, which Flask depends on, and older versions of Flask appear to not specify their dependencies properly