Project

General

Profile

Actions
Copy link

Bug #9281

closed

Compute profile doesn't use selected security group in openstack

Added by Brian Lee almost 10 years ago. Updated almost 10 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Compute resources - OpenStack
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

I created some new security groups in openstack, one starts with a A so it is first in the list. All compute profiles default to that one, even after selecting the default security group. This is caused every VM that is created to have the wrong security group.

Related issues 1 (1 open — 0 closed)

Is duplicate of Foreman - Bug #7350: [Openstack] - security groups are not applied to new hostNew09/04/2014Actions
Actions
Copy link
 #1

Updated by Dominic Cleal almost 10 years ago

  • Is duplicate of Bug #7350: [Openstack] - security groups are not applied to new host added
Actions
Copy link
 #2

Updated by Dominic Cleal almost 10 years ago

  • Status changed from New to Duplicate

Thanks for the report, as discussed in IRC, I think this is a dupe of #7350.

Actions
Copy link

Also available in: Atom PDF