As per the messages in the installation log, the process it is failing in 'aws_metadata.py' script.
This happens when installing Vertica on a server part of OpenStack cloud, or Amazon Web Services (AWS).
There is a related discussion about this problem in Vertica blog, although referred to Vertica 7.x and CentOS it should be valid also for Vertica 8.x and Linux RHEL - refer to:
According to the above discussion, it is noted that this problem can happen when installing Vertica on OpenStack cloud:
The root of the problem is that if you are installing Vertica on OpenStack it will have a metadata server (169.254.169.254), and if the install python script gets a response from it, it assumes its running under AWS, so it will request AWS specific metadata which doesn't exist, so it gets no response from the OpenStack metadata server.
To fix the issue, edit the file 'aws_metadata.py' (found under /opt/vertica/oss/ python/lib/python2.7/site-ackages/vertica/system/aws_metadata.py)
Inside the 'def load' function (not in the 'def init') change the self.is_aws parameter to
"self.is_aws = False"
This way the installation won't think you are under AWS.
After the modification repeat Data Repository / Vertica installation.