OpenNMS

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

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 1.8.0
  • Fix Version/s: 1.9.92
  • Component/s: Provisioning/Discovery/Capsd/Provisiond
  • Security Level: Default (Default Security Scheme)
  • Labels:
  • Environment:
    Operating System: Linux
    Platform: PC
  • Bugzilla Id:
    3863

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

Issue Links

blocks

Bug - A problem which impairs or prevents the functions of the product. NMS-4696 Let unmanaged interfaces remain unmanaged when reprovisioned

  • Major - Major loss of function.
  • Reopened - This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
is duplicated by

Bug - A problem which impairs or prevents the functions of the product. NMS-4181 provisiond and the "scan to suspend" behavior

  • Blocker - Blocks development and/or testing work, production could not run.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Martin Lorentz added a comment -

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.

Show
Martin Lorentz added a comment - 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.
Hide
Permalink
Alejandro Galue added a comment -

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

Show
Alejandro Galue added a comment - 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
Hide
Permalink
Alejandro Galue added a comment -

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.

Show
Alejandro Galue added a comment - 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.
Hide
Permalink
Antonio Russo added a comment -

Alejandro have you cherry picked the changes in 1.8?

Show
Antonio Russo added a comment - Alejandro have you cherry picked the changes in 1.8?
Hide
Permalink
Antonio Russo added a comment -

Fixed on revision 535a69230f59017e1e664e20936363dfc331bfda 1.8.

Just back ported Alejandro work!

Show
Antonio Russo added a comment - Fixed on revision 535a69230f59017e1e664e20936363dfc331bfda 1.8. Just back ported Alejandro work!

People

  • Assignee:
    Alejandro Galue
    Reporter:
    Dominik Klein
Vote (6)
Watch (5)

Dates

  • Created:
    Updated:
    Resolved: