Virtual Images error installing, port 8500 connection refused. #379
-
|
Hi, Following the installation instructions for the VM image, I'm encountering a number of errors. Whatever you're expecting to be on port 8500 seems absent (I've checked firewall rules + looked for a listen on that port). All services described in the installation troubleshooting section are up, but the "cluster" is down. I've had the same results with both of the virtual image packages. Command to reproduce (as root): sh /opt/seagate/cortx/provisioner/cli/virtual_appliance/bootstrap.shOutput: INFO: Configuring haproxy |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 4 replies
-
|
Thank you for reporting this @srmcdowell and I apologize for the difficulties! What hypervisor are you using? |
Beta Was this translation helpful? Give feedback.
-
|
I have similar issues on ESX 7.0. I think one of the issues is that interfaces ens224 and ens256 assume you have DHCP provisioning IP addresses. I was able to get further by manually editing ifcfg-ens224 and ifcfg-ens256 to assign IPs manually prior to running bootstrap.sh. I can get further and the mgmt UI is now responding, but I can't get S3 to work. |
Beta Was this translation helpful? Give feedback.
-
|
thanks @d283w for mentioning this. @srmcdowell I'm wondering whether you can run For reference -> Here is my output when I run it.
|
Beta Was this translation helpful? Give feedback.
-
|
Something's going wrong with the process to modify haproxy.cfg and /etc/hosts �[0;31m----------�[0;0m INFO: Configuring s3 ips in /etc/hosts Manually modifying both files to remove the 192.168.X.X references, replacing with the IP for the ens256 interface finally resulted in success for the s3-sanity-test. |
Beta Was this translation helpful? Give feedback.
-
|
@srmcdowell , can you please try the instructions from @d283w and @justinzw to see if that works for you? |
Beta Was this translation helpful? Give feedback.
-
|
These instructions seems have done the trick -- thanks! I'd maintain that this is an issue, since the VMs aren't usable without corrective action (that is only documented here) is required by the end-user. |
Beta Was this translation helpful? Give feedback.
-
|
@justinzw , is this a Discussion or an Issue? |
Beta Was this translation helpful? Give feedback.
-
|
yah I agree with @srmcdowell that this is an issue. |
Beta Was this translation helpful? Give feedback.
-
|
Can we transfer it to an Issue? I couldn’t see how.... |
Beta Was this translation helpful? Give feedback.
-
|
created issue https://github.com/Seagate/cortx/issues/580 |
Beta Was this translation helpful? Give feedback.
Something's going wrong with the process to modify haproxy.cfg and /etc/hosts
�[0;31m----------�[0;0m
�[0;31m ID: Setup HAProxy config�[0;0m
�[0;31mFunction: file.managed�[0;0m
�[0;31m Name: /etc/haproxy/haproxy.cfg�[0;0m
�[0;31m Result: False�[0;0m
�[0;31m Comment: Unable to manage file: Jinja variable list object has no element 0�[0;0m
�[0;31m Started: 18:09:57.376345�[0;0m
�[0;31mDuration: 177.684 ms�[0;0m
�[0;31m Changes: �[0;0m
INFO: Configuring s3 ips in /etc/hosts
�[0;1;31msrvnode-1:�[0;0m
�[0;1;31mData failed to compile:�[0;0m
�[0;1;31m----------
Rendering SLS 'base:components.s3server.config_hosts' failed: Jinja variable list object has no element 0�[0;0m
Manually modifying both …