Project

General

Profile

Actions

Bug #3902

closed

Foreman is unable to create instances with openstack Havana

Added by Ohad Levy over 10 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - OpenStack
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Havana requires to select an internal network, until now, in grizzly, it would auto create an interface in every internal network, starting with Havana this is no longer possible.


Related issues 2 (0 open2 closed)

Related to Foreman - Bug #6455: No network to select, and OpenStack error not propagated properlyResolvedTom Caspy07/01/2014Actions
Has duplicate Foreman - Bug #7381: OpenStack Plugin uses network name instead of UUID, causing errorDuplicateWill Newby09/08/2014Actions
Actions #1

Updated by Ohad Levy over 10 years ago

  • Status changed from New to Ready For Testing
Actions #2

Updated by Anonymous over 10 years ago

  • Target version changed from 1.9.3 to 1.9.2
Actions #3

Updated by Anonymous over 10 years ago

  • Target version changed from 1.9.2 to 1.9.1
Actions #4

Updated by Anonymous over 10 years ago

  • Target version changed from 1.9.1 to 1.9.0
Actions #5

Updated by Anonymous about 10 years ago

  • Target version changed from 1.9.0 to 1.8.4
Actions #6

Updated by Anonymous about 10 years ago

  • Target version changed from 1.8.4 to 1.8.3
Actions #7

Updated by Anonymous about 10 years ago

  • Target version changed from 1.8.3 to 1.8.4
Actions #8

Updated by Anonymous about 10 years ago

  • Target version changed from 1.8.4 to 1.8.3
Actions #9

Updated by Anonymous about 10 years ago

  • Target version changed from 1.8.3 to 1.8.2
Actions #10

Updated by Romain Vrignaud about 10 years ago

The patch https://gist.github.com/anonymous/67e5c3f6d3cdd1f444cd works well on Icehouse. Not tested on Havana.

The only minor webui problem is that Network tab in host creation still have "Primary Interface" displayed without anything under.
(maybe same behavior with other compute resources type)

Actions #11

Updated by Anonymous about 10 years ago

  • Target version changed from 1.8.2 to 1.8.1
Actions #12

Updated by Dominic Cleal almost 10 years ago

  • Related to Bug #6455: No network to select, and OpenStack error not propagated properly added
Actions #13

Updated by Anonymous almost 10 years ago

  • Target version changed from 1.8.1 to 1.8.0
Actions #14

Updated by Anonymous almost 10 years ago

  • Target version changed from 1.8.0 to 1.7.5
Actions #15

Updated by Anonymous almost 10 years ago

  • Target version changed from 1.7.5 to 1.7.4
Actions #16

Updated by The Foreman Bot almost 10 years ago

  • Pull request https://github.com/theforeman/foreman/pull/1099 added
Actions #17

Updated by Dominic Cleal almost 10 years ago

  • Has duplicate Bug #7381: OpenStack Plugin uses network name instead of UUID, causing error added
Actions #18

Updated by Anonymous almost 10 years ago

  • Target version changed from 1.7.4 to 1.7.3
Actions #19

Updated by Dominic Cleal over 9 years ago

  • Category changed from Compute resources to Compute resources - OpenStack
Actions #20

Updated by Dominic Cleal over 9 years ago

  • Target version changed from 1.7.3 to 1.7.2
Actions #21

Updated by Ohad Levy over 9 years ago

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

Updated by Dominic Cleal over 9 years ago

  • Translation missing: en.field_release set to 21
Actions

Also available in: Atom PDF