-
Notifications
You must be signed in to change notification settings - Fork 20
OCPBUGS-4465: Log message if nmstate output is '--- {}\n' #72
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
Conversation
@kevydotvinu: This pull request references Jira Issue OCPBUGS-4465, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@kevydotvinu: This pull request references Jira Issue OCPBUGS-4465, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@kevydotvinu: This pull request references Jira Issue OCPBUGS-4465, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@kevydotvinu: This pull request references Jira Issue OCPBUGS-4465, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@kevydotvinu: This pull request references Jira Issue OCPBUGS-4465, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@kevydotvinu: This pull request references Jira Issue OCPBUGS-4465, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@kevydotvinu: This pull request references Jira Issue OCPBUGS-4465, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@kevydotvinu: This pull request references Jira Issue OCPBUGS-4465, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
pkg/ignition/builder.go
Outdated
@@ -73,6 +73,9 @@ func (b *ignitionBuilder) ProcessNetworkState() (error, string) { | |||
} | |||
return err, "" | |||
} | |||
if string(out) == "--- {}\n" { | |||
return nil, "no network configuration file(s): " + string(out) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No point to add string(out) to the message: it does not provide any details
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ack @dtantsur. I will make the change. And will the no network configuration file(s)
be the appropriate message here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we cannot add anything more useful - yes. Does it log any errors to stderr though?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @dtantsur, no stderr
. Hence I have changed the message to no network configuration
. Please review and let me know if anything needs to be added.
@@ -73,6 +73,9 @@ func (b *ignitionBuilder) ProcessNetworkState() (error, string) { | |||
} | |||
return err, "" | |||
} | |||
if string(out) == "--- {}\n" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want to add the same to GenerateConfig? Maybe even extracted to a helper function?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I tested without the GenerateConfig
change, I could see the below and it was working. However, I will add that there.
$ oc logs -f deployment/metal3 -c metal3-baremetal-operator
...
{"level":"info","ts":1670250809.4937377,"logger":"controllers.BareMetalHost","msg":"registering and validating access to management controller","baremetalhost":"openshift-machine-api/openshift-worker-0","provisioningState":"inspecting","credentials":{"credentials":{"name":"openshift-worker-0-bmc-secret","namespace":"openshift-machine-api"},"credentialsVersion":"1251268"}}
{"level":"info","ts":1670250809.4938302,"logger":"controllers.BareMetalHost","msg":"error building PreprovisioningImage","baremetalhost":"openshift-machine-api/openshift-worker-0","provisioningState":"inspecting","message":"Cannot generate image: no network configuration file(s): --- {}\n"}
{"level":"info","ts":1670250809.4938524,"logger":"controllers.BareMetalHost","msg":"saving host status","baremetalhost":"openshift-machine-api/openshift-worker-0","provisioningState":"inspecting","operational status":"error","provisioning state":"inspecting"}
{"level":"info","ts":1670250809.5001462,"logger":"controllers.BareMetalHost","msg":"publishing event","baremetalhost":"openshift-machine-api/openshift-worker-0","reason":"RegistrationError","message":"Cannot generate image: no network configuration file(s): --- {}\n"}
...
$ oc logs -f deployment/metal3-image-customization
...
{"level":"info","ts":1670250809.3059509,"logger":"controllers.PreprovisioningImage","msg":"updating status","preprovisioningimage":"openshift-machine-api/openshift-worker-0"}
{"level":"info","ts":1670250809.6846116,"logger":"controllers.PreprovisioningImage","msg":"image build failed","preprovisioningimage":"openshift-machine-api/openshift-worker-0","error":"err"}
{"level":"info","ts":1670250809.6887758,"logger":"controllers.PreprovisioningImage","msg":"updating status","preprovisioningimage":"openshift-machine-api/openshift-worker-0"}
{"level":"info","ts":1670250810.077957,"logger":"controllers.PreprovisioningImage","msg":"image build failed","preprovisioningimage":"openshift-machine-api/openshift-worker-0","error":"err"}
{"level":"info","ts":1670250810.0780048,"logger":"controllers.PreprovisioningImage","msg":"updating status","preprovisioningimage":"openshift-machine-api/openshift-worker-0"}
...
/jira refresh |
@dtantsur: This pull request references Jira Issue OCPBUGS-4465, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
@kevydotvinu: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dtantsur, kevydotvinu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
@kevydotvinu: Jira Issue OCPBUGS-4465: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-4465 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Even if the nmstate data is incorrect, the metal3 customized image builds and boots up without the network.