Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1607532

Summary: [IPv6] Incorrect IP parsing for infrautils diagstatus JMX connector CLI diagnostic utility
Product: Red Hat OpenStack Reporter: Janki <jchhatba>
Component: opendaylightAssignee: Stephen Kitt <skitt>
Status: CLOSED WONTFIX QA Contact: Noam Manos <nmanos>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: aadam, jchhatba, joflynn, jschluet, mkolesni, skitt, vorburger
Target Milestone: z5Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: IPv6
Fixed In Version: opendaylight-8.3.0-2.el7ost Doc Type: Bug Fix
Doc Text:
Previously when attempting to retrieve diagnostics, IPv6 addresses were handled as IPv4 addresses. This meant that the diagstatus CLI command was unable to retrieve diagnostics from remote nodes configured using IPv6 addresses. This issue has been resolved and IPv6 addresses are handled correctly.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-06 16:16:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1488821    

Description Janki 2018-07-23 16:30:19 UTC
Description of problem:
2018-07-23T15:47:25,480 | ERROR | SystemReadyService-0 | DiagStatusServiceMBeanImpl       | 272 - org.opendaylight.infrautils.diagstatus-impl - 1.3.3.redhat-1 | unable to start jmx connector for host [fd00

This means IP parsing for remote Diagstatus is IPv4 specific.

Version-Release number of selected component (if applicable):
OSP13 + ODL

How reproducible:
Always when deployed with IPv6.

Steps to Reproduce:
1. Deploy ODL over IPv6 underlay infra.

Actual results:
jmx connector IP is not properly parsed for IPv6 addresses.

Expected results:
jmx connector IP should be properly parsed IPv6 address.

Comment 1 Michael Vorburger 2018-07-23 16:48:41 UTC
(06:12:27  CEST) vorburger: janki: re. "how harmful is this", this error means that the diagstatus CLI command cannot retrieve the remote diagstatus from other nodes, but that /diagstatus URL won't be affected, because that is (intentoinally) only node local.

Comment 7 Joanne O'Flynn 2018-08-14 09:45:47 UTC
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible.

If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-".


To add draft documentation text:

* Select the documentation type from the "Doc Type" drop down field.

* A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.

Comment 11 Janki 2018-08-16 05:56:14 UTC
Noam, As talked over IRC, I will provide you my setup for this. Or you can wait till all v6 related patches are available in rpm and then verify this.

Comment 15 Noam Manos 2018-08-28 12:17:49 UTC
Thanks Janki, issue still occures on seal25:

(undercloud) [stack@undercloud-0 ~]$ ssh heat-admin.24.19 "grep ERROR  /var/log/containers/opendaylight/karaf.*"

2018-08-28T11:17:59,063 | ERROR | Framework Event Dispatcher: org.eclipse.osgi.internal.framework.EquinoxEventPublisher@4c6e276e | core                             | 8 - org.apache.karaf.features.core - 4.1.5 | FrameworkEvent ERROR - org.apache.karaf.features.core
2018-08-28T11:19:02,056 | ERROR | Blueprint Extender: 1 | UpgradeStateListener             | 405 - org.opendaylight.serviceutils.upgrade - 0.1.3.redhat-3 | Failed to write mdsal config
java.util.concurrent.ExecutionException: OptimisticLockFailedException{message=Optimistic lock failed for path /(urn:opendaylight:serviceutils:upgrade?revision=2018-07-02)upgrade-config, errorList=[RpcError [message=Optimistic lock failed for path /(urn:opendaylight:serviceutils:upgrade?revision=2018-07-02)upgrade-config, severity=ERROR, errorType=APPLICATION, tag=resource-denied, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException: Node was replaced by other transaction.]]}
2018-08-28T11:19:10,899 | ERROR | Blueprint Extender: 3 | LearntVpnVipToPortEventProcessor | 361 - org.opendaylight.netvirt.vpnmanager-impl - 0.6.3.redhat-3 | Failed to register the entity arpmonitoring
2018-08-28T11:19:16,445 | ERROR | SystemReadyService-0 | DiagStatusServiceMBeanImpl       | 272 - org.opendaylight.infrautils.diagstatus-impl - 1.3.3.redhat-3 | unable to start jmx connector for host fd00:fd00:fd00:2000::13

Comment 17 Franck Baudin 2019-03-06 16:16:44 UTC
As per depreciation notice [1], closing this bug. Please reopen if relevant for RHOSP13, as this is the only version shipping ODL.

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/html-single/release_notes/index#deprecated_functionality

Comment 18 Franck Baudin 2019-03-06 16:17:49 UTC
As per depreciation notice [1], closing this bug. Please reopen if relevant for RHOSP13, as this is the only version shipping ODL.

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/html-single/release_notes/index#deprecated_functionality