Deploying Windows AD Murano application goes to Failure

[Sergii Turivnyi]

ISO:
{"build_id": "2015-08-18_03-05-20", "build_number": "187", "release_versions": {"2015.1.0-7.0": {"VERSION": {"build_id": "2015-08-18_03-05-20", "build_number": "187", "api": "1.0", "fuel-library_sha": "0062e69db17f8a63f85996039bdefa87aea498e1", "nailgun_sha": "4710801a2f4a6d61d652f8f1e64215d9dde37d2e", "feature_groups": ["mirantis"], "fuel-nailgun-agent_sha": "e01693992d7a0304d926b922b43f3b747c35964c", "openstack_version": "2015.1.0-7.0", "fuel-agent_sha": "57145b1d8804389304cd04322ba0fb3dc9d30327", "production": "docker", "python-fuelclient_sha": "4c74a60aa60c06c136d9197c7d09fa4f8c8e2863", "astute_sha": "e24ca066bf6160bc1e419aaa5d486cad1aaa937d", "fuel-ostf_sha": "17786b86b78e5b66d2b1c15500186648df10c63d", "release": "7.0", "fuelmain_sha": "c9dad194e82a60bf33060eae635fff867116a9ce"}}}, "auth_required": true, "api": "1.0", "fuel-library_sha": "0062e69db17f8a63f85996039bdefa87aea498e1", "nailgun_sha": "4710801a2f4a6d61d652f8f1e64215d9dde37d2e", "feature_groups": ["mirantis"], "fuel-nailgun-agent_sha": "e01693992d7a0304d926b922b43f3b747c35964c", "openstack_version": "2015.1.0-7.0", "fuel-agent_sha": "57145b1d8804389304cd04322ba0fb3dc9d30327", "production": "docker", "python-fuelclient_sha": "4c74a60aa60c06c136d9197c7d09fa4f8c8e2863", "astute_sha": "e24ca066bf6160bc1e419aaa5d486cad1aaa937d", "fuel-ostf_sha": "17786b86b78e5b66d2b1c15500186648df10c63d", "release": "7.0", "fuelmain_sha": "c9dad194e82a60bf33060eae635fff867116a9ce"}

Steps to reproduce:
Configure Active Directory application
    Domain Name my.donain
    Instance Count 2
    Account Name Administrator
    Enter valid passwords

    Instance flavor Medium
Deploy application

Expected result:
After deployment status of application is Active.
Number of instances equal 2

Actual result:
 Deploy FAILURE. Number of instances is 1. Instance is active.

2015-08-25 16:24:40 — Action deploy is scheduled
2015-08-25 16:25:19 — Starting Active Directory deployment
2015-08-25 16:25:19 — Creating VM for Primary Controller for my.domain domain
2015-08-25 16:26:07 — Setting up password
2015-08-25 16:26:13 — Configuring Primary Controller
2015-08-25 16:57:25 — Defining DNS listener IP
2015-08-25 16:57:45 — Creating VM for Secondary Controller
2015-08-25 16:57:45 — DNS listener IP is 10.0.9.4
2015-08-25 16:58:10 — [heatclient.exc.HTTPUnauthorized]: ERROR: Authentication failed. Please try again with option --include-password or export HEAT_INCLUDE_PASSWORD=1 Authentication required
2015-08-25 16:58:10 — Deployment finished with errors

[Ekaterina Chernova (efedorova)]

Please, attach engine logs

looks like token expiration, are you able to reproduce it?

[Sergii Turivnyi (sturivnyi)]

Yep,I can reproduce it in 100% cases.
Logs in attachment.

On Wed, Aug 26, 2015 at 6:25 PM, Ekaterina Chernova <email address hidden>
wrote:

> Please, attach engine logs
>
> looks like token expiration, are you able to reproduce it?
>
> ** Changed in: mos/8.0
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1488853
>
> Title:
> Deployting Windows AD Murano application goes to Failure
>
> Status in Mirantis OpenStack:
> New
> Status in Mirantis OpenStack 7.0.x series:
> Won't Fix
> Status in Mirantis OpenStack 8.0 series:
> Incomplete
>
> Bug description:
> ISO:
> {"build_id": "2015-08-18_03-05-20", "build_number": "187",
> "release_versions": {"2015.1.0-7.0": {"VERSION": {"build_id":
> "2015-08-18_03-05-20", "build_number": "187", "api": "1.0",
> "fuel-library_sha": "0062e69db17f8a63f85996039bdefa87aea498e1",
> "nailgun_sha": "4710801a2f4a6d61d652f8f1e64215d9dde37d2e",
> "feature_groups": ["mirantis"], "fuel-nailgun-agent_sha":
> "e01693992d7a0304d926b922b43f3b747c35964c", "openstack_version":
> "2015.1.0-7.0", "fuel-agent_sha":
> "57145b1d8804389304cd04322ba0fb3dc9d30327", "production": "docker",
> "python-fuelclient_sha": "4c74a60aa60c06c136d9197c7d09fa4f8c8e2863",
> "astute_sha": "e24ca066bf6160bc1e419aaa5d486cad1aaa937d", "fuel-ostf_sha":
> "17786b86b78e5b66d2b1c15500186648df10c63d", "release": "7.0",
> "fuelmain_sha": "c9dad194e82a60bf33060eae635fff867116a9ce"}}},
> "auth_required": true, "api": "1.0", "fuel-library_sha":
> "0062e69db17f8a63f85996039bdefa87aea498e1", "nailgun_sha":
> "4710801a2f4a6d61d652f8f1e64215d9dde37d2e", "feature_groups": ["mirantis"],
> "fuel-nailgun-agent_sha": "e01693992d7a0304d926b922b43f3b747c35964c",
> "openstack_version": "2015.1.0-7.0", "fuel-agent_sha":
> "57145b1d8804389304cd04322ba0fb3dc9d30327", "production": "docker",
> "python-fuelclient_sha": "4c74a60aa60c06c136d9197c7d09fa4f8c8e2863",
> "astute_sha": "e24ca066bf6160bc1e419aaa5d486cad1aaa937d", "fuel-ostf_sha":
> "17786b86b78e5b66d2b1c15500186648df10c63d", "release": "7.0",
> "fuelmain_sha": "c9dad194e82a60bf33060eae635fff867116a9ce"}
>
> Steps to reproduce:
> Configure Active Directory application
> Domain Name my.donain
> Instance Count 2
> Account Name Administrator
> Enter valid passwords
>
> Instance flavor Medium
> Deploy application
>
> Expected result:
> After deployment status of application is Active.
> Number of instances equal 2
>
> Actual result:
> Deploy FAILURE. Number of instances is 1. Instance is active.
>
> 2015-08-25 16:24:40 — Action deploy is scheduled
> 2015-08-25 16:25:19 — Starting Active Directory deployment
> 2015-08-25 16:25:19 — Creating VM for Primary Controller for my.domain
> domain
> 2015-08-25 16:26:07 — Setting up password
> 2015-08-25 16:26:13 — Configuring Primary Controller
> 2015-08-25 16:57:25 — Defining DNS listener IP
> 2015-08-25 16:57:45 — Creating VM for Secondary Controller
> 2015-08-25 16:57:45 — DNS listener IP is 10.0.9.4
> 2015-08-25 16:58:10 — [heatclient.exc.HTTPUnauthorized]: ERROR:
> Authentication fai...

[Sergii Turivnyi (sturivnyi)]

Yep,I can reproduce it in 100% cases.
Logs in attachment.

[Sergii Turivnyi (sturivnyi)]

New exception:
2015-08-27 16:22:47 — Action deploy is scheduled
2015-08-27 16:22:53 — Starting Active Directory deployment
2015-08-27 16:22:53 — Creating VM for Primary Controller for my.domain domain
2015-08-27 16:36:39 — Configuring Primary Controller
2015-08-27 16:36:39 — Setting up password
2015-08-27 16:51:37 — Defining DNS listener IP
2015-08-27 16:51:41 — DNS listener IP is 10.0.10.4
2015-08-27 16:51:41 — Creating VM for Secondary Controller
2015-08-27 16:58:02 — Setting up password
2015-08-27 16:58:03 — Joining host to my.domain domain
2015-08-27 17:05:14 — [murano.engine.system.agent.AgentException]: {'source': 'command', 'command': u'Join-Domain', 'details': {u'PositionMessage': u'At line:46 char:8\r\n+ Add-Computer -DomainName $DomainName -Credential $Credential -Force\r\n+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~', u'ScriptStackTrace': u'at Join-Domain<Process>, <No file>: line 46'}, 'timestamp': '2015-08-27T17:05:13.604627', 'message': u"Computer 'murano-2' failed to join domain 'my.domain' from its current workgroup 'WORKGROUP' with following error message: The user name or password is incorrect.", 'type': u'System.InvalidOperationException'}
2015-08-27 17:05:14 — Deployment finished with errors

[Roman Podoliaka (rpodolyaka)]

Murano team, could you please take a look at Sergii's comments above?

[Alexey Khivin (akhivin)]

upstream bug has been fixed
https://bugs.launchpad.net/murano-apps/+bug/1498821

[Alexey Khivin (akhivin)]

Set to invalid because the fix is not touched MOS code itself.
Only AD application code was changed. Applications is not the part of MOS distribution