OSTF 'Check that user can deploy WordPress app in Murano environment' fails

[Maksym Livshyn]

OSTF test 'Check that user can deploy WordPress app in Murano environment' fails on step #7 (Checking environment status). please look at the stack trace attached.

Name of the ostf test:
fuel_health.tests.tests_platform.test_murano_linux.MuranoDeployLinuxServicesTests.test_deploy_wordpress_app

Also, tried to reproduce this issue manually using the steps from ostf tests, and deployment also failed with the next error:

Steps to reproduce:

1. Create in Horizon Murano Environment;
2. Add the next component: Apache HTTP Server, MySql, WordPress;
3. Deploy Environment

Expected result:
Environment is successfully deployed;

Actual result:
Deployment is failed;

2016-05-24 13:31:37 — Action deploy is scheduled
2016-05-24 13:31:44 — Ensuring Apache is deployed.
2016-05-24 13:31:44 — Creating VM for MySql
2016-05-24 13:31:44 — Creating VM for Apache Server.
2016-05-24 13:33:32 — Instance is created. Deploying Apache
2016-05-24 13:35:24 — Instance is created. Deploying MySql
2016-05-24 13:40:34 — Apache is installed.
2016-05-24 13:40:34 — Apache is available at http://192.168.111.18
2016-05-24 13:42:37 — Creating database and user.
2016-05-24 13:42:37 — MySql application is installed.
2016-05-24 13:42:37 — Creating test_db database.
2016-05-24 13:43:43 — [murano.engine.system.agent.AgentException]: {'errorCode': 100, 'message': u'Script createDatabase returned error code', 'extra': None, 'details': {u'stdout': None, u'stderr': u'./createMySqlDatabase.sh: line 14: mysql: command not found', u'exitCode': 127}, 'time': u'2016-05-24 13:42:36.406023'}
2016-05-24 13:43:43 — Deployment finished with errors

FUEL Info:

api: '1.0'
astute_sha: 6c5b73f93e24cc781c809db9159927655ced5012
auth_required: true
build_id: '301'
build_number: '301'
feature_groups:
- mirantis
fuel-agent_sha: 50e90af6e3d560e9085ff71d2950cfbcca91af67
fuel-library_sha: 5d50055aeca1dd0dc53b43825dc4c8f7780be9dd
fuel-nailgun-agent_sha: d7027952870a35db8dc52f185bb1158cdd3d1ebd
fuel-ostf_sha: 2cd967dccd66cfc3a0abd6af9f31e5b4d150a11c
fuelmain_sha: a65d453215edb0284a2e4761be7a156bb5627677
nailgun_sha: 4162b0c15adb425b37608c787944d1983f543aa8
openstack_version: 2015.1.0-7.0
production: docker
python-fuelclient_sha: 486bde57cda1badb68f915f66c61b544108606f3
release: '7.0'
release_versions:
  2015.1.0-7.0:
    VERSION:
      api: '1.0'
      astute_sha: 6c5b73f93e24cc781c809db9159927655ced5012
      build_id: '301'
      build_number: '301'
      feature_groups:
      - mirantis
      fuel-agent_sha: 50e90af6e3d560e9085ff71d2950cfbcca91af67
      fuel-library_sha: 5d50055aeca1dd0dc53b43825dc4c8f7780be9dd
      fuel-nailgun-agent_sha: d7027952870a35db8dc52f185bb1158cdd3d1ebd
      fuel-ostf_sha: 2cd967dccd66cfc3a0abd6af9f31e5b4d150a11c
      fuelmain_sha: a65d453215edb0284a2e4761be7a156bb5627677
      nailgun_sha: 4162b0c15adb425b37608c787944d1983f543aa8
      openstack_version: 2015.1.0-7.0
      production: docker
      python-fuelclient_sha: 486bde57cda1badb68f915f66c61b544108606f3
      release: '7.0'

[Maksym Livshyn (mlivshyn)]

Again, tried to reproduce this issue a few times and got the same result. Connected to an instance that murano has created and found the next info in logs from murano-agent.log:

WARNING: The following packages cannot be authenticated!
  mysql-common libmysqlclient18 libdbi-perl libdbd-mysql-perl
  libterm-readkey-perl mysql-client-5.5 mysql-client
' run /opt/stack/venvs/murano-agent/local/lib/python2.7/site-packages/muranoagent/executors/application/__init__.py:69
2016-05-25 12:19:32.371 510 DEBUG application [-] 'deployWordPress.sh' execution stderr: 'W: Failed to fetch http://http.debian.net/debian/dists/jessie/InRelease

W: Failed to fetch http://http.debian.net/debian/dists/jessie-backports/InRelease

W: Failed to fetch http://http.debian.net/debian/dists/jessie/Release.gpg Could not resolve 'http.debian.net'

W: Failed to fetch http://http.debian.net/debian/dists/jessie-backports/Release.gpg Could not resolve 'http.debian.net'

W: Some index files failed to download. They have been ignored, or old ones used instead.
E: There are problems and -y was used without --force-yes
E: There are problems and -y was used without --force-yes
E: There are problems and -y was used without --force-yes
--2016-05-25 12:18:47-- http://wordpress.org/latest.zip
Resolving wordpress.org (wordpress.org)... failed: Name or service not known.
wget: unable to resolve host address ‘wordpress.org’
sudo: unzip: command not found
chown: cannot access ‘/var/www/html/wordpress’: No such file or directory
chmod: cannot access ‘/var/www/html/wordpress’: No such file or directory
cp: cannot stat ‘wp-config-sample.php’: No such file or directory
' run /opt/stack/venvs/murano-agent/local/lib/python2.7/site-packages/muranoagent/executors/application/__init__.py:73
2016-05-25 12:19:32.386 510 ERROR muranoagent.app [-] Error running execution plan
2016-05-25 12:19:32.386 510 TRACE muranoagent.app Traceback (most recent call last):
2016-05-25 12:19:32.386 510 TRACE muranoagent.app File "/opt/stack/venvs/murano-agent/local/lib/python2.7/site-packages/muranoagent/app.py", line 89, in _run
2016-05-25 12:19:32.386 510 TRACE muranoagent.app result = runner.run()
2016-05-25 12:19:32.386 510 TRACE muranoagent.app File "/opt/stack/venvs/murano-agent/local/lib/python2.7/site-packages/muranoagent/execution_plan_runner.py", line 39, in run
2016-05-25 12:19:32.386 510 TRACE muranoagent.app raise script_globals['__execution_plan_exception']
2016-05-25 12:19:32.386 510 TRACE muranoagent.app CustomException: Script deploy returned error code
2016-05-25 12:19:32.386 510 TRACE muranoagent.app

[Hidekazu Nakamura (nakamura-h)]

I was able to avoid this issue by using existing subnet with DHCP Name Server.
This is caused by not resolving name 'http.debian.net'.

[Valerii Kovalchuk (vakovalchuk)]

Moving to Invalid due to Incomplete status for 2 months