Client Error: Not Found for url

Bug #1711341 reported by Syed Armani
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Expired
Undecided
Unassigned

Bug Description

Host OS: Trusty
OSA checkout: 14.2.7 tag

During the Mitaka -> Newton upgrade process as described here[0],
the "openstack-ansible galera-install.yml -e 'galera_upgrade=true'" fails with this[1] error.

[0] https://docs.openstack.org/openstack-ansible/newton/upgrade-guide/manual-upgrade.html
[1] http://paste.openstack.org/show/618659/

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

This bug will require more information to triage properly. Can you please supply more details about the environment - is this an AIO test environment, or something larger? Have you verified via curl or something that http://172.29.236.10:8181/os-releases/14.2.7/ubuntu-14.04-x86_64/requirements_absolute_requirements.txt returns a file with content or not. If not, have you verified that the load balancer is working properly and whether the repo servers have any content to match that query?

Revision history for this message
Syed Armani (dce3062) wrote :

This is a 4 node(VM) test environment where i am testing the upgrade from Mitaka to Newton.

I applied this[0] patch to the 14.2.7 tag and then executed the repo-install.yml playbook, after that i executed the "galera-install.yml" playbook which failed.

Also, curl http://172.29.236.10:8181/os-releases/14.2.7/ubuntu-14.04-x86_64/requirements_absolute_requirements.txt resulted in 404 error messages.

On your suggestion, i executed the repo-build playbook like this:

openstack-ansible repo-build.yml -e repo_build_git_reclone=yes -e repo_build_wheel_rebuild=yes -e repo_build_venv_rebuild=yes

which resulted in rebuilding the repo and the error that i got on running galera-install.yml playbook also disappeared.

[0] https://github.com/openstack/openstack-ansible-repo_build/commit/2d4719fd7de85fbd20ffb8fe7cbb9ac0a49eb014

Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

Maybe your repo failed indeed, for a transient issue on your side.
Due to the incertainty, we can't say if it's a bug or not, and I will mark this as incomplete.

Changed in openstack-ansible:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openstack-ansible because there has been no activity for 60 days.]

Changed in openstack-ansible:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.