Bug 1909642 - [vsphere] Fail to update machine-config with error: Unit file nodeip-configuration.service does not exist
Summary: [vsphere] Fail to update machine-config with error: Unit file nodeip-configur...
Keywords:
Status: CLOSED DUPLICATE of bug 1910738
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Antonio Murdaca
QA Contact: Michael Nguyen
URL:
Whiteboard:
: 1909643 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-21 09:29 UTC by jima
Modified: 2021-04-05 17:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-04 18:10:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description jima 2020-12-21 09:29:16 UTC
Description of problem:
Install upi-on-vsphere with nightly build 4.7.0-0.nightly-2020-12-20-031835. After installation is completed, then try to update machine-config.
For example, apply below new "ImageContentSourcePolicy":

apiVersion: operator.openshift.io/v1alpha1
kind: ImageContentSourcePolicy
metadata:
  name: brew-registry
spec:
  repositoryDigestMirrors:
  - mirrors:
    - brew.registry.redhat.io
    source: registry.redhat.io
  - mirrors:
    - brew.registry.redhat.io
    source: registry.stage.redhat.io
  - mirrors:
    - brew.registry.redhat.io
    source: registry-proxy.engineering.redhat.com

Then waiting for machine-config update, but mco is degraded with error:
# ./oc get co | grep machine-config
machine-config                             4.7.0-0.nightly-2020-12-20-031835   False       False         True       15m

# ./oc get co machine-config -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  annotations:
    exclude.release.openshift.io/internal-openshift-hosted: "true"
    include.release.openshift.io/self-managed-high-availability: "true"
    include.release.openshift.io/single-node-developer: "true"
  creationTimestamp: "2020-12-21T04:26:30Z"
  generation: 1
  managedFields:
  - apiVersion: config.openshift.io/v1
  ......
  name: machine-config
  resourceVersion: "107909"
  uid: 5afe65fb-437e-4b26-bb97-e7c001221c81
spec: {}
status:
  conditions:
  - lastTransitionTime: "2020-12-21T04:30:24Z"
    message: Cluster version is 4.7.0-0.nightly-2020-12-20-031835
    status: "False"
    type: Progressing
  - lastTransitionTime: "2020-12-21T08:52:18Z"
    message: 'Failed to resync 4.7.0-0.nightly-2020-12-20-031835 because: timed out waiting for the condition during syncRequiredMachineConfigPools: error pool master is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 1)'
    reason: RequiredPoolsFailed
    status: "True"
    type: Degraded
  - lastTransitionTime: "2020-12-21T08:52:18Z"
    message: Cluster not available for 4.7.0-0.nightly-2020-12-20-031835
    status: "False"
    type: Available
  - lastTransitionTime: "2020-12-21T08:42:18Z"
    reason: One or more machine config pool is degraded, please see `oc get mcp` for further details and resolve before upgrading
    status: "False"
    type: Upgradeable
  extension:
    master: 'pool is degraded because nodes fail with "1 nodes are reporting degraded status on sync": "Node control-plane-0 is reporting: \"error enabling unit: Failed to enable unit: Unit file nodeip-configuration.service does not exist.\\n\""'
    worker: 'pool is degraded because nodes fail with "1 nodes are reporting degraded status on sync": "Node compute-1 is reporting: \"error enabling unit: Failed to enable unit: Unit file nodeip-configuration.service does not exist.\\n\""'

Then checked on node, it is indeed not find file nodeip-configuration.service. And this service should only be present on ipi-on-vsphere cluster.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install 4.7.0-0.nightly-2020-12-20-031835 
2. Apply new machine-config
3.

Actual results:
machine-config operator is degraded.

Expected results:
Update should be successful.

Additional info:
It works on 4.7.0-0.nightly-2020-12-13-104805

Comment 1 jima 2020-12-21 09:32:39 UTC
*** Bug 1909643 has been marked as a duplicate of this bug. ***

Comment 2 jima 2020-12-23 06:03:22 UTC
The issue is also reproduced when upgrading on upi-on-vsphere cluster from 4.6.0-0.nightly-2020-12-21-163117 to 4.7.0-0.nightly-2020-12-21-131655.

mco is degraded with error: 
   master: 'pool is degraded because nodes fail with "1 nodes are reporting degraded
      status on sync": "Node control-plane-1 is reporting: \"error enabling unit:
      Failed to enable unit: Unit file nodeip-configuration.service does not exist.\\n\""'
    worker: 'pool is degraded because nodes fail with "1 nodes are reporting degraded
      status on sync": "Node compute-1 is reporting: \"error enabling unit: Failed
      to enable unit: Unit file nodeip-configuration.service does not exist.\\n\""'

Comment 3 Ben Howard 2021-01-04 18:10:33 UTC

*** This bug has been marked as a duplicate of bug 1910738 ***

Comment 4 W. Trevor King 2021-04-05 17:46:19 UTC
Removing UpgradeBlocker from this older bug, to remove it from the suspect queue described in [1].  If you feel like this bug still needs to be a suspect, please add keyword again.

[1]: https://github.com/openshift/enhancements/pull/475


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