Bug #2701
ACLs for Hosts based on clusters don't work
Status: | Closed | Start date: | 01/30/2014 | |
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Core & System | |||
Target version: | - | |||
Resolution: | duplicate | Pull request: | ||
Affected Versions: | OpenNebula 4.4 |
Description
ACLs for Hosts grouped by Clusters ('Assigned to cluster' in Sunstone) don't work. The following configuration
... 81 @100 -H-------- %112 -m-- 82 @101 -H-------- %112 -m-- 83 @101 -H-------- %104 -m-- 84 @102 -H-------- %104 -m-- 85 @104 -H-------- %104 -m-- 86 @104 -H-------- %112 -m-- 87 @104 -H-------- %113 -m-- 88 @105 -H-------- %104 -m-- 89 @106 -H-------- %104 -m-- 90 @106 -H-------- %112 -m-- 91 @107 -H-------- %112 -m-- 92 @107 -H-------- %104 -m-- ...
will produce a bunch of
... [SCHED][D]: VM 4421: Host 38 filtered out. User is not authorized to MANAGE it. ...
messages for all hosts. Even though the owner of VM 4421 is in (at least) one group allowed on that cluster. In most cases, the owner is in multiple groups and some of them (more than one) have access to that cluster. ACLs shown above are the only ACLs in which Hosts are mentioned, so there is no conflict.
History
#1 Updated by Boris Parak over 7 years ago
Any news? Is this a bug or just a mistake in configuration? Feedback will be greatly appreciated.
#2 Updated by Carlos MartÃn over 7 years ago
- Status changed from Pending to Closed
- Resolution set to duplicate
Hi,
I'm sorry, we missed this ticket... Actually we found the same problem, see #2725. It was solved for the 4.4.1 release
Regards