Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #9397] mysql ido: invalid notification_id in the contactnotifications table #3058

Closed
icinga-migration opened this issue Jun 10, 2015 · 5 comments
Labels
area/db-ido Database output bug Something isn't working

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/9397

Created by jmeyer on 2015-06-10 09:03:16 +00:00

Assignee: (none)
Status: Rejected (closed on 2015-12-15 10:51:44 +00:00)
Target Version: (none)
Last Update: 2015-12-15 10:51:44 +00:00 (in Redmine)

Icinga Version: v2.3.0-235-gbdb1838
Backport?: Not yet backported
Include in Changelog: 1

I've issued a custom notification:

select notification_id, start_time from icinga_notifications;
+----------------------+---------------------+
| notification_id     | start_time          |
+----------------------+---------------------+
|                  338    | 2015-06-10 08:16:25 |
+----------------------+---------------------+

And there were two notifications sent out for two contacts:

select * from icinga_contactnotifications;
+------------------------+-------------+-----------------+-------------------+---------------------+-----------------+---------------------+---------------+--------------------+
| contactnotification_id | instance_id | notification_id | contact_object_id | start_time          | start_time_usec | end_time            | end_time_usec | endpoint_object_id |
+------------------------+-------------+-----------------+-------------------+---------------------+-----------------+---------------------+---------------+--------------------+
|                    343 |           1 |               0 |               576 | 2015-06-10 08:16:25 |          708928 | 2015-06-10 08:16:25 |        708928 |               NULL |
|                    344 |           1 |               0 |               481 | 2015-06-10 08:16:25 |          708928 | 2015-06-10 08:16:25 |        708928 |               NULL |
+------------------------+-------------+-----------------+-------------------+---------------------+-----------------+---------------------+---------------+--------------------+

Note that the notification_id is 0, instead of 338.

v2.3.4 stable is showing a different behaviour:
This seems to differ sometimes, by no obvious reason, as the inserted id was id-1 (338 instead of 339), though, I was not able to reproduce it more than once. Continued tests showed correct id behaviour.

This might be related to #8976.


Relations:

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-06-10 10:24:51 +00:00

The reason I was asking for stable tests - I suspect the mysql multi statement change in #8738 causing trouble.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-06-10 10:25:04 +00:00

  • Relates set to 8738

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-06-23 13:30:51 +00:00

  • Target Version set to Backlog

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-06-23 13:31:40 +00:00

  • Relates set to 8976

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-12-15 10:51:45 +00:00

  • Status changed from New to Rejected
  • Target Version deleted Backlog

This is a similar issue as reported in #8976, I'm therefore closing this as duplicate.

@icinga-migration icinga-migration added bug Something isn't working area/db-ido Database output labels Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/db-ido Database output bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant