Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-5461

profile-refresh command does not update the content of added features.xml

    XMLWordPrintable

Details

    • % %
    • Hide
      • Install attached maven repository into your local maven repository
      • Start fuse
        Fix $FUSE/bin/setenv
        export EXTRA_JAVA_OPTS="-Djava.rmi.server.hostname=0.0.0.1 -Daether.updateCheckManager.sessionState=bypass"
        
        $FUSE/bin/fuse
        
      • Create a fabric envrionment
        fabric:create --clean --zookeeper-password admin --zookeeper-data-dir zkdata --wait-for-provisioning --resolver localip
        profile-edit --pid io.fabric8.maven/io.fabric8.maven.localRepository='${karaf.data}/repository' default
        
      • Create a child container which uses a featureas.xml with a bunle(mvn:com.redhat/fabricTestDeploy/1.0-SNAPSHOT)
        profile-create --parents default Test
        profile-edit --repositories file:///opt/features.xml Test
        profile-edit --features TestDeploy Test
        profile-edit --features camel-blueprint Test
        container-create-child --profile Test root child
        
      • Check the log from child container
        [1.0-SNAPSHOT]Hello from Fabric based Camel route! : child
        Testing the changes now !!!
        
      • Update the features.xml
        Curernt:
        <bundle>mvn:com.redhat/fabricTestDeploy/1.0-SNAPSHOT</bundle>
        

        Modified:

        <bundle>mvn:com.redhat/fabricTestDeploy/2.0-SNAPSHOT</bundle>
        
        profile-refresh Test
        
      • Check the log from child container
        [1.0-SNAPSHOT]Hello from Fabric based Camel route! : child
        Testing the changes now !!!
        

        Child container still uses the old features.xml.

      • check the feature. It displays latest features.xml
        features:info TestDeploy 
        mvn:com.redhat/fabricTestDeploy/2.0-SNAPSHOT
        

        So user easily gets confused like which features.xml is used by the container

      Workaround:

      container-stop child
      rm instances/child/data/tmp/features.xml
      container-start child
      

      log from child container

      [2.0-SNAPSHOT]Hello from Fabric based Camel route! : child
      Testing the changes now !!!
      
      Show
      Install attached maven repository into your local maven repository Start fuse Fix $FUSE/bin/setenv export EXTRA_JAVA_OPTS="-Djava.rmi.server.hostname=0.0.0.1 -Daether.updateCheckManager.sessionState=bypass" $FUSE/bin/fuse Create a fabric envrionment fabric:create --clean --zookeeper-password admin --zookeeper-data-dir zkdata --wait-for-provisioning --resolver localip profile-edit --pid io.fabric8.maven/io.fabric8.maven.localRepository='${karaf.data}/repository' default Create a child container which uses a featureas.xml with a bunle(mvn:com.redhat/fabricTestDeploy/1.0-SNAPSHOT) profile-create --parents default Test profile-edit --repositories file:///opt/features.xml Test profile-edit --features TestDeploy Test profile-edit --features camel-blueprint Test container-create-child --profile Test root child Check the log from child container [1.0-SNAPSHOT]Hello from Fabric based Camel route! : child Testing the changes now !!! Update the features.xml Curernt: <bundle>mvn:com.redhat/fabricTestDeploy/1.0-SNAPSHOT</bundle> Modified: <bundle>mvn:com.redhat/fabricTestDeploy/2.0-SNAPSHOT</bundle> profile-refresh Test Check the log from child container [1.0-SNAPSHOT]Hello from Fabric based Camel route! : child Testing the changes now !!! Child container still uses the old features.xml. check the feature. It displays latest features.xml features:info TestDeploy mvn:com.redhat/fabricTestDeploy/2.0-SNAPSHOT So user easily gets confused like which features.xml is used by the container Workaround: container-stop child rm instances/child/data/tmp/features.xml container-start child log from child container [2.0-SNAPSHOT]Hello from Fabric based Camel route! : child Testing the changes now !!!
    • Sprint 5 - towards ER2

    Description

      When user updates bundle's info in features.xml, the updated features.xml is not applied with profile-refresh command. unless user specifically delete it from instances/<Node>/ folder.

      Attachments

        1. features.xml
          0.2 kB
        2. mavenRepo.tar.gz
          5 kB

        Issue Links

          Activity

            People

              pantinor@redhat.com Paolo Antinori
              rhn-support-hfuruich Hisao Furuichi
              Roman Jakubco Roman Jakubco (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: