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

Broken artifact resolution while using HTTP proxy and remote repository defined in settings.xml

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • jboss-fuse-6.3
    • jboss-fuse-6.2.1, jboss-fuse-6.3
    • Fabric8 v1
    • None
    • % %
    • Hide

      1. create 1 machine for root container and 1 for proxy server (squid)
      2. set up squid proxy server on second machine
      3. extract fuse, uncomment admin user in etc/users.properties, bin/start, fabric:create
      4. 

      profile-edit --pid io.fabric8.agent/org.ops4j.pax.url.mvn.settings='file:/home/fuse/http-proxy-settings.xml' default
profile-edit --pid io.fabric8.agent/org.ops4j.pax.url.mvn.repositories='+http://fusewin.tpb.lab.eng.brq.redhat.com:8081/nexus/content/repositories/fuse-qe-snapshots@snapshots' default

      5. 

      profile-create uselessprofile
profile-edit --bundle mvn:org.jboss.fuse.qa.test/useless-artifact/1.0-SNAPSHOT uselessprofile
profile-edit --bundle mvn:org.jboss.fuse.qa.test/useless-artifact/1.0 uselessprofile
container-add-profile root uselessprofile

      6. restart fuse
      7. artifacts should resolve during restart
      8. 

      profile-edit --bundle mvn:org.jboss.fuse.qa.test/useless-artifact/1.1-SNAPSHOT uselessprofile
profile-edit --bundle mvn:org.jboss.fuse.qa.test/useless-artifact/1.1 uselessprofile
profile-refresh uselessprofile

      9. resolution status wont change and is still success
      10. check local maven repository for artifacts. you will find out artifacts weren't resolved.

      Show
      1. create 1 machine for root container and 1 for proxy server (squid) 2. set up squid proxy server on second machine 3. extract fuse, uncomment admin user in etc/users.properties, bin/start, fabric:create 4. profile-edit --pid io.fabric8.agent/org.ops4j.pax.url.mvn.settings= 'file:/home/fuse/http-proxy-settings.xml' default profile-edit --pid io.fabric8.agent/org.ops4j.pax.url.mvn.repositories= '+http: //fusewin.tpb.lab.eng.brq.redhat.com:8081/nexus/content/repositories/fuse-qe-snapshots@snapshots' default 5. profile-create uselessprofile profile-edit --bundle mvn:org.jboss.fuse.qa.test/useless-artifact/1.0-SNAPSHOT uselessprofile profile-edit --bundle mvn:org.jboss.fuse.qa.test/useless-artifact/1.0 uselessprofile container-add-profile root uselessprofile 6. restart fuse 7. artifacts should resolve during restart 8. profile-edit --bundle mvn:org.jboss.fuse.qa.test/useless-artifact/1.1-SNAPSHOT uselessprofile profile-edit --bundle mvn:org.jboss.fuse.qa.test/useless-artifact/1.1 uselessprofile profile-refresh uselessprofile 9. resolution status wont change and is still success 10. check local maven repository for artifacts. you will find out artifacts weren't resolved.
    • Sprint 5 - towards ER2

      Artifact resolution is not triggered while using HTTP proxy and remote maven repository specified in external settings.xml file. I can see the same behaviour for HTTP proxy specified in settings.xml and remote repository specified in fabric agent PID. When configuration is set and you deploy profile with artifact located in remote repository fabric should trigger artifact resolution chain. With this configuration provisioning status remains "success" without any log. When you shut down and start fuse required artifacts are resoloved via http proxy without problem. However any following update of profile with bundle from remote repositories is not served until restart. Without http proxy specified in settings.xml resolution works as expected. Behaviour looks same for release or snapshot repository.

        1. settings.xml
          1 kB

            pantinor@redhat.com Paolo Antinori
            ecervena@redhat.com Emil Cervenan
            Emil Cervenan Emil Cervenan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: