Kubespray: Inventory building is throwing errors about ruamel.yaml

[gvsphani]

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG

Environment:

• Cloud provider or hardware configuration: Openstack but not using terraform to create the environment, using heat instead

• OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
  Linux 3.10.0-957.5.1.el7.x86_64 x86_64
  NAME="CentOS Linux"
  VERSION="7 (Core)"
  ID="centos"
  ID_LIKE="rhel fedora"
  VERSION_ID="7"
  PRETTY_NAME="CentOS Linux 7 (Core)"
  ANSI_COLOR="0;31"
  CPE_NAME="cpe:/o:centos:centos:7"
  HOME_URL="https://www.centos.org/"
  BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

• Version of Ansible (ansible --version):
  ansible 2.7.8
  config file = /root/kubespray/ansible.cfg
  configured module search path = [u'/root/kubespray/library']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Oct 30 2018, 23:45:53) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]

Kubespray version (commit) (git rev-parse --short HEAD):
44de04b

Network plugin used: flannel

Copy of your inventory file: this is about inventory building

Command used to invoke ansible:
CONFIG_FILE=inventory/mktplcl/hosts.ini python3 contrib/inventory_builder/inventory.py ${IPS[@]}
Traceback (most recent call last):
File "contrib/inventory_builder/inventory.py", line 386, in
sys.exit(main())
File "contrib/inventory_builder/inventory.py", line 383, in main
KubesprayInventory(argv, CONFIG_FILE)
File "contrib/inventory_builder/inventory.py", line 76, in __init__
self.yaml_config = yaml.load(self.hosts_file)
File "/opt/rh/rh-python36/root/usr/lib64/python3.6/site-packages/ruamel/yaml/main.py", line 331, in load
return constructor.get_single_data()
File "/opt/rh/rh-python36/root/usr/lib64/python3.6/site-packages/ruamel/yaml/constructor.py", line 109, in get_single_data
node = self.composer.get_single_node()
File "/opt/rh/rh-python36/root/usr/lib64/python3.6/site-packages/ruamel/yaml/composer.py", line 87, in get_single_node
event.start_mark,
ruamel.yaml.composer.ComposerError: expected a single document in the stream
in "inventory/mktplcl/hosts.ini", line 4, column 1
but found another document
in "inventory/mktplcl/hosts.ini", line 15, column 1

Output of ansible run:

Anything else do we need to know:

[jhelbling]

@gvsphani
Please checkout v2.8.3 tag and check again

[farhany]

No more python problems with that tag version -- but did need to need ruamel.yaml. Shouldn't ruamel.yaml be in requirements.txt?

[cnaslain]

I've got the same issue under CentOS 7.
The checkout of v2.8.3 also solves this issue. Regression on the master branch?

[crazy-canux]

not working on my ubuntu16.04.

ansible --version
ansible 2.7.9
python version = 2.7.12 (default, Nov 12 2018, 14:36:49) [GCC 5.4.0 20160609]

CONFIG_FILE=inventory/mycluster/hosts.ini python3 contrib/inventory_builder/inventory.py ${IPS[@]}
Traceback (most recent call last):
File "contrib/inventory_builder/inventory.py", line 391, in
sys.exit(main())
File "contrib/inventory_builder/inventory.py", line 388, in main
KubesprayInventory(argv, CONFIG_FILE)
File "contrib/inventory_builder/inventory.py", line 77, in __init__
self.yaml_config = yaml.load(self.hosts_file)
File "/usr/local/lib/python3.5/dist-packages/ruamel/yaml/main.py", line 331, in load
return constructor.get_single_data()
File "/usr/local/lib/python3.5/dist-packages/ruamel/yaml/constructor.py", line 109, in get_single_data
node = self.composer.get_single_node()
File "/usr/local/lib/python3.5/dist-packages/ruamel/yaml/composer.py", line 87, in get_single_node
event.start_mark,
ruamel.yaml.composer.ComposerError: expected a single document in the stream
in "inventory/mycluster/hosts.ini", line 4, column 1
but found another document
in "inventory/mycluster/hosts.ini", line 15, column 1

[teipsum]

Is there a fix to this problem which does not require checking out a different version?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.