[rfe] TripleO CI must collect and publish console logs from fake overcloud nodes during introspection and deployment
Bug #1771082 reported by
Dmitry Tantsur
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Unassigned |
Bug Description
Without seeing what is happening on a node it may be impossible to understand what does not work. See https:/
Changed in tripleo: | |
milestone: | none → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
Changed in tripleo: | |
milestone: | stein-2 → stein-3 |
To post a comment you must log in.
So ovb bmc uses pyghmi:
Looks like pyghmi supports SOL (Serial over Lan), but by default there is no iohandler[1].
Could we create an iohandler in OVB BMC that creates a remote serial console[2] in Openstack Nova?
Then the CI jobs could do:
ipmitool -I lanplus -U admin -P password -H 127.0.0.1 sol acticvate and redirect the output to a file?
[1] https:/ /github. com/openstack/ pyghmi/ blob/master/ pyghmi/ ipmi/bmc. py#L31 /developer. openstack. org/api- ref/compute/ #create- remote- console
[2] https:/