| 2017-07-31 11:25:40 |
Andreas Scheuring |
bug |
|
|
added bug |
| 2017-07-31 11:28:12 |
Andreas Scheuring |
description |
The sync repo task fails with
rsync: mkdir \"/var/www/repo/venvs/15.1.2\" failed: No such file or directory
This bug has been introduced with patch [1]. It intended to fix the locations to which the distribution+arch repo masters synced its packages. This works fine as long as the first host in the repo_masters group is equal to repo_all[0]. In this case, the venv directory gets created on repo_all[0] and follow up repo containers can synchronize to it.
But if this is not the case (e.g. repo_all[0] is on x86 and an s390x repo hosts exists as well, the first container in the repo_masters group wil be the s390x node (due to alphabetical order I guess). In this case we fail.
The solution is to either
- pre-create the directories before executing the rsync or
- to let rsync create the directory structure - this can be achieved with the --relative option
[1] https://github.com/openstack/openstack-ansible-repo_build/commit/e4c5ab4c6ebf33267d4a4cdf7ecff35465899167 |
The sync repo task fails with
rsync: mkdir \"/var/www/repo/venvs/15.1.2\" failed: No such file or directory
This bug has been introduced with patch [1]. It intended to fix the locations to which the distribution+arch repo masters synced its packages. This works fine as long as the first host in the repo_masters group is equal to repo_all[0]. In this case, the venv directory gets created on repo_all[0] and follow up repo containers can synchronize to it.
But if this is not the case (e.g. repo_all[0] is on x86 and an s390x repo hosts exists as well, the first container in the repo_masters group wil be the s390x node (due to alphabetical order I guess). In this case we fail.
The solution is to either
#1 pre-create the directories before executing the rsync or
#2 to let rsync create the directory structure - this can be achieved with the --relative option
If we pick #2 - it might make sense to undo the fix [1] and commit an repoen [2] again
[1] https://github.com/openstack/openstack-ansible-repo_build/commit/e4c5ab4c6ebf33267d4a4cdf7ecff35465899167
[2] https://bugs.launchpad.net/openstack-ansible/+bug/1704936 |
|
| 2017-07-31 11:39:15 |
OpenStack Infra |
openstack-ansible: status |
New |
In Progress |
|
| 2017-07-31 11:39:15 |
OpenStack Infra |
openstack-ansible: assignee |
|
Andreas Scheuring (andreas-scheuring) |
|
| 2017-08-11 08:45:09 |
OpenStack Infra |
openstack-ansible: assignee |
Andreas Scheuring (andreas-scheuring) |
Markus Zoeller (markus_z) (mzoeller) |
|
| 2017-08-11 08:47:43 |
Markus Zoeller (markus_z) |
tags |
|
ocata-backport-potential |
|
| 2017-08-11 09:35:40 |
OpenStack Infra |
openstack-ansible: status |
In Progress |
Fix Released |
|
| 2017-08-11 10:49:15 |
OpenStack Infra |
tags |
ocata-backport-potential |
in-stable-newton ocata-backport-potential |
|
| 2017-08-11 11:01:31 |
OpenStack Infra |
tags |
in-stable-newton ocata-backport-potential |
in-stable-newton in-stable-ocata ocata-backport-potential |
|
