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

Pull failed because of: org.eclipse.jgit.api.errors.InvalidRemoteException: Invalid remote: origin

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate Issue
    • Affects Version/s: jboss-fuse-6.3
    • Fix Version/s: fuse-6.x-GA
    • Component/s: Fabric8 v1
    • Labels:
      None

      Description

      There is a possible spot for errors in a single node Fabric that can lead to failed deployment operations.

      It's tied to the scenario fixed with ENTESB-5807 but a set of logs from 6.3 suggest that there are still flows that can turn into errors.

      In particular:

      2017-03-28 08:26:32,435 | WARN  | onStateManager-0 | DefaultPullPushPolicy            | 84 - io.fabric8.fabric-git - 1.2.0.redhat-630187 | Pull failed because of: org.eclipse.jgit.api.errors.InvalidRemoteException: Invalid remote: origin
      2017-03-28 08:31:30,562 | INFO  | cache-1-thread-1 | ZkDataStoreImpl                  | 82 - io.fabric8.fabric-core - 1.2.0.redhat-630187 | Event CHILD_UPDATED detected on /fabric/configs/containers/x001 with data 1.0.1.1000. Sending notification.
      2017-03-28 08:31:30,563 | INFO  | cache-1-thread-1 | ZkDataStoreImpl                  | 82 - io.fabric8.fabric-core - 1.2.0.redhat-630187 | Event CHILD_ADDED detected on /fabric/configs/versions/1.0.1.1000/containers/x001 with data gateway-mq gateway-http. Sending notification.
      2017-03-28 08:31:30,568 | WARN  | store-2-thread-1 | ZkDataStoreImpl                  | 82 - io.fabric8.fabric-core - 1.2.0.redhat-630187 | Caught: java.lang.NullPointerException
      java.lang.NullPointerException
              at io.fabric8.internal.ContainerImpl.getContainerProfile(ContainerImpl.java:764)[82:io.fabric8.fabric-core:1.2.0.redhat-630187]
              at io.fabric8.internal.ContainerImpl.getOverlayProfile(ContainerImpl.java:306)[82:io.fabric8.fabric-core:1.2.0.redhat-630187]
              at io.fabric8.features.FabricFeaturesServiceImpl.listInstalledRepositories(FabricFeaturesServiceImpl.java:392)[90:io.fabric8.fabric-features-service:1.2.0.redhat-630187]
              at io.fabric8.features.FabricFeaturesServiceImpl.run(FabricFeaturesServiceImpl.java:116)[90:io.fabric8.fabric-features-service:1.2.0.redhat-630187]
              at io.fabric8.service.ZkDataStoreImpl.doRunCallbacks(ZkDataStoreImpl.java:211)[82:io.fabric8.fabric-core:1.2.0.redhat-630187]
              at io.fabric8.service.ZkDataStoreImpl.access$000(ZkDataStoreImpl.java:86)[82:io.fabric8.fabric-core:1.2.0.redhat-630187]
              at io.fabric8.service.ZkDataStoreImpl$1.run(ZkDataStoreImpl.java:199)[82:io.fabric8.fabric-core:1.2.0.redhat-630187]
              at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_101]
              at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_101]
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_101]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_101]
              at java.lang.Thread.run(Thread.java:745)[:1.8.0_101]
      

      shows that ZkDataStoreImpl is still blindly reacting to events even if the container is in an a transitional state, and it should not try to perform certain operation without assuming possible failures.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  grgrzybek Grzegorz Grzybek
                  Reporter:
                  sonicaaaa Paolo Antinori
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: