Cannot load bundle details for bigtop-processing-mapreduce bundle

Bug #1572788 reported by Antonio Rosales
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-gui (Juju Charms Collection)
New
Undecided
Unassigned

Bug Description

I am trying to deploy:
https://jujucharms.com/u/bigdata-dev/bigtop-processing-mapreduce/bundle/1

Since quickstart isn't working and deployer isn't in the core product I go to the juju-gui and search for "bigtop processing mapreduce." I find the bundle (see attached), but when I click on it it fails to load with the error message:

"There was a problem while loading the entity details. You could try searching for another charm or bundle or go back."

Also, the quickstart that we direct users to on jujucharms.com fails:
juju quickstart u/bigdata-dev/bigtop-processing-mapreduce/1

arosales@x230:~/tmp$ juju-1 quickstart ./bigtop-bundle.yaml
usage: juju-quickstart [-h] [-e ENV_NAME] [-n BUNDLE_NAME] [-i]
                       [--environments-file ENV_FILE]
                       [--gui-charm-url CHARM_URL] [--no-browser]
                       [--distro-only] [--ppa] [--version] [--debug]
                       [--description] [--upload-tools]
                       [--upload-series UPLOAD_SERIES]
                       [--constraints CONSTRAINTS]
                       [bundle]
juju-quickstart: error: invalid YAML contents: services:
  namenode:
    charm: cs:~bigdata-dev/trusty/apache-bigtop-namenode
    num_units: 1
    annotations:
      gui-x: "600"
      gui-y: "350"
    constraints: mem=7G
  resourcemanager:
    charm: cs:~bigdata-dev/trusty/apache-bigtop-resourcemanager
    num_units: 1
    annotations:
      gui-x: "600"
      gui-y: "100"
    constraints: mem=7G
  slave:
    charm: cs:~bigdata-dev/trusty/apache-bigtop-slave
    num_units: 3
    annotations:
      gui-x: "250"
      gui-y: "225"
    constraints: mem=7G
series: trusty
relations:
  - [resourcemanager, namenode]
  - [namenode, slave]
  - [resourcemanager, slave]

but we know this, however that is what we instruct users to do. It seems the only way to deploy this bundle is via deployer, which we unfortunately don't document :-/

Revision history for this message
Antonio Rosales (arosales) wrote :
Revision history for this message
Antonio Rosales (arosales) wrote :
Revision history for this message
Aditya Mandyam (akm862) wrote :

I am also experiencing this problem, but I am trying to use a different bundle: landscape-dense-maas

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.