You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2016/05/04 01:40:12 UTC

[jira] [Created] (BIGTOP-2421) Ignite 1.5.0-final is broken for missing osgi classes.

Konstantin Boudnik created BIGTOP-2421:
------------------------------------------

             Summary: Ignite 1.5.0-final is broken for missing osgi classes.
                 Key: BIGTOP-2421
                 URL: https://issues.apache.org/jira/browse/BIGTOP-2421
             Project: Bigtop
          Issue Type: Bug
          Components: deployment
    Affects Versions: 1.1.0
         Environment: CentOS7 (at the minimum)
            Reporter: Konstantin Boudnik
            Priority: Critical
             Fix For: 1.2.0


During the deployment of ignite_hadoop component, on the first start of the deamon, the following error messages are thrown
{code}
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
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)