openstack | Repository tracking all OpenStack repositories

You should get used to use and abuse the debug module.

Provided that the ansible ad-hoc command raised you that the facts are under ansible_facts, you could have done a simple task in your playbook:

Use a dictionary comprehension:

I've got an answer through github through the official Gnocchi repository.

It looks like you cannot directly get the same output, although there are two possible strategies to get close to it:

1. Define an archive policy that matches the desired aggregation.
2. Perform the http requests for each stat and aggregate data manually later.

More about that can be directly found here

The order was wrong, as well as lots of unneccessary elements causing errors and crashes.

Current working code is:

You can use a better mechanism than ignore_errors in this case, it is failed_when.
With it, you can fine grain the failure of a task to exactly what you want.

In your case it would be something like:

From the documentation:

Shallow clone.
Perform a shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.

Lightweight checkout.
If selected, try to obtain the Pipeline script contents directly from the SCM without performing a full checkout. The advantage of this mode is its efficiency; however, you will not get any changelogs or polling based on the SCM. (If you use checkout scm during the build, this will populate the changelog and initialize polling.) Also build parameters will not be substituted into SCM configuration in this mode. Only selected SCM plugins support this mode.

To sum up:

• Shallow Clone is the Git feature that lets you pull down just the latest commits, not the entire repo history. So if your project has years of history, or history from thousands of commits, you can select a particular depth to pull.
• Lightweight checkout is a Jenkins capability that enables to pull a specific file from the repo, as opposed to the entire repo. So it is useful for example when fetching the Jenkinsfile from a repo because you you need only the specific file and Don't care about other SCM information.

PYTHONWARNINGS certainly does suppress python's warnings. Try running:

Does the support for Ubuntu 18.04.6 LTS (bionic) deprecated?

Not exactly.

As a general rule, the latest version of the script targets the latest supported (by Openstack) versions of the host operating systems. Older versions may work. But there might be minor issues ... that someone with the ability to read / diagnose shell scripts ought to be able to figure out.

If you need a version of the script that explicitly supports (say) Bionic, there will be one in the Git6 repo history.

^{(This is in line with general OpenStack Ubuntu support. The latest OpenStack release is Wallably and Wallaby no longer supports Bionic. The Bionic -> Focal cross-over release of Openstack was Ussuri; see https://ubuntu.com/openstack/docs/supported-versions. Note that Devstack is not an official OpenStack product, but they are effectively forced to track the "supported release" rules, at least loosely.)}

The version of the Devstack script that you checked out does not explicitly supports Focal rather than Bionic.

If you look at https://opendev.org/openstack/devstack/src/branch/master/stack.sh on line 230, it currently says:

• 1, check whether the network:dhcp port exist or not, it should exist and show that there is one or more ports which has the ip at the head of the range within start=192.168.14.241,end=192.168.14.249. Like this: