Skip to content

Issues: openshift/machine-config-operator

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

allow setting label to nodes about to be upgraded/restarted lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#3204 opened Jun 22, 2022 by ibotty
MCD fails with empty string in source lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#2705 opened Aug 5, 2021 by Xaenalt
tracker for: Marking Degraded due to: machineconfig.machineconfiguration.openshift.io "rendered-..." not found lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#2114 opened Sep 22, 2020 by cgwalters
Allow administrators to guide upgrade ordering lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#2059 opened Sep 3, 2020 by cgwalters
machine-specific machineconfigs lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1720 opened May 8, 2020 by cgwalters
enhance flow for custom machineconfigs for specific machinesets lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1619 opened Apr 6, 2020 by cgwalters
move rhel7 worker node updates entirely to openshift-ansible lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1592 opened Mar 26, 2020 by cgwalters
The MCD is stuck and unable to recover from file degradations jira lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1443 opened Feb 5, 2020 by yuqi-zhang
Capture and report systemd unit failures by default to the MCS jira lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1365 opened Jan 10, 2020 by cgwalters
Enable RH Registry signature verification by default lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1349 opened Dec 19, 2019 by jasinner
Simplify controller architecture, merge "operator" and "controller" lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#878 opened Jun 21, 2019 by ericavonb
Manage sebooleans in MachineConfig lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#852 opened Jun 13, 2019 by runcom
get rid of ./lib/* fork lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#819 opened Jun 5, 2019 by runcom
Future Release Branches Frozen For Merging | branch:release-4.18 branch:release-4.19 tide/merge-blocker Denotes an issue that blocks the tide merge queue for a branch while it is open.
#637 opened Apr 15, 2019 by openshift-merge-robot
move types to openshift/api lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#588 opened Mar 27, 2019 by runcom
MCD: Actually handle directories and symlinks jira lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#125 opened Oct 11, 2018 by jlebon
ProTip! Type g i on any issue or pull request to go back to the issue listing page.