Undercloud install failed.

[Matthias Runge]

Undercloud install failed.

Reason: No JSON object could be decoded

See the previous output for details about what went wrong. The full install
log can be found at /home/stack/.instack/install-undercloud.log.

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1505, in install
    _validate_configuration()
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 711, in _validate_configuration
    _validate_no_ip_change()
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 689, in _validate_no_ip_change
    network_config = json.loads(f.read())
  File "/usr/lib64/python2.7/json/__init__.py", line 338, in loads
    return _default_decoder.decode(s)
  File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
Command 'instack-install-undercloud' returned non-zero exit status 1

It tries to read/decode the file /etc/os-net-config/config.json which is zero sized.
-rw-r--r--. 1 root root 0 May 15 14:12 config.json

No idea why? I'm using tripleo-quickstart with master snapshot from May 15th: ./quickstart.sh --requirements quickstart-extras-requirements.txt --tags all --teardown all --no-clone -p quickstart-extras.yml <ip-addr>

[Prateek Arora (parora)]

Found the same error again on a RDO Cloud VM

[Matthias Runge (mrunge)]

workaround: rm rm /etc/os-net-config/config.json

In my case, that doesn't really help: https://paste.fedoraproject.org/paste/pa38TkdY23gAh0POIPQ1yF5M1UNdIGYhyRLivL9gydE=

[Matthias Runge (mrunge)]

fun fact, that happens with master, with ocata, with a ci passed image from master.

[Michele Baldessari (michele)]

So I tried the following and it all just worked for me:
./quickstart.sh -v --working-dir $BASEDIR \
  --requirements requirements.txt \
  -p quickstart-extras.yml -r quickstart-extras-requirements.txt \
  -X \
  --bootstrap \
  -T all \
  --release master \
  --config /home/ospdeploy/ci/tripleo-quickstart/tripleo-quickstart/config/general_config/pacemaker.yml \
  --nodes /home/ospdeploy/ci/tripleo-quickstart/tripleo-quickstart/config/nodes/3ctlr_1comp.yml \
  $SCALEBOX 2>&1 | tee $LOGFILE || result=1

Also I could not find the master-passed-ci files. Do those come from somewhere else or am I being blind?

[Matthias Runge (mrunge)]

for completeness: master-passed-ci.yml looks like this:

cat config/release/master-passed-ci.yml
release: master-passed-ci
undercloud_image_url: https://images.rdoproject.org/master/delorean/current-tripleo/stable/undercloud.qcow2
overcloud_image_url: https://images.rdoproject.org/master/delorean/current-tripleo/stable/overcloud-full.tar
ipa_image_url: https://images.rdoproject.org/master/delorean/current-tripleo/stable/ironic-python-agent.tar
repos:
  - type: generic
    reponame: delorean
    filename: delorean.repo
    baseurl: http://trunk.rdoproject.org/centos7/current-passed-ci/
    hash_url: https://trunk.rdoproject.org/centos7/current-passed-ci/delorean.repo
    priority: 20

  - type: file
    filename: delorean-deps.repo
    down_url: https://trunk.rdoproject.org/centos7/delorean-deps.repo

  - type: package
    pkg_name: centos-release-ceph-jewel
    custom_cmd: 'sudo yum install -y --enablerepo=extras'

  - type: package
    pkg_name: centos-release-opstools
    custom_cmd: 'sudo yum install -y'

repo_cmd_after: |
  sudo yum-config-manager --save --setopt centos-ceph-jewel.gpgcheck=0
  sudo yum-config-manager --save --setopt centos-opstools.gpgcheck=0
  sudo yum repolist;
  sudo yum update -y

[Matthias Runge (mrunge)]

It is reproducible on my bare metal node with as little as
./quickstart.sh --no-clone \
                --clean --teardown all \
                --release master \
                <ipaddr>

[Julie Pichon (jpichon)]

"openstack undercloud upgrade" is failing for me in the same way, on a system set up with quickstart a couple of weeks ago. The error happens early on, right after:

2018-02-16 10:48:52,543 INFO: Logging to /home/stack/.instack/install-undercloud.log
2018-02-16 10:48:52,561 INFO: Checking for a FQDN hostname...
2018-02-16 10:48:52,589 INFO: Static hostname detected as undercloud
2018-02-16 10:48:52,599 INFO: Transient hostname detected as undercloud
2018-02-16 10:48:52,602 DEBUG: An exception occurred
(snip)

Workaround in comment #2 not working for me either. That file is empty though, if it matters.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE