Closed stevelle closed 9 years ago
this issue is being caused by the branch release version for the repo_package file for ansible-lxc-rpc pointing at a sha instead of itself.
repo_packages/ansible_rpc_lxc.yml
from stable/icehouse file:
https://github.com/rcbops/ansible-lxc-rpc/blob/stable/icehouse/rpc_deployment/vars/repo_packages/ansible_rpc_lxc.yml#L20
This points to the sha "22dd0baba7b1e0f496794ee59c968738df1a257d" that lacks the dependencies required to perform a modern build.
Does this have to be pinned at a SHA, or would pointing to the current branch/tag help?
In all honesty, it could be pointed at a sha it just needs to be a more updated sha. For the branches, I'd recommend that it be pointed at the branch.
As of this morning issues #527 and #499 should no longer be blocked when using rpc.cloudnull.io or mirror.rackspace.com. sadly rpc-slushee is likely still in a bad state due the perpetual CDN problems.
no longer occurs for master. General process issue to be addressed separately.
Gate is reporting an issue with us moving the frozen repo to mirror.rackspace.
see also: http://jenkins.propter.net/job/dev-sat6-gate/317/console
Blocks #527 and #499
Issue doesn't appear to actually be with a lack of https. Checking mirror for the requirements shows some gaps in places, which could be the cause. Ex.
more to be discovered