[Feature request] "labkey ssh" access to a bridge as well besides a physical interface

Bug #1956778 reported by Taihsiang Ho
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
canonical-server-hwe-utils
New
Undecided
Unassigned

Bug Description

The current d05-2 node uses a bridge (of a physical interface) as the main PXE port. This configuration may result in the failure of "labkey ssh" smart connection[1].

We may enhance labkey to pick up the corresponding IP information of bridge and physical interface both, rather than re-configure d05-2 "back to normal" every time.

[1] labkey ssh d05-2 (after d05-2 is deployed) will raise Traceback:

Traceback (most recent call last):
  File "./labkey", line 401, in <module>
    m.ssh()
  File "./labkey", line 309, in ssh
    ip = machine.boot_interface.links[0].ip_address
  File "/home/tai271828/.local/share/virtualenvs/canonical-server-hwe-utils-q1W0WnoQ/lib/python3.8/site-packages/maas/client/viscera/__init__.py", line 566, in __getitem__
    return self._items[spec]
IndexError: list index out of range

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.