[Sahara][Mapr] Cannot login to Mapr HUE dashboard

[Evgeny Sikachev]

ENVIRONMENT: MOS 9.0 ISO 135
shotgun2: http://paste.openstack.org/show/492858/

TEMPLATE:
  - plugin_name: mapr
    plugin_version: 5.1.0.mrv2
    node_group_templates:
      - name: master
        flavor:
          vcpus: 4
          ram: 8192
          root_disk: 80
          ephemeral_disk: 40
        node_processes:
          - Metrics
          - Webserver
          - ZooKeeper
          - HTTPFS
          - Oozie
          - FileServer
          - CLDB
          - Flume
          - Hue
          - NodeManager
          - HistoryServer
          - ResourceManager
          - HiveServer2
          - HiveMetastore
          - Sqoop2-Client
          - Sqoop2-Server
        auto_security_group: true
      - name: worker
        flavor:
          vcpus: 2
          ram: 4096
          root_disk: 40
          ephemeral_disk: 40
        node_processes:
          - NodeManager
          - FileServer
        auto_security_group: true
    cluster_template:
      name: mapr510mrv2
      node_group_templates:
        master: 1
        worker: 1

STEPS TO REPRODUCE:
1. Deploy env with sahara
2. Download image for Mapr http://sahara-files.mirantis.com/images/upstream/mitaka/sahara-mitaka-mapr-5.1.0-ubuntu.qcow2
3. Register image in Sahara
4. Create cluster from TEMPLATE
5. Wait for cluster creation
6. Click on cluster
7. Click on HUE weblink
8. Try default credentials(admin, admin)

EXPECTED RESULT:
Login is correct

ACTUAL RESULT:
Cannot login to HUE

I think we need add credentials for login on page with cluster info, like Ambari/CDH plugin

Upstream-bug: https://bugs.launchpad.net/sahara/+bug/1566907

[Dina Belova (dbelova)]

Adding 9.0 milestone back due to the wait-for-stable tag -> fix will arrive as a part of sync with stable/mitaka code.

[Vitalii Gridnev (vgridnev)]

We did some research about this problem, and seems that it's not so critical to be included in stable/mitaka. Fix will not be consumed from stable/mitaka.

[Dina Belova (dbelova)]

Added move-to-10.0 tag due to the fact bug was transferred from 9.0 to 10.0

[Dina Belova (dbelova)]

This is going to arrive as a part of Newton release