Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Provisioning stopped working after upgrade to 27.0.4

Description

Blocking problem:

Adding service definitions in Provisioning has no effect on the node. New service is added in Provisioning, but node is not provisioned.

 

History:

A standalone OpenNMS installation monitoring ~100 nodes and ~1.000 services has been upgraded from 26.2.2 to 27.0.4.

Apt packages were used from the OpenNMS repo,  the upgrade didn't show any errors or warnings, /usr/share/opennms/bin/install -dis was executed.

After some hours of running it has been discovered that new services couldn't be added to or removed from existing nodes.

New nodes could be added, also discovery found new nodes.

The proposal in OpenNMS chat of executing 

service opennms stop; yes /usr/share/opennms/bin/fix-karaf-setup.sh; service opennms start

didn't have an influence on the problem.

 

If I can provide any files or additional input, please let me know and I can share. 

Thank you for the support!

Environment

Ubuntu 20.04.2 LTS

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Sven Reissmann February 10, 2021 at 10:10 AM

Fixed for me by upgrading to 27.0.5. Thanks!

Sascha Rommelfangen February 10, 2021 at 5:56 AM

Thank you!

Christian Pape February 9, 2021 at 4:02 PM

Fixed in .

Sven Reissmann February 9, 2021 at 12:24 PM

I'm using  Debian 10.7 and OpenJDK 11.0.9.1 

If you still need it, I can provide you with provisiond.log and web.log (loglevel=DEBUG), but I'd prefer not to share it publicly, as it looks like SNMPv3 passwords get logged into provisiond.log.

Maybe this exception from provisiond.log is of interest?

Chandra Gorantla February 8, 2021 at 9:42 PM

Fixed

Details

Assignee

Reporter

Labels

HB Backlog Status

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created February 6, 2021 at 8:00 PM
Updated June 22, 2021 at 1:15 PM
Resolved February 9, 2021 at 4:02 PM
Configure