Bug #2899
closed
Unable to remove the ptable because it is still associated with the host
Description
Ptable created -> Associted with OS
Host created -> Associated with OS (associated with the ptable indirectly)
Ptable removed from the OS, but still remained to be associated with the OS)
Unable to remove the ptable because it is still associated with the OS.
Under the host -> operating system -> Partition table is blank with error (Ptable is not associated with the OS)
Select "unmanage host"
operating system field completely removed, but yet
SELECT "hosts.ptable_id" from "hosts" where name = 'name of host';
returned 11, which is the ptable i created. Had to manually update hosts set ptable_id = NULL where name = 'name of host'; to be able to then remove the ptable.
Version is 1.1stable, yet i am not sure if this is in 1.2.2 or not, couldn't find a bug fix for it in any of the issue lists or it mentioned, but possible it is fixed already and i overlooked.
Updated by Jon Shanks over 11 years ago
Correction
Ptable removed from the OS, but still remained to be associated with the OS)
Should say
Ptable removed from the OS, but still remained to be associated with the host
Updated by Jon Shanks over 11 years ago
Another correction:
Unable to remove the ptable because it is still associated with the OS
should say:
Unable to remove the ptable because it is still associated with the host
(not having a good day)
Updated by Lukas Zapletal over 11 years ago
- Subject changed from Ptable_id not set to NULL after ptable removed from OS to Unable to remove the ptable because it is still associated with the host
- Category set to DB migrations
- Target version set to 1.3.0
Hey, thanks for the report. Typical database consistency issue, it should disappear with our foreign keys effort which is close to be merged.
Updated by Lukas Zapletal over 11 years ago
- Target version deleted (
1.3.0)
I think this is already solved with our foreign keys. Migration might delete those records, beware! Please re-test with 1.3 once it is done and close.
Updated by Dominic Cleal about 11 years ago
- Related to Feature #2400: Add foreign keys on database level added
Updated by Benjamin Papillon almost 11 years ago
- Status changed from Feedback to Closed
Hello,
I'm closing this bug as there is no feedback for few months now and a related ticket has been closed. If you feel this is an error, please reopen or create a new issue.
Regards