Project

General

Profile

Actions
Copy link

Bug #11443

closed

ptable template ID changed during upgrade from 1.8.2 -> 1.9, breaks unattended provisioning

Added by salman butt over 8 years ago. Updated about 8 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DB migrations
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
1.9.0
Red Hat JIRA:

Description

I upgraded from version 1.8.2 to 1.9 earlier this morning. No problems were encountered during the upgrade, or the app restart after.

Performing a test provision after the upgrade resulted in this error:

http://pastebin.com/3eFfmn6E

After some digging around, I found that my ptable template ID changed from 12 to 67, somehow. The OS had been created in foreman approximately 3 weeks ago, and the ptable had been associated with it. I had provisioned several VMs under this OS -- most recent was two days ago. No other changes were made to the KS template, or the ptable template.

One odd thing: Attempting to preview the KS template for a host which already existed (existingHost01) rendered the template w/out any problems. When I attempted to preview the KS template for the host I was attempting to provision today (newTestProv01), the template threw an error.

I checked the OS and verified that the ptable was listed as associated, and the checkbox was checked.

Please let me know if I can provide further information.

Related issues 1 (0 open — 1 closed)

Related to Foreman - Feature #7096: Partition Tables should just be a kind of Provisioning TemplatesClosedMarek Hulán08/14/2014Actions
Actions
Copy link

Also available in: Atom PDF