It is no longer supported by jammy and lead us to the following errors with the announce-release job.
```
No package matching 'python-dev' is available
```
Change-Id: I295bf25056f66c29649620ce8420382c4a151c1d
VirtualBMC is not a tool designed for production use; ensure this is
explicitly documented in the readme.
Story #2010382
Task #46661
Change-Id: I581b96b93d9b24f650ac0c6280d074708ec69ef4
When setting parameters revolving around boot
mode, options, firmware, it is necessary to
extract and edit the XML document.
Some details, however, are not automatically
extracted and libvirt must be told to provide
secure information. This change prevents us
from accidently loosing such configuration
parameters
Story: 2010382
Task: 46651
Change-Id: I0da2f37c5b630d2a180f59b74f23c027ee56e17b
Maintaining support for older not supported in Zed Python versions
would take too much effort with a lot of libraries dropping
compatibility with 3.6 and 3.7
Change-Id: I58a810d8cf4247153623c247de71f774928653aa
Also leave py3.6 test as it's still trendy
Remove l-c job definition from tox.ini, it was not used anyway and
we're removing l-c jobs everywhere
Fix tempest test
Change-Id: Ibdb5be75cf9e1c7a2ce26c05ee1e5e5d85d20482
We have updated the yoga testing runtime to keep the
py36 testing.
- https://review.opendev.org/c/openstack/governance/+/820195
Unit tests job template is also updated to keep python
3.6 as a voting job. So with the py3.6 and py3.9 testing as voting
job template, we are keeping python 3.6, 3.7, 3.8, and 3.9 as
tested versions in the Yoga cycle.
- https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/820286
This commit re-add the python 3.6/3.7 versions in setup.cfg classifier.
Change-Id: I0b1fd265bfed80b76e5eced456d80b65310b4368
UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
Change-Id: Id0b52f70e02b08d4983a218af7c2e34c38ec3c7d
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I2781f250f8db9907987b75b0c66ad8bfb041ccee
We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver for the release team.
Removed specific doc requirements from test-requirements.txt
Change-Id: Ib2570e01bef426c0e5ecfd59249d08ea00749b28
As discussed during the upstream ironic community meeting on
Monday Dec 14 2020, the lower-constraints job is being removed.
Change-Id: I79af2ef5dd144d7b0bd3e3036fbf0e671701ef6a
Remove pep8 dependencies from test-requirements, they're not
needed there and are hard to constraint properly.
Change lower-constraints to make pip resolver happy.
Change-Id: I85f2e368f6834888e3c82d365c2ecbcebfabd8e7
Also re-oreder jobs and add common openstack jobs for cover and
lower-constraints.
And disable dstat to prevent failures due to dstat bug in focal.
Change-Id: Ia219fdaac13c21d9fce08e69b45945d4b5e37a89
Versions of hacking from 3.1.0 until 4.0.0 NOT included are supposed
to require a safe version of flake8, so besides normale issues related
to minor version upgrades, we can safely use those versions.
Also forcing pycodestyle versions to be compatible with flake8 installed
by hacking.
Change-Id: I98bc624f9eb8f8153885e52366e34ac7a0e047fa
The current code logs the milliseconds twice:
2020-09-21 00:24:21,706.706 3484 DEBUG VirtualBMC [-] Get power...
The documentation for the logging module in py3 is quite
unambiguous about %(asctime) providing milliseconds.
The documentation in py2 is unclear on what is supposed
to offer, but in practice it works exactly as py3.
Change-Id: Ibb050c58d5fb949316700d7d2db4c77bd62f5e25
As recommended, since version 3.2.0 tox switches pip invocations
to use the module -m pip instead of direct invocation.
We set min version to 3.2.1 [1] to also fix the behavior of
--parallel--safe-build
[1] https://tox.readthedocs.io/en/latest/changelog.html#v3-2-1-2018-08-10
Change-Id: I4003a8bebc7737250d0c318426e885d0888df57d
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we don't need it
in lower-constraints.
These changes will help us to drop `mock` from openstack/requirements
Change-Id: Iccbcd6deddc1d246d214a2c52086a0cc8d911882
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Set openstackdocs_pdf_link to link to PDF file. Note that
the link to the published document only works on docs.openstack.org
where the PDF file is placed in the top-level html directory. The
site-preview places the PDF in a pdf directory.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I20ea481c1dd9651258b8ae13da9b1e1ec710482b
libvirt-python needs to be compiled also during doc building, add
"compile" target to bindep which is used for install and doc jobs.
This fixes the doc CI jobs.
Change-Id: I8ec597485db067a919d2455a81b7fe79b83153f7
Full py3 compatible version.
Add all Python3 modules to stdlib list.
Also includes fix to an enum34 dependency bug.
Change-Id: I26f38e18ce5c1c61aadbc1590a79c97e7b3c4ab4
Now that we no longer support py27, we can use the standard library
unittest.mock module instead of the third party mock lib.
Change-Id: I436eab174b823c1e0e028529fed9009cc38776bc
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg
- Update classifiers
- Update requirements, no need for python_version anymore
- Use sphinx-build everywhere
Change-Id: I737d176d35d3bc55848645af05f0362ab3853844
The new version enables a lot of standard flake8 checks, so a few
fixes are required. W503 is disabled as it conflicts with W504
and the latter seems to be preferred nowadays.
Change-Id: Ic1efc86ec41daf6fadb4cebb8a73b4dd158f880a
The virtualbmc-tempest-ironic-ipmi-iscsi job is based on
ironic-base job which will default to dib.
To prevent breaking the virtualbmc CI we set the ramdisk
type to tinyipa for now and we'll convert the jobs here later.
Change-Id: I0aaf3c8114de03c8eac00f885928fc4d85d4ac08
The daemon child processes do not respond to a SIGTERM. This means that
they stay running indefinitely. This is because the manager process
installs a SIGTERM handler to propagate the signal to children, and this
handler is inherited by the children.
Return children to the default handler for SIGTERM.
Change-Id: I784e7cd9e0545a591150dc21a8232bd85672c21c
Story: 2003534
Task: 24819
Jay Faulkner