Bug 1882005 - NTO does not create machine config for the master machine config pool
Summary: NTO does not create machine config for the master machine config pool
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node Tuning Operator
Version: 4.6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 4.5.z
Assignee: Jiří Mencák
QA Contact: Simon
URL:
Whiteboard:
Depends On: 1881422
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-23 15:08 UTC by OpenShift BugZilla Robot
Modified: 2020-10-19 14:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-19 14:54:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-node-tuning-operator pull 157 0 None closed [release-4.5] Bug 1882005: Issue a warning when two or more profiles use the same priority. 2020-12-02 17:35:29 UTC
Red Hat Product Errata RHBA-2020:4228 0 None None None 2020-10-19 14:55:21 UTC

Comment 3 Simon 2020-10-13 19:24:56 UTC
Cluster version: 4.5.0-0.nightly-2020-10-10-030038

for pr in $(oc get profiles -n openshift-cluster-node-tuning-operator --no-headers | cut -d ' ' -f 1); do echo $pr; oc get profile $pr -n openshift-cluster-node-tuning-operator -o json | jq ".spec.config.tunedProfile"; done
ip-10-0-159-69.us-east-2.compute.internal
"openshift-node-performance-hp-performanceprofile"
ip-10-0-166-18.us-east-2.compute.internal
"openshift-node-performance-hp-performanceprofile"
ip-10-0-215-9.us-east-2.compute.internal
"openshift-node-performance-hp-performanceprofile"

$ oc get mc | grep nto
50-nto-master                                                                                          2.2.0             2m15s

$ echo cat /proc/cmdline | oc debug node/ip-10-0-159-69.us-east-2.compute.internal
Starting pod/ip-10-0-159-69us-east-2computeinternal-debug ...
To use host binaries, run `chroot /host`
Pod IP: 10.0.159.69
If you don't see a command prompt, try pressing enter.
BOOT_IMAGE=(hd0,gpt1)/ostree/rhcos-10fe98b7d7770b33481b7a33ff023aa006d6c66e554b180c6f32b52447cde021/vmlinuz-4.18.0-193.24.1.el8_2.dt1.x86_64 rhcos.root=crypt_rootfs random.trust_cpu=on console=tty0 console=ttyS0,115200n8 rd.luks.options=discard ostree=/ostree/boot.1/rhcos/10fe98b7d7770b33481b7a33ff023aa006d6c66e554b180c6f32b52447cde021/0 ignition.platform.id=aws skew_tick=1 nohz=on rcu_nocbs= tuned.non_isolcpus= intel_pstate=disable nosoftlockup tsc=nowatchdog intel_iommu=on iommu=pt isolcpus=managed_irq, systemd.cpu_affinity= default_hugepagesz=2M +

Comment 5 errata-xmlrpc 2020-10-19 14:54:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.5.15 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4228


Note You need to log in before you can comment on or make changes to this bug.