Project

General

Profile

Actions

Bug #2718

closed

Subnet doesn't appear when domain and subnet is assigned to a specific location

Added by Alejandro Falcon almost 11 years ago. Updated over 10 years ago.

Status:
Rejected
Priority:
High
Assignee:
-
Category:
Organizations and Locations
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Steps: I create a new location, new subnet and new domain, then assign subnet and domain to the newly created location. When I create a new host the subnet doesn't appear under that location and domain.

When I assign the subnet and domain to all locations it works fine.

Actions #1

Updated by Alejandro Falcon almost 11 years ago

This might be related to http://projects.theforeman.org/issues/2203 fix

Actions #2

Updated by Alejandro Falcon almost 11 years ago

Forgot to say I'm using 1.2 RC3

Actions #3

Updated by Ohad Levy almost 11 years ago

can you confirm that the domain is selected as part of the subnet?

Actions #4

Updated by Alejandro Falcon almost 11 years ago

yes I have the domain selected for the subnet. It's weird because I have 3 locations/domains/subnets, that were all working fine before upgrading to 1.2 RC. Yesterday I was going to build one server and 2 of these locations had these issues but one of them didn't, so I tried to create a new one without luck.

I'm using Foreman with MySQL, upgraded from RPM packages.

Actions #5

Updated by Anonymous over 10 years ago

  • Description updated (diff)
  • Assignee set to Anonymous
Actions #6

Updated by Dominic Cleal over 10 years ago

  • Category set to Organizations and Locations
  • Status changed from New to Assigned

I wonder if this is the same as #2734, worth double checking that it's still reproducible. We fixed this later in 1.2.1.

Actions #7

Updated by Anonymous over 10 years ago

Can't reproduce the issue as described with code from master; Will check the same with the latest release.

Actions #8

Updated by Anonymous over 10 years ago

can't reproduce the issue with Foreman 1.2.1 (on Fedora 18).

Actions #9

Updated by Anonymous over 10 years ago

  • Status changed from Assigned to Rejected
Actions

Also available in: Atom PDF