Open lentzi90 opened 1 year ago
/triage accepted
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
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
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
I don't remember whether someone has done or is doing anything related to this. Does anyone have any info on this ? Maybe stuff you have done or are doing overlaps with this? @mquhuy @smoshiur1237 @Sunnatillo @huutomerkki
/remove-lifecycle stale
I don't remember whether someone has done or is doing anything related to this. Does anyone have any info on this ? Maybe stuff you have done or are doing overlaps with this? @mquhuy @smoshiur1237 @Sunnatillo @huutomerkki
I think @huutomerkki is working on some items of this list.
/assign @huutomerkki
User Story
As a developer I would like to collect BMHs and other relevant resources from e2e tests in order to understand failures better.
Detailed Description
The e2e tests currently collects BMO and Ironic logs along with events from the namespaces where the test resources are created. This is already quite good, but in some cases it would be useful to get the complete BMH object. Perhaps other custom resources could also be useful. I would say we should even try to get the state from Ironic's point of view (e.g.
baremetal node list
). See this function in CAPI e2e. We can probably reuse it./kind feature