Project

General

Profile

Actions

Bug #24038

closed

Reversed group inheritance

Added by Laurent Nominé over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Fixed in Releases:
Found in Releases:

Description

Description of problem:
It looks like assigning a role to a host doesn't affect the host itself but the hostgroup it belongs to.

For example, say we have two hosts Host1 and Host2 inside a hostgroup Hostgroup1. In normal conditions, assigning a role to Hostgroup1 is the only way to affect both hosts in one operation. However, I figured out that a direct role assignment to Host2 writes the information to Hostgroup1 instead.

Version-Release number of selected component (if applicable):
2.2.0 and lower versions

Steps to Reproduce:
1. Create a hostgroup
2. Assign an Ansible role to it
3. Place a host inside this hostgroup
4. Assign another Ansible role to the host

Actual results:
Two roles are assigned to the hostgroup

Expected results:
One role assigned to the hostgroup and another role assigned to the host.

Actions #1

Updated by Marek Hulán over 6 years ago

  • Priority changed from High to Normal
  • Translation missing: en.field_release deleted (367)
  • Triaged set to No

Thanks for the detailed report, I was able to reproduce and good news is, roles are not really assigned to the hostgroup, the form only displays it wrongly. The more serious problem would happen if used submitted the form. Then the assignment would become real. Sending a fix, if you're interested in testing, apply the patch from https://github.com/theforeman/foreman_ansible/pull/182, restart your Foreman and see if all works as expected.

The issue was introduced in foreman_ansible 2.1.0 and I expect the fix to land in 2.2.2

Actions #2

Updated by Marek Hulán over 6 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Marek Hulán
  • Pull request https://github.com/theforeman/foreman_ansible/pull/182 added
Actions #3

Updated by Marek Hulán over 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #4

Updated by Marek Hulán over 6 years ago

  • Target version set to foreman-ansible 2.2.4
  • Fixed in Releases foreman-ansible 2.2.4 added
Actions #5

Updated by Marek Hulán over 6 years ago

  • Status changed from Closed to New
  • Target version deleted (foreman-ansible 2.2.4)
  • Difficulty deleted (easy)
  • Bugzilla link set to 1607394

sadly this has been fixed just partly, host form still lists other hosts's run list if they are in the same hostgroup

Actions #6

Updated by The Foreman Bot over 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_ansible/pull/191 added
Actions #7

Updated by Marek Hulán over 6 years ago

  • Status changed from Ready For Testing to Closed
  • Target version set to foreman-ansible 2.2.5
  • Fixed in Releases foreman-ansible 2.2.5 added
  • Fixed in Releases deleted (foreman-ansible 2.2.4)
Actions

Also available in: Atom PDF