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

Changing feature repo version in fabric profile doesn't trigger change in bundles

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • jboss-fuse-6.1
    • jboss-fuse-6.1
    • None
    • None
    • % %
    • Hide

      1) I've created a fabric
      2) Created a profile from FMC
      3) Added a feature repo to the profile (something like mvn:com.rh/myTest/1.0.0/xml/features in my case), and added feature from that repo
      4) Assigned that profile to a child container
      5) Created a new fabric version (fabric:version-create)
      6) checked out that version using git
      7) edited the "repository.mvn" prop (in my case located in "...fabric/profiles/MyProfile.profile/io.fabric8.agent.properties") pointing to a new minor version of the feature repo (so mvn:com.rh/myTest/1.0.1/xml/features)
      8) pushed back to git
      9) fabric:container-upgrade to assign the version i created to all my containers
      10) checked in fmc that the bundles in that repo are not updated

      On the contrary, if in step 7), I switch to a new major version (e.g. 2.0.0), I see in step 10) that everything is changed correctly.

      Show
      1) I've created a fabric 2) Created a profile from FMC 3) Added a feature repo to the profile (something like mvn:com.rh/myTest/1.0.0/xml/features in my case), and added feature from that repo 4) Assigned that profile to a child container 5) Created a new fabric version (fabric:version-create) 6) checked out that version using git 7) edited the "repository.mvn" prop (in my case located in "...fabric/profiles/MyProfile.profile/io.fabric8.agent.properties") pointing to a new minor version of the feature repo (so mvn:com.rh/myTest/1.0.1/xml/features) 8) pushed back to git 9) fabric:container-upgrade to assign the version i created to all my containers 10) checked in fmc that the bundles in that repo are not updated On the contrary, if in step 7), I switch to a new major version (e.g. 2.0.0), I see in step 10) that everything is changed correctly.

    Description

      In a Fabric profile, with an associated feature repo (versioned in maven, so pointing to something like "mvn:com.rh/myTest/1.0.0/xml/features" ), create a new version of the fabric (fabric:version-create), then edit (using git) the path to the maven repo to point to a new minor version (so something like "mvn:com.rh/myTest/1.0.1/xml/features"), and then apply this new version of the fabric to the containers.

      This doesn't trigger the change in the bundles related to that feature repo (or better, looking from FMC, the version is updated, the update location is not).

      Instead, changing to a new major version (so something like "mvn:com.rh/myTest/1.2.0/xml/features"), everything works as expected.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              rhn-support-gbonocor Giuseppe Bonocore (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: