Provisioner KnowledgeBase

https://docs.google.com/document/d/1LXOYYpbFCAOMQCiWpltEqI3Zr-5OVMI-5LGgK7BqyNA/edit?ts=5d031b12#heading=h.1ui14hyuzs9n

[[TOC]]

Dos and Don'ts

Dos

• Before you begin with provisioning ensure you have had a good review of files that are expected to be changed:
  • /opt/seagate/eos-prvsnr/pillar/components/release.sls
  • /opt/seagate/eos-prvsnr/pillar/components/cluster.sls These files require customization for every node for node and release specific details. Such customization cannot be skipped.

Dont's

Frequently Asked Questions

Known Issues/Workarounds

Issue. Error ModuleNotFoundError: No module named 's3iamcli' while creating iam account

[root@ees-node1 ees-prvsnr]# s3iamcli CreateAccount -n cloud -e [email protected]
Traceback (most recent call last):
  File "/bin/s3iamcli", line 5, in <module>
    from s3iamcli.main import S3IamCli
ModuleNotFoundError: No module named 's3iamcli'

Solution

[root@ees-node1 ees-prvsnr]# ls -l /usr/bin/python3
lrwxrwxrwx. 1 root root 9 Jun 19 00:22 /usr/bin/python3 -> python3.6
[root@ees-node1 ees-prvsnr]# ls -l /usr/bin/python
lrwxrwxrwx. 1 root root 7 Mar 22 02:04 /usr/bin/python -> python2
[root@ees-node1 ees-prvsnr]# ls -l /usr/bin/python*
lrwxrwxrwx. 1 root root     7 Mar 22 02:04 /usr/bin/python -> python2
lrwxrwxrwx. 1 root root     9 Mar 22 02:04 /usr/bin/python2 -> python2.7
-rwxr-xr-x. 1 root root  7216 Apr 11  2018 /usr/bin/python2.7
lrwxrwxrwx. 1 root root     9 Jun 19 00:22 /usr/bin/python3 -> python3.6
-rwxr-xr-x. 2 root root 11384 Apr  7 22:19 /usr/bin/python3.4
-rwxr-xr-x. 2 root root 11384 Apr  7 22:19 /usr/bin/python3.4m
lrwxrwxrwx. 1 root root    18 Jun 19 00:22 /usr/bin/python36 -> /usr/bin/python3.6
-rwxr-xr-x. 2 root root 11408 Apr 25 17:05 /usr/bin/python3.6
-rwxr-xr-x. 2 root root 11408 Apr 25 17:05 /usr/bin/python3.6m  

[root@ees-node1 ees-prvsnr]# rm /usr/bin/python3
rm: remove symbolic link ‘/usr/bin/python3’? y  

[root@ees-node1 ees-prvsnr]# ln -s /usr/bin/python3.4 /usr/bin/python3
[root@ees-node1 ees-prvsnr]# ls -l /usr/bin/python*
lrwxrwxrwx. 1 root root     7 Mar 22 02:04 /usr/bin/python -> python2
lrwxrwxrwx. 1 root root     9 Mar 22 02:04 /usr/bin/python2 -> python2.7
-rwxr-xr-x. 1 root root  7216 Apr 11  2018 /usr/bin/python2.7
lrwxrwxrwx. 1 root root    18 Jun 19 02:26 /usr/bin/python3 -> /usr/bin/python3.4
-rwxr-xr-x. 2 root root 11384 Apr  7 22:19 /usr/bin/python3.4
-rwxr-xr-x. 2 root root 11384 Apr  7 22:19 /usr/bin/python3.4m
lrwxrwxrwx. 1 root root    18 Jun 19 00:22 /usr/bin/python36 -> /usr/bin/python3.6
-rwxr-xr-x. 2 root root 11408 Apr 25 17:05 /usr/bin/python3.6
-rwxr-xr-x. 2 root root 11408 Apr 25 17:05 /usr/bin/python3.6m

Issue. Error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600) while CreateAccount

[root@ees-node1 .sgs3iamcli]# s3iamcli createaccount -n s3user1 -e [email protected]
Enter Ldap User Id: sgiamadmin
Enter Ldap password:
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)

Solution

• Modify file /etc/haproxy/haproxy.cfg

#----------------------------------------------------------------------
# BackEnd roundrobin as balance algorith for s3 auth server
#----------------------------------------------------------------------
backend s3-auth
    balance static-rr                                     #Balance algorithm


    server s3authserver-instance1 0.0.0.0:9086 check ssl verify required ca-file /etc/ssl/stx-s3/s3auth/s3authserver.crt
    # server s3authserver-instance1 0.0.0.0:9085 check  # s3 auth server instance 1
    # server s3authserver-instance2 0.0.0.0:9086 check  # s3 auth server instance 2

• Restart haproxy service

systemctl restart haprxoy

Issue. Vagrant doesn't rsync OR Files on VM not in sync with files on host after vagrant up or vagrant rsync

Solution

The issue lies with VM in Virtualbox not destroying correctly. To resolve this issue:

• Open Virtualbox
• Try to find the concerning VM
• Select VM -> Right click -> Select Remove
  
• Select Delete all files
  
• Select Virtual Media Manager
  
• Delete any suspicious vdi entries or entries with errors
• Close Virtualbox
• Attempt vagrant up again and verify the results.

Issue. s3server is not getting online while Bootstrap.

Solution

• set the "S3_REUSEPORT" parameter to "true" in /opt/seagate/s3/config/s3config.yaml file.