| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001310 | PacketFence | core | public | 2011-10-15 02:10 | 2012-10-19 13:34 |
|
| Reporter | psnizek | |
| Assigned To | fgaudreault | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | no change required | |
| Platform | | OS | | OS Version | |
| Product Version | 3.0.1 | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0001310: adding a node before adding a person causes key constraint failed without proper error message in the UI |
| Description | it's correct that adding a node before a person should cause an error. However, the error should be displayed in the WebUI which is not the case. Instead, the WebUI displays 'Added Record' (without dispaying the mac address) which suggests everything's OK. In packetfence.log the below 'key constraint failed' is logged leaving the user guessing what might be wrong.
Despite of what the pf pdf documentation might or might not mention I believe this could be handled much more user friendly. |
| Additional Information | Oct 15 07:51:56 pfcmd(4340) WARN: database query failed with: Cannot add or update a child row: a foreign key constraint fails (`pf`.`node`, CONSTRAINT `0_57` FOREIGN KEY (`pid`) REFERENCES `person` (`pid`) ON DELETE CASCADE ON UPDATE CASCADE). (errno: 1452), will try again (pf::db::db_query_execute)
|
| Tags | No tags attached. |
|
| fixed in git revision | |
| fixed in mtn revision | |
|
| Attached Files | |
|
Relationships 
Notes 