-
Notifications
You must be signed in to change notification settings - Fork 113
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
missing consol logging makes bmh provisioning fail #228
Comments
The changes I did is available in this fork |
I've updated #226 to remove console=ttyS0 form the kernel, it can now instead be configured. |
That sounds great |
/kind feature |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues close after 30d of inactivity. Reopen the issue with /close |
@metal3-io-bot: Closing this issue. 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. |
Bug 2017412: [4.9] fix Image provisioning fails with file name too long
After upgrade to v0.4.1 the bmh no longer logs syslog to the console during the different phases.
It seems to do with this: #160
This for some odd reason has the effect on my baremetal nodes (Hauwei ibmc managed, UEFI and Legacy bootmode) that it fails in random phases like clean wait, inspection wait.
I am not able to get anything to provision the servers as they all get stuck in clean wait.
After help from the community slack https://kubernetes.slack.com/archives/CHD49TLE7/p1606294233210600
I was able to get syslog to consol re-enabled in the ironic-image.
What did to get it back in working state:
I added ssh-debugging in order to get in the the image and try to run some debugging steps to figure out what was wrong
#226
Then I rebuild the ironic-image to get the required parameters included in the
inspector.ipxe.j2
- I have this file do to the work in the #226 - and theironic.conf.j2
and enabled thesystemd.journald.forward_to_console=yes
This getting the console logging back I am now able to get the bmh to behave as expected, from inspection to full deployment.
At least for me having the possibility to switch on console logging via a env variable would work better than having to hack the image on every new release.
The text was updated successfully, but these errors were encountered: