tripleo-ansible-inventory returns localhost as undercloud IP

Bug #1679979 reported by Maroš Zaťko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

Description
===========
tripleo-ansible-inventory returns localhost as undercloud address, so it resolves to localhost even when ansible task is running on other machine than localhost

Steps to reproduce
==================
* in playbook access groups.undercloud
* watch it resolve to localhost

Expected result
===============
It should resolve to correct address

Actual result
=============
groups.undercloud is always localhost

Tags: validations
Maroš Zaťko (mzatko)
Changed in tripleo:
assignee: nobody → Maroš Zaťko (mzatko)
status: New → In Progress
Changed in tripleo:
importance: Undecided → Medium
milestone: none → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Revision history for this message
Alex Schultz (alex-schultz) wrote :

Moving backed to triaged as there hasn't been any update (or patches) posted that I could find.

Changed in tripleo:
status: In Progress → Triaged
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
assignee: Maroš Zaťko (mzatko) → nobody
importance: Medium → Undecided
status: Triaged → 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.