Comment 19 for bug 1834218
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to metal (f/centos8) | #19 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: f/centos8
commit 1f0706ee30f44c6
Author: Don Penney <email address hidden>
Date: Mon Feb 3 12:48:03 2020 -0500
Drop clone.py references from boot menu comment blocks
As part of recent code cleanup activities, the controllerconfig
clone.py module was dropped. This update removes references to this
file from the comment blocks of the boot menu files grub.cfg and
centos.
Change-Id: If2260c74f58a61
Partial-Bug: 1834218
Signed-off-by: Don Penney <email address hidden>
commit 91f488af02e2bc2
Author: Jim Somerville <email address hidden>
Date: Mon Jan 27 17:18:47 2020 -0500
Security: Handle nospectre_v1 in the bootargs
Most of the v1 mitigation is baked into the kernel and not
optional. The swapgs barriers are, however, optional.
They have a negative performance impact so we disable them
by using the nospectre_v1 kernel bootarg.
Partial-Bug: 1860193
Depends-On: https:/
Change-Id: Id11232fe113293
Signed-off-by: Jim Somerville <email address hidden>
commit eff0d663776587a
Author: Angie Wang <email address hidden>
Date: Mon Jan 20 15:09:10 2020 -0500
Remove unused post_clone_
Change-Id: I3be9384b94473c
Partial-Bug: 1834218
Depends-On: https:/
Signed-off-by: Angie Wang <email address hidden>
commit 4609dacc5f2ffa5
Author: Eric MacDonald <email address hidden>
Date: Mon Jan 20 11:34:07 2020 -0500
Fix rvmc container build
The current rvmc container build has a conflict over the
python3-pip install.
The CentOS repo has a prior version of python3-pip that
requires python3 3.6 but the CENGN repo requires 3.7 due
to the Titanium base image.
The issue is resolved by updating this dockerfile with an
older verison of python3-pip.
Also, Since python3-pip provides pip3 the explicit pip3
install is no longer required.
Change-Id: Ic0cf0d070eaa8f
Story: 2006980
Task: 37775
Signed-off-by: Eric MacDonald <email address hidden>
commit a9a2ca64bc409dd
Author: Saul Wold <email address hidden>
Date: Wed Jan 15 19:22:09 2020 -0800
rvmc: remove un-used build data
The error below reported in the build logs because rvmc is not
setup to be built as an RPM package.
ERROR: build_dir (425): Neither srpm_path nor .spec file not found
in '/localdisk/
Closes-Bug: 1859893
Change-Id: I9b2788bb227afb
Signed-off-by: Saul Wold <email address hidden>
commit d59ba5fdc21a895
Author: Al Bailey <email address hidden>
Date: Tue Jan 7 08:41:36 2020 -0600
Remove unused inventory and python-
Neither of these components were maintained or used, and so are
being abandoned.
- inventory was an old fork of the sysinv code
- python-
The devstack commands, although currently disabled, have also
been updated.
Change-Id: If6a109edbc70eb
Story: 2004515
Task: 37538
Depends-On: https:/
Signed-off-by: Al Bailey <email address hidden>
commit e86d0b915896b74
Author: Eric MacDonald <email address hidden>
Date: Fri Jan 3 14:28:28 2020 -0500
Fix MNFA timer timeout condition check
A timer module change made in https:/
introduced a change that makes all unstarted/stopped timers appear
as expired/rung.
A MNFA (Multi Node Failure Avoidance) timeout of zero represents no
timeout and is implemented by not starting a timer for that condition.
However, due to the recent change, that makes the MNFA timer expiry
check succeed immediatly causing MNFA to exit prematurely causing the
issue reported by the Bug reference.
The fix is to condition the timer expiry check with a non-zero MNFA
timeout value.
Test Plan:
PASS: Verify MNFA handling with and without timeout.
PASS: Verify 3 node MNFA handling due to node power cycle
PASS: Verify 2 node MNFA handling and recovery due to cable pull
Change-Id: I97363cd309f786
Closes-Bug: 1858216
Signed-off-by: Eric MacDonald <email address hidden>
commit e68db45a2e12fb2
Author: Al Bailey <email address hidden>
Date: Mon Dec 23 10:49:58 2019 -0600
Add pylint checks for python files in metal
Created a pylint.rc file for running pylint
Added a pylint task to zuul
Targets the following python files:
- redfish docker code
- hwmond_notify
Other python components in metal are not being included
because they are being removed in later commits.
Story: 2004515
Task: 37956
Change-Id: I782672c366e56d
Signed-off-by: Al Bailey <email address hidden>
commit 9bf231a2866c0ff
Author: Eric MacDonald <email address hidden>
Date: Fri Jan 3 09:34:37 2020 -0500
Fix BMC access loss handling
Recent refactoring of the BMC handler FSM introduced a code change that
prevents the BMC Access alarm from being raised after initial BMC
accessibility was established and is then lost.
This update ensures BMC access alarm management is working properly.
This update also implements ping failure debounce so that a single ping
failure does not trigger full reconnection handling. Instead that now
requires 3 ping failures in a row. This has the effect of adding a minute
to ping failure action handling before the usual 2 minute BMC access failure
alarm is raised. ping failure logging is reduced/improved.
Test Plan: for both hwmond and mtcAgent
PASS: Verify BMC access alarm due to bad provisioning (un, pw, ip, type)
PASS: Verify BMC ping failure debounce handling, recovery and logging
PASS: Verify BMC ping persistent failure handling
PASS: Verify BMC ping periodic miss handling
PASS: Verify BMC ping and access failure recovery timing
PASS: Verify BMC ping failure and recovery handling over BMC link pull/plug
PASS: Verify BMC sensor monitoring stops/resumes over ping failure/recovery
Regression:
PASS: Verify IPv6 System Install using provisioned BMCs (wp8-12)
PASS: Verify BMC power-off request handling with BMC ping failing & recovering
PASS: Verify BMC power-on request handling with BMC ping failing & recovering
PASS: Verify BMC reset request handling with BMC ping failing & recovering
PASS: Verify BMC sensor group read failure handling & recovery
PASS: Verify sensor monitoring after ping failure handling & recovery
Change-Id: I74870816930ef6
Closes-Bug: 1858110
Signed-off-by: Eric MacDonald <email address hidden>
commit 09b95bf651c065e
Author: Don Penney <email address hidden>
Date: Thu Jan 2 17:40:09 2020 -0500
Update kickstarts to generate DNF repo config files
As the patching framework is updated to use DNF instead of the smart
package manager, the kickstarts are updated to generate the initial
DNF repo config files, rather than configure the smartpm channels.
Depends-On: https:/
Change-Id: Ic625aa4646b457
Story: 2006227
Task: 37935
Signed-off-by: Don Penney <email address hidden>
commit 8959d8258ddd6be
Author: Eric MacDonald <email address hidden>
Date: Sun Dec 8 16:35:51 2019 -0500
Utility to install a server via Redfish
This update introduces the implementation for a docker container named
'rvmc', standing for Redfish Virtual Media Controller, which executes a
python file that imports the open source redfish-
establish a secure Redfish communication session with a Redfish
supported Board Management Controller to insert a URL based ISO image
into its Virtual Media CD/DVD device so that on that server's next
reboot will boot and install that image.
This container supports single and multi target configuration files with
IPV4 and IPV6 BMC addressing.
Change-Id: I4d555046800c8d
Depends-On: https:/
Depends-On: https:/
Story: 2006980
Task: 37775
Signed-off-by: Eric MacDonald <email address hidden>
commit 6ccd0f4a4322b62
Author: marvin <email address hidden>
Date: Tue Nov 19 15:26:03 2019 +0800
Monitor the datanetwork for non-OpenStack work node
Update the lmon to support datanetwork interface monitoring
and use collectd to control the alarm information. Now lmon
will obtain the list of interfaces from /etc/lmon/lmon.conf
which can be generated by puppet.
Change-Id: Ice72eda03d1bbd
Story: #2002948
Task: #37326
Signed-off-by: marvin <email address hidden>