[Bug 1824483] Re: Subiquity DHCP bug

2019-04-17 Thread Michael Hudson-Doyle
You can escape to the terminal by switching to another vt with ctrl- alt-f2 or similar. The files I'd be interested in are /var/log/syslog or the output of "sudo journalctl". Of course getting the files off the server might be fun if the network isn't getting set up, I guess you'll need to plug

[Bug 1824483] Re: Subiquity DHCP bug

2019-04-17 Thread mtsec
Not as far as I could see during the normal installation flow. As I can easily reproduce this issue, which logs would you like to receive? Please include instructions on how to escape to the terminal from within subiquity and the location of the logs you're interested in. -- You received this

[Bug 1824483] Re: Subiquity DHCP bug

2019-04-16 Thread Michael Hudson-Doyle
That's strange, the dhcp part is all handled by systemd-networkd really so I don't think any subiquity changes here are very relevant. Is there anything revealing in the journal or syslog? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1824483] Re: Subiquity DHCP bug

2019-04-12 Thread mtsec
** Attachment added: "ERROR Ubuntu Server 18.04.2 LTS" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1824483/+attachment/5255130/+files/ERROR%20Ubuntu%20Server%2018.04.2%20LTS.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to