VERSION:
feature_groups:
- mirantis
production: "docker"
release: "6.1"
openstack_version: "2014.2-6.1"
api: "1.0"
build_number: "337"
build_id: "2015-04-21_22-54-31"
nailgun_sha: "3928c5aee6e7aabad37cf0665acc6790ef220141"
python-fuelclient_sha: "08640730176591a3818f24e75b710f8c95846e6e"
astute_sha: "bf1751a4fe0d912325e3b4af629126a59c1b2b51"
fuel-library_sha: "af4eee78a4dd6e6606079f5515bac91c45b04114"
fuel-ostf_sha: "df8db1f48f03b18126ce5ec65317a1eb83a5a95f"
fuelmain_sha: "aad0a7ad97a5660f5d53fa830b168d36fa9694eb"
[root@nailgun ~]# fuel rel --sync-deployment-tasks --dir /etc/puppet/; echo $?
DEPRECATION WARNING: file /etc/fuel/client/config.yaml is found and will be used as a source for settings. However, it deprecated and will not be used by default in the ongoing version of python-fuelclient.
No tasks found for release Juno on Ubuntu 14.04.1 of version 2014.2-6.1
No tasks found for release Juno on CentOS 6.5 of version 2014.2-6.1
0
This issue is fixed on most ISOs, but this is a silent failure and image-based deployment will fail later. We should fail here if there are releases without any tasks with a non-zero exit code.
My concern is that the client should not fail if request to the server passed succesfully and the result was rendered correctly. If lack of tasks means an error on the server side then it the server that should fail, not the client.
Moreover, some people and projects use their own implementations of API clients so "fixing" this issue on the client side won't help them.