You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Ioannis Canellos (JIRA)" <ji...@apache.org> on 2011/09/07 23:59:09 UTC

[jira] [Created] (KARAF-856) Cellar discovery task can erase preconfigure node IPs

Cellar discovery task can erase preconfigure node IPs
-----------------------------------------------------

                 Key: KARAF-856
                 URL: https://issues.apache.org/jira/browse/KARAF-856
             Project: Karaf
          Issue Type: Bug
          Components: cellar-core
    Affects Versions: cellar-2.2.2
            Reporter: Ioannis Canellos
            Assignee: Ioannis Canellos
             Fix For: cave-3.0.0, cellar-2.2.3


With the introduction of discovery services in Cellar a new bug was introduced. The discovery task can overwrite/erase the tcpIpMembers property of the instance.cfg.
This breaks unicast discovery and only multicast and cloud discovery are possible.

There are two things that need to be done:
a) Make sure that no updates to the configuration will happen, if no discovery services are running.
b) Discovery service use a different property to use for storing IPs, than the one used for simple unicast.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (KARAF-856) Cellar discovery task can erase preconfigured node IPs

Posted by "Ioannis Canellos (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ioannis Canellos resolved KARAF-856.
------------------------------------

    Resolution: Fixed

Committed to trunk and branch 2.2.x

> Cellar discovery task can erase preconfigured node IPs
> ------------------------------------------------------
>
>                 Key: KARAF-856
>                 URL: https://issues.apache.org/jira/browse/KARAF-856
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-core
>    Affects Versions: cellar-2.2.2
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>             Fix For: cave-3.0.0, cellar-2.2.3
>
>
> With the introduction of discovery services in Cellar a new bug was introduced. The discovery task can overwrite/erase the tcpIpMembers property of the instance.cfg.
> This breaks unicast discovery and only multicast and cloud discovery are possible.
> There are two things that need to be done:
> a) Make sure that no updates to the configuration will happen, if no discovery services are running.
> b) Discovery service use a different property to use for storing IPs, than the one used for simple unicast.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (KARAF-856) Cellar discovery task can erase preconfigured node IPs

Posted by "Ioannis Canellos (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ioannis Canellos updated KARAF-856:
-----------------------------------

    Summary: Cellar discovery task can erase preconfigured node IPs  (was: Cellar discovery task can erase preconfigure node IPs)

> Cellar discovery task can erase preconfigured node IPs
> ------------------------------------------------------
>
>                 Key: KARAF-856
>                 URL: https://issues.apache.org/jira/browse/KARAF-856
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-core
>    Affects Versions: cellar-2.2.2
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>             Fix For: cave-3.0.0, cellar-2.2.3
>
>
> With the introduction of discovery services in Cellar a new bug was introduced. The discovery task can overwrite/erase the tcpIpMembers property of the instance.cfg.
> This breaks unicast discovery and only multicast and cloud discovery are possible.
> There are two things that need to be done:
> a) Make sure that no updates to the configuration will happen, if no discovery services are running.
> b) Discovery service use a different property to use for storing IPs, than the one used for simple unicast.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira