Project

General

Profile

Bug #436

Migration should not fail if domain name is not set

Added by Ohad Levy about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
DB migrations
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

while it implies something else is wrong (if the foreman host does not have a domain name set), we should not fail the migration because of it.
many people use a simple non configured vm to try out foreman...

Associated revisions

Revision 9e6e5884 (diff)
Added by Ohad Levy about 8 years ago

Fixes #436 - Migration should not fail if domain name is not set

History

#1 Updated by Ohad Levy about 8 years ago

  • Status changed from New to Ready For Testing
  • % Done changed from 0 to 100

#2 Updated by Ohad Levy about 8 years ago

  • Category set to DB migrations
  • Status changed from Ready For Testing to Closed
  • Assignee set to Ohad Levy

Also available in: Atom PDF