-
Notifications
You must be signed in to change notification settings - Fork 23
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
Issue with install 5.1 #284
Comments
Perhaps an issue caused by the locale or timezone? if you can share any further details of the system it may allow the issue to be reproduced (e.g. You could check if you have the expected version of euca2ools and dependencies installed:
If that does not help then you could try editing the faststart generated
which causes the service image to be installed in a slightly different way. You can re-run the install using something like:
|
Thanks for the response . Hunting through the log files I have found in cloud-error.log Restarting eucalyptus-cloud shows and debug shows n. May 16 04:43:14 2021 WARN [Topology:eucalyptus-bootstrap-ephemeralconfiguration-bootstrap-topology-external-worker-73] START:DISABLED arn:euca:bootstrap:api.10.0.0.20:loadbalancing:api.10.0.0.20.loadbalancing/ NOTREADY->DISABLED=NOTREADY [LoadBalancingServiceBootstrapper.enable( ): returned false, terminating bootstrap for component: loadbalancing] Sun. May 16 04:43:14 2021 WARN [Topology:eucalyptus-bootstrap-ephemeralconfiguration-bootstrap-topology-external-worker-74] START:DISABLED arn:euca:eucalyptus::imagingbackend:10.0.0.20/ NOTREADY->DISABLED=NOTREADY [ImagingBackendServicePropertyBootstrapper.enable( ): returned false, terminating bootstrap for component: imagingbackend] |
Here is what is seen during a successful s3 interaction:
so it is not clear why you see issues with the same date format. You could check the java version:
and the locale:
You could run this for a quick test with full client debug output to see if that shows any further details around the issue:
if that is successful you can deregister the ami and delete the bucket:
|
Used fresh install minimal install of centos 7.9 no mods
and ran as root
bash <(curl -Ls https://get.eucalyptus.cloud)
Install failed with
fatal: [host1]: FAILED! => {"attempts": 5, "changed": true, "cmd": "set -eu\neval $(clcadmin-assume-system-credentials)\nif ! euctl services.imaging.worker.image services.loadbalancing.worker.image | grep "[ae]mi-" ; then\n esi-install-image --force --remove-all\nfi\nesi-install-image --install-default\n", "delta": "0:00:19.340381", "end": "2021-05-13 20:40:46.944538", "failed_when_result": true, "msg": "non-zero return code", "rc": 1, "start": "2021-05-13 20:40:27.604157", "stderr": "", "stderr_lines": [], "stdout": "Checking if image 'eucalyptus-service-image-v5.0.101' is already installed...\nFound tarball /usr/share/eucalyptus/service-images/eucalyptus-service-image-5.0.101.tar.xz\nChecking env variables\nDecompressing tarball: /usr/share/eucalyptus/service-images/eucalyptus-service-image-5.0.101.tar.xz\nInstalling image from eucalyptus-service-image.raw\nBundling, uploading and registering image to bucket: eucalyptus-service-image-v5.0.101\nError: Unable to install imaging worker due to:\neuca-install-image: error (AccessDenied): Unable to parse date.", "stdout_lines": ["Checking if image 'eucalyptus-service-image-v5.0.101' is already installed...", "Found tarball /usr/share/eucalyptus/service-images/eucalyptus-service-image-5.0.101.tar.xz", "Checking env variables", "Decompressing tarball: /usr/share/eucalyptus/service-images/eucalyptus-service-image-5.0.101.tar.xz", "Installing image from eucalyptus-service-image.raw", "Bundling, uploading and registering image to bucket: eucalyptus-service-image-v5.0.101", "Error: Unable to install imaging worker due to:", "euca-install-image: error (AccessDenied): Unable to parse date."]}
Any thoughts
The text was updated successfully, but these errors were encountered: