Skip to:

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

WebUI shows "rescan to suspend" for "forced unmanaged" services

Description

If I uncheck a service on a node's "Manage and Unmanage Interfaces and Services" page, it tells me to rescan the node in order to apply the change:

—
Changes for a specific node will become effective upon execution of a forced rescan on that node (node must not be down when rescanned).
—

The node page then says "rescan to suspend" for the particular service.

Now I rescan the node and wait for the uei.opennms.org/internal/provisiond/nodeScanCompleted event.

Two bugs on this:

1) polling still happens until OpenNMS is restarted.

2) "rescan to suspend" never changes to "forced unmanaged" as it used to.

Tested with 1.8.0-2 x64 on opensuse 11.1

Environment

Operating System: Linux Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Antonio Russo November 14, 2011 at 7:08 AM

Fixed on revision 535a69230f59017e1e664e20936363dfc331bfda 1.8.

Just back ported Alejandro work!

Antonio Russo November 14, 2011 at 3:53 AM

Alejandro have you cherry picked the changes in 1.8?

Alejandro Galue September 23, 2011 at 7:24 PM

Fixed on revision afcfb051e7356cecfe060d46d8bea5c9b9452b91 for 1.10

Now, the behavior for Provisiond when suspending/resuming the polling of services, is exactly the same as it is for Capsd.

Alejandro Galue July 12, 2011 at 1:58 PM

On my tests (with 1.8.13-SNAPSHOT) this only happen with provisioned nodes, or discovered nodes managed by Provisiond (i.e. Capsd is disabled).

Restart OpenNMS fix the problem, but the service status on the WebUI still says "Rescan to Suspend" instead of "Force Unmanaged".

When using Provisiond, I never see this events:
uei.opennms.org/internal/poller/suspendPollingService
uei.opennms.org/internal/poller/resumePollingService

Martin Lorentz March 31, 2011 at 7:01 AM

A rather annoying situation - temporarily unmanaging services with a few simple clicks was nice. For now changing the status manually in the DB does work for me:

update ifservices set status = 'F' where status = 'S' and nodeid = <nodeid>;

After updating the status in the DB, restart OpenNMS.

The use case for unmanaging services is still the same for me, no matter whether I use capsd or provisiond. So here's my vote for this bug.

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created June 11, 2010 at 9:26 AM
Updated January 27, 2017 at 4:26 PM
Resolved September 23, 2011 at 7:24 PM

Flag notifications