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 #11182] IDO: entry_time of all comments is set to the date and time when Icinga 2 was restarted #3949

Closed
icinga-migration opened this issue Feb 18, 2016 · 14 comments
Labels
area/db-ido Database output blocker Blocks a release or needs immediate attention bug Something isn't working
Milestone

Comments

@icinga-migration
Copy link

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

Created by elippmann on 2016-02-18 10:01:24 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2016-06-15 09:30:06 +00:00)
Target Version: 2.5.0
Last Update: 2016-07-25 14:55:31 +00:00 (in Redmine)

Icinga Version: 2.4.1
Backport?: Not yet backported
Include in Changelog: 1

The entry_time of all comments is set to the date and time when Icinga 2 was restarted.

Steps to reproduce:

  • Add a comment
  • Wait some seconds
  • Restart Icinga 2
  • Notice that the entry_time of all comments has been reset

Changesets

2016-06-15 09:28:57 +00:00 by mfriedrich 399ae42

DB IDO: Fix comment/downtime entry_time reset

fixes #11182

Relations:

@icinga-migration
Copy link
Author

Updated by elippmann on 2016-02-18 10:09:27 +00:00

  • Priority changed from High to Normal

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-02-22 18:24:33 +00:00

  • Target Version set to Backlog

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-02-24 19:44:45 +00:00

  • Status changed from New to Assigned
  • Assigned to set to mfriedrich

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-03-18 13:01:58 +00:00

  • Parent Id set to 11412

The entry time is fetched from the created Comment/Downtime object. I guess this is a similar issue with re-creating these object inserts on restart as seen with the other issues on the parent ticket.

@icinga-migration
Copy link
Author

Updated by elippmann on 2016-04-26 07:05:58 +00:00

  • Duplicated set to 11677

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-04-26 08:12:55 +00:00

  • Priority changed from Normal to High

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-05-04 08:53:20 +00:00

  • Duplicated set to 11724

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-06-15 09:15:45 +00:00

object Comment "mbmif.int.netways.de-1450175944-0" ignore_on_error {
    author = "icingaadmin"
    entry_type = 1.000000
    expire_time = 0.000000
    host_name = "mbmif.int.netways.de"
    service_name = "procs"
    text = "fdsfdsfs"
    version = 1450175944.182888
}

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-06-15 09:27:45 +00:00

  • Target Version changed from Backlog to 2.5.0

Same problem for downtimes. Over there the state file does store it once, but the written config object does not.

object Downtime "mbmif.int.netways.de-1465982706-0" ignore_on_error {
    author = "icingaadmin"
    comment = "f-kggdsgdsgdfgd"
    config_owner = ""
    duration = 0.000000
    end_time = 1465986299.000000
    entry_time = 1465982706.599242
    fixed = true
    host_name = "lcp-example"
    scheduled_by = ""
    service_name = "rittal-water-air-in-temp"
    start_time = 1465982699.000000
    triggered_by = ""
    version = 1465982706.599916
}

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-06-15 09:30:06 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset 399ae42.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-07-05 15:10:30 +00:00

  • Duplicated set to 12101

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-07-25 14:55:32 +00:00

  • Parent Id deleted 11412

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-08-19 17:44:06 +00:00

  • Duplicated set to 12489

@icinga-migration
Copy link
Author

Updated by elippmann on 2016-08-25 13:18:43 +00:00

  • Copied To set to 12548

@icinga-migration icinga-migration added blocker Blocks a release or needs immediate attention bug Something isn't working area/db-ido Database output labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.5.0 milestone 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 blocker Blocks a release or needs immediate attention bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant