Ansible Playbook Error (ansbile-setup)

Google Cloud Apigee
1

Playbook :carlosfrias/apigee-opdk-setup-component-installer

Task: Install apigee-setup

No issue running manually → /opt/apigee/apigee-service/bin/apigee-service apigee-setup install

ERROR –

fatal: [localhost]: FAILED! => {
“changed”: true,
“cmd”: “{u’stat’: {u’isuid’: False, u’uid’: 1001, u’exists’: True, u’attr_flags’: u’‘, u’woth’: False, u’isreg’: True, u’device_type’: 0, u’mtime’: 1462257495.0, u’block_size’: 4096, u’inode’: 101052620, u’isgid’: False, u’size’: 4907, u’executable’: True, u’charset’: u’us-ascii’, u’readable’: True, u’version’: u’18446744073355176986’, u’pw_name’: u’apigee’, u’gid’: 1001, u’ischr’: False, u’wusr’: True, u’writeable’: True, u’mimetype’: u’text/x-shellscript’, u’blocks’: 16, u’xoth’: True, u’islnk’: False, u’nlink’: 1, u’issock’: False, u’rgrp’: True, u’gr_name’: u’apigee’, u’path’: u’/opt/apigee/apigee-service/bin/apigee-service’, u’xusr’: True, u’atime’: 1494297475.0369334, u’md5’: u’9988817e4065c55e4b756c5e2fec53b1’, u’isdir’: False, u’ctime’: 1494297473.4714925, u’isblk’: False, u’wgrp’: True, u’checksum’: u’98f0ca5d04d97646e1190821b1b044f193770eb3’, u’dev’: 64768, u’roth’: True, u’isfifo’: False, u’mode’: u’0775’, u’xgrp’: True, u’rusr’: True, u’attributes’: }, u’changed’: False} apigee-setup install”,
“delta”: “0:00:00.019315”,
“end”: “2017-05-09 09:13:52.908049”,
“failed”: true,
“invocation”: {
“module_args”: {
“_raw_params”: “{u’stat’: {u’isuid’: False, u’uid’: 1001, u’exists’: True, u’attr_flags’: u’‘, u’woth’: False, u’isreg’: True, u’device_type’: 0, u’mtime’: 1462257495.0, u’block_size’: 4096, u’inode’: 101052620, u’isgid’: False, u’size’: 4907, u’executable’: True, u’charset’: u’us-ascii’, u’readable’: True, u’version’: u’18446744073355176986’, u’pw_name’: u’apigee’, u’gid’: 1001, u’ischr’: False, u’wusr’: True, u’writeable’: True, u’mimetype’: u’text/x-shellscript’, u’blocks’: 16, u’xoth’: True, u’islnk’: False, u’nlink’: 1, u’issock’: False, u’rgrp’: True, u’gr_name’: u’apigee’, u’path’: u’/opt/apigee/apigee-service/bin/apigee-service’, u’xusr’: True, u’atime’: 1494297475.0369334, u’md5’: u’9988817e4065c55e4b756c5e2fec53b1’, u’isdir’: False, u’ctime’: 1494297473.4714925, u’isblk’: False, u’wgrp’: True, u’checksum’: u’98f0ca5d04d97646e1190821b1b044f193770eb3’, u’dev’: 64768, u’roth’: True, u’isfifo’: False, u’mode’: u’0775’, u’xgrp’: True, u’rusr’: True, u’attributes’: }, u’changed’: False} apigee-setup install”,
“_uses_shell”: true,
“chdir”: null,
“creates”: null,
“executable”: null,
“removes”: null,
“warn”: true
}
},
“rc”: 127,
“start”: “2017-05-09 09:13:52.888734”,
“stderr”: “/bin/sh: {ustat:: command not found”,
“stderr_lines”: [
“/bin/sh: {ustat:: command not found”
],
“stdout”: “”,
“stdout_lines”:
}

2

I have noticed that this error occurs during times when resources become constrained on the control server. I found that you can alleviate the issue by using tags to partition the load on the control server into three runs. This can be accomplished by running the playbook with --tags=os-pre-req; then with --tags=apigee-pre-req; and then finally with --skip-tags=os-pre-req,apigee-pre-req.

1 Like
3

I had a new error now.

After running with --tags=os-pre-req it stops at ansible_bio_version, since cache playbook didn’t ran it isn’t loading variables.

Same with --tags=apigee-pre-req, asks for JAVA_HOME variable set. Running it with cache creates the same error.

4

The cache can take some time to run. I separated it out into its own tag so that you can invoke it as needed without incurring the penalty of having it run during times when you don’t need it. Please use the --tags=cache to get those variables into your cache.

5

So you’re saying
I should run the playbook first with tags=cache, then with os-pre-req and then with apigee-pre-req. After that skip-tags=os-pre-req,apigee-pre-req ?