Could not fetch URL https://rpc-repo.rackspace.com/os-releases/12.0.8

[Dale Dude]

Trying tag 12.0.8 and repo update fails. Seems only 12.0.5 directory exists at rpc-repo.rackspace.com.

Could not fetch URL https://rpc-repo.rackspace.com/os-releases/12.0.8: 404 Client Error: Not Found for url: https://rpc-repo.rackspace.com/os-releases/12.0.8 - skipping
  Could not find a version that satisfies the requirement wheel==0.29.0 (from versions: )

[Jesse Pretorius (jesse-pretorius)]

This seems like a configuration issue as the rpc-repo is not required for anything. It's simply referenced for pre-built wheels if they happen to be there. We did find some old documentation reference to using this as a source, which we've removed: https://review.openstack.org/293024

[Jesse Pretorius (jesse-pretorius)]

This affects minor upgrades, and seems to be fine after running repo-build before repo-server - but not the other way around.

[Jesse Pretorius (jesse-pretorius)]

Patch in progress for master: https://review.openstack.org/296594

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: liberty
Review: https://review.openstack.org/297037

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/297037
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=3183826b1e5a59d39210ea5e9ccb321a737dca05
Submitter: Jenkins
Branch: liberty

commit 3183826b1e5a59d39210ea5e9ccb321a737dca05
Author: Jesse Pretorius <email address hidden>
Date: Thu Mar 24 11:01:32 2016 +0000

    Ensure that wheel version used matches upper-constraints

    The upper-constraint for the 'wheel' package is 0.26.0, but
    I61795b3afb4804060d494a08975c10adcf52f468 set the wheel version
    OSA uses to a higher version than that.

    This causes an issue where the repo-server install may fail
    because it can't find a version of wheel to install that meets
    the requirements of <0.26.0,==0.29.0

    Change-Id: Iec25d126b3274b5116101e2c55123a960dace6f8
    Related-Bug: 1559619

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/295941
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=49e9400c415220ad41732ae8c8561063131f4165
Submitter: Jenkins
Branch: master

commit 49e9400c415220ad41732ae8c8561063131f4165
Author: Kevin Carter <email address hidden>
Date: Tue Mar 22 11:26:09 2016 -0500

    Remove the repo clone mirror play

    This play is no longer used and is a hold over from the time
    when the OpenStack-Ansible project came from the Rackspace
    Private Cloud product. Being this is not a play used by
    the core project it should be removed.

    This change also resolves an issue/misconseption that using
    the clone play is a better/more stable way to build/deploy
    an OpenStack cloud using OpenStack-Ansible.

    Change-Id: Icc4d3d01ecd0e3eb2de1ad54b9bff1ca1662beb4
    Closes-Bug: #1559619
    Signed-off-by: Kevin Carter <email address hidden>

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/296594
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=3cdac57fc817e8e7bfed7a5fecb38baa66fe9e86
Submitter: Jenkins
Branch: master

commit 3cdac57fc817e8e7bfed7a5fecb38baa66fe9e86
Author: Jesse Pretorius <email address hidden>
Date: Wed Mar 23 16:29:29 2016 +0000

    Remove pip_get_pip_options override from group_vars

    In the group_vars pip_get_pip_options is set with the intention
    of restricting the initial pip install to using the local repo
    server first, then reaching out to a set upstream repo.
    The pip install role then has a fallback which ignores these
    settings and goes to pypi to fetch the versions required.

    While this works, it causes an initial failure to install pip
    when the repo server is not yet available. This is OK considering
    that there isa fallback, but when other pip install options
    need to be used (eg: proxy options, certificate validation
    disabling due to bad proxies) then circumstances are reached
    where both tasks will fail and pip is uninstallable.

    Going back to the original intent, the use of this setting in
    group_vars is a logic flaw. If there's a repo server already,
    then everywhere where it matters the pip_lock_down role would
    have already restricted pip install options to make use of the
    local repo server for the first task in pip_install anyway. In
    other words we're double-doing the lock down unnecessarily.

    This patch results in the following behaviour:

    - The first pip install task will look for the versions specified
      in the local repo if there is one and the pip_lock_down task has
      run on the host in question.
    - If there is no local pip.conf, the first pip install task will
      seek the packages from pypi.
    - If the deployer chooses to set 'pip_get_pip_options' in
      user_variables, then those options will be honoured.

    This patch paves the way for https://review.openstack.org/296114
    to actually be something useful to have merged.

    Closes-Bug: 1559619
    Change-Id: I148e3628a75d81711b969eddee0c452e2ba16664

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 13.0.0 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 13.0.0 release.

[Jesse Pretorius (jesse-pretorius)]

Liberty milestone will be re-added if/when a patch is submitted.