Project

General

Profile

Actions
Copy link

Bug #32028

closed

[smart_proxy_ansible] Regression in db53b1b: looking for role variables in nonexistent directories

Added by Dominique Quatravaux almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/smart_proxy_ansible/pull/32
Fixed in Releases:
smart_proxy_ansible 3.1.0
Found in Releases:
smart_proxy_ansible 3.0.1
Red Hat JIRA:

Description

What I tried: having

[defaults]
roles_path = roles:$VIRTUAL_ENV/usr/local/share/kubespray/roles:$VIRTUAL_ENV/usr/local/share/ansible/roles:/usr/share/kubespray/roles

in /etc/ansible/ansible.cfg (only the last one of these directories existing), I tried

curl http://smartproxy:8000/ansible/roles/reset/variables

What I expected:

{"reset":{"flush_iptables":true,"reset_restart_network":true}}

What I got instead:

{"reset":{}}
Actions
Copy link
 #1

Updated by The Foreman Bot almost 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/smart_proxy_ansible/pull/32 added
Actions
Copy link
 #2

Updated by The Foreman Bot almost 4 years ago

  • Fixed in Releases smart_proxy_ansible 3.0.1 added
Actions
Copy link
 #3

Updated by Anonymous almost 4 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link
 #4

Updated by Tomer Brisker over 3 years ago

  • Fixed in Releases smart_proxy_ansible 3.1.0 added
  • Fixed in Releases deleted (smart_proxy_ansible 3.0.1)
Actions
Copy link

Also available in: Atom PDF