Uploaded image for project: 'Bigtop'
  1. Bigtop
  2. BIGTOP-2421

Ignite RPM is broken: "missing" osgi package deps

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.1.0
    • Fix Version/s: 1.2.0
    • Component/s: deployment
    • Labels:
      None
    • Environment:

      CentOS7 (at the minimum)

      Description

      During the deployment of ignite_hadoop component, on the first start of the deamon, the following error messages are thrown

      Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install ignite-hadoop' returned 1: Error: Package: ignite-hadoop-1.5.0.final-1.el7.cen
      tos.noarch (Bigtop)
                 Requires: osgi(org.apache.servicemix.bundles.spring-beans)
      Error: Package: ignite-hadoop-1.5.0.final-1.el7.centos.noarch (Bigtop)
                 Requires: osgi(org.apache.servicemix.bundles.spring-context-support)
      Error: Package: ignite-hadoop-1.5.0.final-1.el7.centos.noarch (Bigtop)
                 Requires: osgi(org.apache.servicemix.bundles.spring-jdbc)
      Error: Package: ignite-hadoop-1.5.0.final-1.el7.centos.noarch (Bigtop)
                 Requires: osgi(org.apache.servicemix.bundles.spring-core)
      Error: Package: ignite-hadoop-1.5.0.final-1.el7.centos.noarch (Bigtop)
                 Requires: osgi(org.apache.servicemix.bundles.spring-tx)
      Error: Package: ignite-hadoop-1.5.0.final-1.el7.centos.noarch (Bigtop)
                 Requires: osgi(org.apache.servicemix.bundles.spring-context)
      Error: Package: ignite-hadoop-1.5.0.final-1.el7.centos.noarch (Bigtop)
                 Requires: osgi(org.apache.servicemix.bundles.spring-expression)
       You could try using --skip-broken to work around the problem
       You could try running: rpm -Va --nofiles --nodigest
      

        Issue Links

          Activity

          Hide
          cos Konstantin Boudnik added a comment -

          This is weird: I am building the component from the sources and I don't see any traces of osgi dependencies that could cause these issues. Given that I am no expert on osgi, I am still not sure why HDFS acceleration (or Spark acceleration) should have any dependencies on the classloading model like that ;(

          Show
          cos Konstantin Boudnik added a comment - This is weird: I am building the component from the sources and I don't see any traces of osgi dependencies that could cause these issues. Given that I am no expert on osgi, I am still not sure why HDFS acceleration (or Spark acceleration) should have any dependencies on the classloading model like that ;(
          Hide
          rvs Roman Shaposhnik added a comment -

          Konstantin Boudnik is this still a problem? Especially in the new Ignite to which we're supposed to bump.

          Show
          rvs Roman Shaposhnik added a comment - Konstantin Boudnik is this still a problem? Especially in the new Ignite to which we're supposed to bump.
          Hide
          cos Konstantin Boudnik added a comment -

          I suspect OSGi issue isn't going anywhere, but I will know more over the weekend, once I have the Ignite 1.9 upgrade ready.

          Show
          cos Konstantin Boudnik added a comment - I suspect OSGi issue isn't going anywhere, but I will know more over the weekend, once I have the Ignite 1.9 upgrade ready.
          Hide
          cos Konstantin Boudnik added a comment -

          Well, as I have suspected, the problem exists with Ignite 1.9 as well. Looks like damn RPM is trying to resolve OSGI java packages as Linux package dependencies. And I have no idea what to do with it ;( Roman Shaposhnik, Olaf Flebbe, Peter Linnell: do you guys have any clue?

          That's what I am getting now:

                  osgi(org.apache.servicemix.bundles.spring-beans) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch
                  osgi(org.apache.servicemix.bundles.spring-context) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch
                  osgi(org.apache.servicemix.bundles.spring-context-support) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch
                  osgi(org.apache.servicemix.bundles.spring-core) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch
                  osgi(org.apache.servicemix.bundles.spring-expression) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch
                  osgi(org.apache.servicemix.bundles.spring-jdbc) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch
                  osgi(org.apache.servicemix.bundles.spring-tx) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch
          
          Show
          cos Konstantin Boudnik added a comment - Well, as I have suspected, the problem exists with Ignite 1.9 as well. Looks like damn RPM is trying to resolve OSGI java packages as Linux package dependencies. And I have no idea what to do with it ;( Roman Shaposhnik , Olaf Flebbe , Peter Linnell : do you guys have any clue? That's what I am getting now: osgi(org.apache.servicemix.bundles.spring-beans) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch osgi(org.apache.servicemix.bundles.spring-context) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch osgi(org.apache.servicemix.bundles.spring-context-support) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch osgi(org.apache.servicemix.bundles.spring-core) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch osgi(org.apache.servicemix.bundles.spring-expression) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch osgi(org.apache.servicemix.bundles.spring-jdbc) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch osgi(org.apache.servicemix.bundles.spring-tx) is needed by ignite-hadoop-1.9.0-1.el7.centos.noarch
          Hide
          cos Konstantin Boudnik added a comment -

          I am going to re-purpose this JIRA to address the general problem, because it isn't related to a particular version of the component.

          Show
          cos Konstantin Boudnik added a comment - I am going to re-purpose this JIRA to address the general problem, because it isn't related to a particular version of the component.
          Hide
          rvs Roman Shaposhnik added a comment -

          Konstantin Boudnik I think you just need to turn off scanning for auto-require/provide: https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering

          Can you try this?

          Show
          rvs Roman Shaposhnik added a comment - Konstantin Boudnik I think you just need to turn off scanning for auto-require/provide: https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering Can you try this?
          Hide
          oflebbe Olaf Flebbe added a comment - - edited

          I agree with Roman Shaposhnik it could be related to https://fedoraproject.org/wiki/Features/OSGiAutoDeps
          According to
          http://ftp.rpm.org/max-rpm/s1-rpm-depend-auto-depend.html
          this can be turned off by AutoReqProv: no or AutoReq: no in the spec file. I am not sure which one.

          But the consequences could be that the whole requirements/provides statements have be given explicitly.

          Show
          oflebbe Olaf Flebbe added a comment - - edited I agree with Roman Shaposhnik it could be related to https://fedoraproject.org/wiki/Features/OSGiAutoDeps According to http://ftp.rpm.org/max-rpm/s1-rpm-depend-auto-depend.html this can be turned off by AutoReqProv: no or AutoReq: no in the spec file. I am not sure which one. But the consequences could be that the whole requirements/provides statements have be given explicitly.
          Hide
          cos Konstantin Boudnik added a comment -

          Ahhhh, why-or-why any one would add a specific case for OSGI? OMG!!!

          Thank you guys for pointing me to the right place - that did the trick. Trivial one-liner is attached

          Show
          cos Konstantin Boudnik added a comment - Ahhhh, why-or-why any one would add a specific case for OSGI? OMG!!! Thank you guys for pointing me to the right place - that did the trick. Trivial one-liner is attached
          Hide
          cos Konstantin Boudnik added a comment -

          Pushed to the master.

          Show
          cos Konstantin Boudnik added a comment - Pushed to the master.

            People

            • Assignee:
              cos Konstantin Boudnik
              Reporter:
              cos Konstantin Boudnik
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development