Public bug reported:
(Cannot figure out what package is causing this, so I'm filing it as a
bug this way.)
What version of Ubuntu?
Ubuntu 20.04 LTS
What I expected to happen?
Normal behavior.
What happened instead?
I have several VMs running on a host, all running Ubuntu 18.04 LTS. To
prepare for an eventual 20.04 upgrade, I upgraded one guest to Ubuntu
20.04.
Everything went smoothly, with no issues.
The next day, however, I try to ssh into the guest, and it is not
responding.
I use virt-manager to show a console window to the guest directly.
Everything seems fine, but when I do "ifconfig", there is no IPv4
address listed (the "inet" line is simply not there, and there is only
an 'inet6' version left). I do an "ifdown eth0 && ifup eth0", and the
IPv4 address is listed again.
Just to see what's going on, I add the following line to cron:
*/5 * * * * (/bin/date && /sbin/ifconfig eth0) >>
/home/webuser/log/ifconfig.output
I check the output later on, and I see that the IPv4 address was being
successfully returned by the ifconfig command, until the 9AM run of this
cron command, and then, the IPv4 address is gone again.
Any ideas? This behavior is only happening on the guest running 20.04
-- the 18.04 guests are unaffected.
** Affects: ubuntu
Importance: Undecided
Status: New
** Description changed:
(Cannot figure out what package is causing this, so I'm filing it as a
bug this way.)
What version of Ubuntu?
- Ubuntu 20.04 LTS (
+ Ubuntu 20.04 LTS
What I expected to happen?
Normal behavior.
What happened instead?
I have several VMs running on a host, all running Ubuntu 18.04 LTS. To
prepare for an eventual 20.04 upgrade, I upgraded one guest to Ubuntu
20.04.
Everything went smoothly, with no issues.
The next day, however, I try to ssh into the guest, and it is not
responding.
I use virt-manager to show a console window to the guest directly.
Everything seems fine, but when I do "ifconfig", there is no IPv4
address listed (the "inet" line is simply not there, and there is only
- an 'inet6' version left). I do a "ifdown eth0 && ifup eth0", and the
+ an 'inet6' version left). I do an "ifdown eth0 && ifup eth0", and the
IPv4 address is listed again.
Just to see what's going on, I add the following line to cron:
*/5 * * * * (/bin/date && /sbin/ifconfig eth0) >>
/home/webuser/log/ifconfig.output
- I check the output later on, and I see that the IPv4 address was beings
+ I check the output later on, and I see that the IPv4 address was being
successfully returned by the ifconfig command, until the 9AM run of this
cron command, and then, the IPv4 address is gone again.
Any ideas?
** Description changed:
(Cannot figure out what package is causing this, so I'm filing it as a
bug this way.)
What version of Ubuntu?
Ubuntu 20.04 LTS
What I expected to happen?
Normal behavior.
What happened instead?
I have several VMs running on a host, all running Ubuntu 18.04 LTS. To
prepare for an eventual 20.04 upgrade, I upgraded one guest to Ubuntu
20.04.
Everything went smoothly, with no issues.
The next day, however, I try to ssh into the guest, and it is not
responding.
I use virt-manager to show a console window to the guest directly.
Everything seems fine, but when I do "ifconfig", there is no IPv4
address listed (the "inet" line is simply not there, and there is only
an 'inet6' version left). I do an "ifdown eth0 && ifup eth0", and the
IPv4 address is listed again.
Just to see what's going on, I add the following line to cron:
*/5 * * * * (/bin/date && /sbin/ifconfig eth0) >>
/home/webuser/log/ifconfig.output
I check the output later on, and I see that the IPv4 address was being
successfully returned by the ifconfig command, until the 9AM run of this
cron command, and then, the IPv4 address is gone again.
- Any ideas?
+ Any ideas? This behavior is only happening on the guest running 20.04
+ -- the 18.04 guests are unaffected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884104
Title:
Ubuntu 20.04 Server "Losing" IP4 address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1884104/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
