Closed sumitjadhav1 closed 3 years ago
cc @digambar15 @snehal1797
/kind bug
Could you open the iDRAC virtual console and check what is actually happening on the nodes? Maybe make a screenshot.
Please make sure you have the latest firmware. Also check if any changes have been made to your network configuration (especially things like MTU).
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale @sumitjadhav1 Any updates on this issue? Is it still an issue for you?
Hi Feruz, sorry for delayed response. When checked with old commit (somewhere around first week of February 2021), issue was still there. Will update the observations with the latest commits this or next week, possibly before meeting.
/remove-lifecycle stale
This issue is not observed, checked with latest commit. Can close for now. Will re-open if seen again.
Verification-RAM-Parameter.txt
Logs to confirm that we were able to on-board real nodes (PowerEdge servers) in Metal3.
Metal3-dev-env commit verified: #658 & Ironic-Image Commit : 258
We're using latest code of metal3-dev-env & our custom changes to introspect real nodes i.e. Dell PowerEdge servers. But it's failing at NBP file download step. Need help from community.
BaseOS=Ubuntu, Kind-Cluster, Container-runtime=docker
Attaching log files & changes we make during successful installation metal3-dev-env. Discussed with @fmuyassarov , @kashifest , the changes done look correct till Node to be in Ready state. metal3-issue.zip
Points to note :