Open marangiop opened 3 years ago
This bug just occurred again, withe the blueprint cycle_12_part2_spain_new
Below you can find the error message of the top two lines of the logs
'create_deployment_environment' workflow execution failed: RuntimeError: Workflow failed: Task failed 'cloudify_agent.operations.install_plugins' -> Failed running pip install. ( Could not find a version that satisfies the requirement wget (from -r plugin-requirements.txt (line 2)) (from versions: ) No matching distribution found for wget (from -r plugin-requirements.txt (line 2)))
Failed running pip install. Output: Processing /tmp/tmp9SqyCy/croupier-permedcoe Requirement already satisfied: cloudify-common==5.1.0.dev1 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 14)) Requirement already satisfied: Jinja2==2.10 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 30)) Requirement already satisfied: MarkupSafe==1.1.1 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 33)) Requirement already satisfied: networkx==1.9.1 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 35)) Requirement already satisfied: paramiko==2.7.2 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 37)) Requirement already satisfied: pika==0.11.2 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 38)) Requirement already satisfied: proxy-tools==0.1.0 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 41)) Requirement already satisfied: PyNaCl==1.4.0 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 48)) Requirement already satisfied: pysnmp==4.4.5 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 50)) Requirement already satisfied: PyYAML==3.10 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 54)) Requirement already satisfied: requests==2.21.0 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 55)) Requirement already satisfied: requests-toolbelt==0.8.0 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 58)) Requirement already satisfied: retrying==1.3.3 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 59)) Requirement already satisfied: six==1.14.0 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 61)) Requirement already satisfied: urllib3==1.23 in /opt/mgmtworker/env/lib/python2.7/site-packages (from -c /tmp/croupier-niWmpi/constraint.txt (line 62)) Collecting wget (from -r plugin-requirements.txt (line 2))
Everything before this line is the same as for a deployment that is correctly created. The line below is when the error comes up. The errors above are a consequence of this error.
Happened again today. Same blueprint, different deployment
Happened again today
This has happened again today, with the blueprint single. Deployment ID is single_08_06 inside Cloudify for GRAPEVINE project
Cloudify Version 20.02.23~community (Community)
Croupier Version Commit 1eb2f325fb0f4385c772c45fe3264c5ebf9d2e07 of branch
grapevine
, after merging frompermedcoe
branch at commit 46239ecccc3fc32a5b1c7cf1b27ed76b45f6ab28Describe the bug As mentioned, this is a relatively rare bug that sometimes comes up after executing a Cloudify CLI command though crontab for creating a Cloudify deployment for a given blueprint. I highlight rare because I perform the same operation every day and this bug almost never comes up.
To Reproduce
cfy
command availableblueprint-single.yaml
(or any other blueprint of choice) inside a remote Cloudify instance at some URLcfy profiles use <Cloudify URL> -t default_tenant -u admin -p <admin_password>
cfy deployments create -b single -i blueprint-single.yaml single
plugin-requirements.txt
) and the deployment will not be created.Expected behavior Deployment creation should take place without problems, even if it's done with a CLI command. This bug could come up again in the future, or maybe never come up. It could have consequences in case where a deployment is not created in the middle of the night and then there is no way to execute the code associated with that deployment until the morning after
Screenshots