Project

General

Profile

Actions

Bug #25069

open

Nested location permissions for subnet access not working correctly

Added by Mike Wilson over 5 years ago. Updated over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Organizations and Locations
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Problem:
When trying to build a host that is a nested location I get the error:
2018-09-27 17:13:47 feac79b5 [app] [I] Current user: admin (administrator)
2018-09-27 17:13:47 feac79b5 [app] [I] Failed to save: Subnet is not defined for host’s location.

Expected outcome:
When trying to SET the nested location (using the web tool) subnet as allowed I see “Parent is already selected” and the value is not saved. The parent IS selected but the problem occurs.

The odd part is we use both ipv4 and ipv6 subnets and the ipv6 subnet DOES let me set the “nested” location as well as the parent location tho the tooltip also said "Parent is already selected".

Foreman and Proxy versions:
Foreman 1.16

I was able to FORCE it to set the value with “hammer cli”

hammer location add-subnet --subnet-id 15 --id 21

Where --id is the location id.

After that the build worked.

Actions #1

Updated by Mike Wilson over 5 years ago

  • Found in Releases 1.16.0 added
Actions

Also available in: Atom PDF