-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XO deploy script with http proxy #7528
Comments
First, ping @stormi because I'm not even sure about the proxy modification in XCP-ng in the first place. |
And ping @julien-f about the import script |
And finally thank you @kevemueller for the report 😉 |
Short update on the change for There is no need to restart anything, changes to the enviroment are effective after re-logon or sourcing of What remains is the bug in
As the URL cannot be reached by I have not found a repository with the deploy script, so @julien-f I suggest this is only you who can change it. If you are not happy with the suggested fix above, anything that catches the error condition of |
Re-ping @julien-f |
@kevemueller I have deployed a new version of the script that should correctly handle the fallback. That would be great if you could test it :) |
Are you using XOA or XO from the sources?
XOA
Which release channel?
stable
Provide your commit number
No response
Describe the bug
In an environment with no direct http access (only via proxy), after a fresh installation of xcp-ng, the xoa deployment fails.
The XCP-ng environment is minimally altered:
/etc/environment
EnvironmentFile=/etc/environment
in/usr/lib/systemd/system/xapi.service
Command line tools yum, wget, curl work well with the proxy.
"Quick Deploy" from xapi dashboard, fails with
"INTERNAL_ERROR", Unix.ECONNREFUSED
bash -c "$(wget -qO- https://xoa.io/deploy)"
fails withI have not found the script source to post a patch against.
Error message
No response
To reproduce
Connect to the XCP-ng host and run
bash -c "$(wget -qO- https://xoa.io/deploy)
The process fails after downloading the deployment script.
Expected behavior
The deployment script should import the appliance.
There is a coding logic error in the script. It is run with set -e (fail after first error), which is good practice, but it is not prepared to gracefully catch the
xe vm-import
. The subsequent fallback code is never executed, as set -e bails the execution.a possible workaround is
With this script XO can be sucessfully deployed behind a http proxy.
Screenshots
No response
Node
?
Hypervisor
XCP-ng 8.2.1
Additional context
No response
The text was updated successfully, but these errors were encountered: