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

Http handler on SSH container cannot resolve url artifact specified in profile via proxy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • jboss-fuse-6.2.1
    • Fabric8 v1, Karaf
    • None
    • % %
    • Hide

      1. set http.proxyHost and http.proxyPort in etc/system.properties
      2. bin/start, bin/client
      3. fabric:create
      4. container-create-ssh ... node1
      5. create profile and add bundle e.g.

      profile-edit --bundles http://fusewin.tpb.lab.eng.brq.redhat.com:8081/nexus/content/repositories/fuse-qe-repo/org/jboss/fuse/qa/test/useless-artifact/1.2/useless-artifact-1.2.jar

      6. add profile to remote container

      Show
      1. set http.proxyHost and http.proxyPort in etc/system.properties 2. bin/start, bin/client 3. fabric:create 4. container-create-ssh ... node1 5. create profile and add bundle e.g. profile-edit --bundles http: //fusewin.tpb.lab.eng.brq.redhat.com:8081/nexus/content/repositories/fuse-qe-repo/org/jboss/fuse/qa/test/useless-artifact/1.2/useless-artifact-1.2.jar 6. add profile to remote container

      In 6.2.1 ER3 (032) it was enough to set http.proxyHost and http.proxyPort in etc/system.properties to resolve artifact by http url in fabric profile on remote ssh container.

      profile-create uselessprofile
profile-edit --bundles http://fusewin.tpb.lab.eng.brq.redhat.com:8081/nexus/content/repositories/fuse-qe-repo/org/jboss/fuse/qa/test/useless-artifact/1.2/useless-artifact-1.2.jar uselessprofile
container-add-profile node1 uselessprofile

      In 6.2.1 ER4 (070) Artifact is not resolved and status hangs on "analyzing". When profile is deployed to root artifact is resolved via proxy as expected.

      Looks like fabric maven proxy was capable to use system.properties proxy settings before but not anymore.

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

              Created:
              Updated:
              Resolved: