There are potentially two related issues here which can result in
an empty generated groups file. The first is that if there are OS_
environment variables set, then os-client-config can create an 'environ'
cloud. That cloud then, in most cases here, will not be a valid cloud
since it won't be a full config, so iterating over all existing clouds
to get their server will fail, meaning that the inventory will be empty
meaning that generated groups will then be generated empty.
To deal with that, we can consume the newer upstream option that allows
the inventory to not bail out if it has a bad cloud, but instead get all
of the resources from the clouds that do work.
Additionally though, we can do an explicit inventory run so that we can
look to see if the inventory run failed, and if so, avoid running the
expand-groups.sh script, since we'd be fairly assured that it would be
running on top of a bad inventory cache.
Change-Id: Ib18987b3083f6addc61934b435d7ecb14aa1d25a
For --config-drive to actually work as advertised in launch-node.py,
it needs to default to False. Otherwise this option is useless.
Change-Id: Ib29fa758779e89d3d25399615fd009b836dda598
So that puppet can find the hiera data for
signing01.ci.openstack.org, put its node pattern in the signing
group.
Change-Id: Ic073605307ff4f14d4e3a1753de0a6e0e9d9542b
Servers are now on same physical location, thus decided
to have two logical sets of hosts, vanilla and chocolate.
Change-Id: I91f48f14f4bd33017b418dd8013fba0b82a80485
This reverts commit 91dcb510bace2f3a14745c18e945f8504a325c15.
The implementation ignored that the referenced template is being
used by many vhosts but the lists for aliases and directories were
defined at (and referenced from) the containing class scope. This
coupled with the newly introduced conditional for the directories
array caused all other vhosts using this template to no longer get
Directory blocks for their docroots.
Change-Id: I808e654a6fb77440e7aecbde4456ddc720fe0d9a
While the host is eavesdrop.openstack.org this particular site is
configured to upload yaml2ical assets. Rename the site so that it
is clearer and if we need to publish elsewhere on eavesdrop.o.o
we can create new ones.
Needed-By: Ic87de4f3c39e19769144095eb809ee7561c117a5
Change-Id: I6262bb839449402c65c7f48a07d8776c1b44a295
Running this playbook on the puppetmaster we consistently run into ssh
failures due to async reconnecting periodically and network issues
between hosts. We can address this by starting a single connection
without async and polling on that which appears to be the default
wait_for behavior. Testing of this seems to indicate it is more
reliable.
Change-Id: Iec72e2c0d099c0e28bc4b4b48608a03b3e66b4c0
We don't need UDebComponents since there is no debian-installer.
Additionally, fix a typo with our updates field.
Change-Id: I070ea1df8897a5388919e30bfbdd54e07fc3b30e
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
With the switch to zuul launcher instead of jenkins we now get the zmq
finished event after all logs are done copying (unlike with jenkins
where the console log could show up later). As a result we don't need to
continue trying to download console logs until some EOF file string
shows up, instead we can download what is there and know it is
complete.
Change-Id: I789c073a2fab8863de833684bc64b3e5cb405cf8
This is a continuation of https://review.openstack.org/326821 to setup
the #openstack-fwaas channel with statusbot and meetbot. The objective
is to get Eavesdrop logging for the channel.
Change-Id: Ia010b781140b6e8d322e9227c733a0630f3a5fb6
Create the signing01.ci.openstack.org job node and puppet the
signing subkey onto it via pubring.gpg and secring.gpg files stored
in private hiera. Also set up some basic configuration and packages
on the management bastion to aid in key management/rotation, and add
the beginnings of administrative documentation for this.
Change-Id: Iecddb778994a38f7898e0c20e7f3f8e93f0a7f60
Depends-On: I70c3b82185681ee64791cda653360c26a93bd466
Story: #2000336
Signed-off-by: Jeremy Stanley <fungi@yuggoth.org>
This patch adds IRC bots to #openstack-pkg, for the packaging-deb group.
It looks like "openstackgerrit" (gerrit change reports) is already there,
but "openstack" (channel logging) and "openstackstatus" (infra status
notifications, success submissions) are not yet because the channel is
not in the "meetbot_channels" and "statusbot_channels" sections.
Change-Id: I91adbf4392cb028de55693f5c09f438cd4d9fb54
This is a redo of change 9c717d9c108b32. That change was incorrect,
the server needs to be placed on the disable list.
Change-Id: I3d0962b975ffaf4560bace88abddb2f661763d55
