ansible-playbook install error

[chenxiang2019]

Hi, all.

I'm trying BESS recently and attempt to install BESS using ansible. However, when I execute the command:

$ ansible-playbook -K -t package -i localhost, -c local env/bess.yml

It raises an error. The error log:

SUDO password: 
[DEPRECATION WARNING]: 'include' for playbook includes. You should use 
'import_playbook' instead. This feature will be removed in version 2.8. 
Deprecation warnings can be disabled by setting deprecation_warnings=False in 
ansible.cfg.

PLAY [all] *********************************************************************

TASK [Gathering Facts] *********************************************************
ok: [localhost]

TASK [apt_repository] **********************************************************
ok: [localhost]

TASK [apt_key] *****************************************************************
ok: [localhost]

TASK [apt_repository] **********************************************************
ok: [localhost]

TASK [apt_repository] **********************************************************
ok: [localhost]

TASK [Install list of packages (this step may take a long time)] ***************
ok: [localhost] => (item=[u'apt-transport-https', u'ca-certificates', u'build-essential', u'g++-5', u'g++-6', u'g++-7', u'clang-3.8', u'clang-4.0', u'autoconf', u'automake', u'libtool', u'make', u'cmake', u'pkg-config', u'libpthread-stubs0-dev', u'libunwind8-dev', u'liblzma-dev', u'zlib1g-dev', u'libpcap-dev', u'libssl-dev', u'curl', u'git', u'python', u'python-dev', u'python-pip', u'python-scapy', u'libgflags-dev', u'libgoogle-glog-dev', u'libgraph-easy-perl', u'libgtest-dev', u'linux-headers-generic', u'lcov', u'python-autopep8'])

TASK [Install clang-5.0 on x86_64] *********************************************
fatal: [localhost]: FAILED! => {"cache_update_time": 1509869397, "cache_updated": false, "changed": false, "failed": true, "msg": "'/usr/bin/apt-get -y -o \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\"     install 'clang-5.0'' failed: E: Unable to correct problems, you have held broken packages.\n", "rc": 100, "stderr": "E: Unable to correct problems, you have held broken packages.\n", "stderr_lines": ["E: Unable to correct problems, you have held broken packages."], "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nSome packages could not be installed. This may mean that you have\nrequested an impossible situation or if you are using the unstable\ndistribution that some required packages have not yet been created\nor been moved out of Incoming.\nThe following information may help to resolve the situation:\n\nThe following packages have unmet dependencies:\n clang-5.0 : Depends: libclang-common-5.0-dev (= 1:5.0~svn318542-1~exp1) but it is not going to be installed\n", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "Some packages could not be installed. This may mean that you have", "requested an impossible situation or if you are using the unstable", "distribution that some required packages have not yet been created", "or been moved out of Incoming.", "The following information may help to resolve the situation:", "", "The following packages have unmet dependencies:", " clang-5.0 : Depends: libclang-common-5.0-dev (= 1:5.0~svn318542-1~exp1) but it is not going to be installed"]}
	to retry, use: --limit @/home/sdn/bess/env/bess.retry

PLAY RECAP *********************************************************************
localhost                  : ok=6    changed=0    unreachable=0    failed=1  

And I tried ansible-playbook -K -t package -i localhost, -c local env/bess.yml --limit @/home/sdn/bess/env/bess.retry in order to resolve this problem but the script reports the same error. How can I fix this problem? Thank you very much!

[chenxiang2019]

This problem could be resolved by commenting the installation statements on package.yml. I install the clang-5.0 manually on my system for meeting the requirements.

[chenxiang2019]

I think I could close this issue.