*** This bug is a duplicate of bug 1231254 ***
https://bugs.launchpad.net/bugs/1231254
** This bug has been marked a duplicate of bug 1231254
Windows instances need timezone to be localtime
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: nova (Ubuntu)
Status: Confirmed = Triaged
** Changed in: nova (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1026621
** Description changed:
We've been seeing a lot of instances simply vanish from the network.
Usually people have been willing to work around this by simply rebooting
or re-creating their instances, but it's troubling for long-running
instances (especially those that have volumes
Michael,
Thank you for taking a look at this and creating the new bug for
changing the way libvirt virtualizes the hardware clock for Windows vs.
Linux. I believe this to be the root cause for the bug defined here
because of the way Windows handles DHCP renewals.
===DHCP===
As for DHCP, I am
===DHCP===
While I do agree that It would make sense to ping an IP before its lease
is deleted as a extra safety measure. This would not have help this
specific Windows issue as the IP is released by the instance.
--
You received this bug notification because you are a member of Ubuntu
Server
We appear to have solved this problem for ourselves by changing the way
windows deals with time. Remember, the symptom is we are obtaining a
lease from August in 1877. Seems like this is caused by windows using
local time rather than UTC. The solution is to change windows to UTC.
Changed the
Hey Jay,
Funny you posted this. I was about to post the same. after a bunch of
testing and comparing how CLoudStack deals with the Hardware Clock for
Windows with how Openstack is configured by default we also noticed that
the Nova VM template uses a hardware clock with a UTC offset. This is a
** Tags added: libvirt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1026621
Title:
nova-network gets release_fixed_ip events from someplace, but the
database still keeps them
Hi! There seem to be two issues here in the one bug -- DHCP refreshes
are causing problems, and pain with windows instances because of how
they handle timezones and that causing extra DHCP refreshes. I'll
talk about each of those separately.
Windows timezones
=
I'm sorry to hear
The bug for the windows timezone issues is 1231254.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1026621
Title:
nova-network gets release_fixed_ip events from someplace, but the
We are seeing the same thing with Windows2012. Lease times are setting
to the year 1877.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1026621
Title:
nova-network gets
I am running into the same problem. It only seems to occur with Windows
2008 instances. I am running nova-network 2012.2.4 with flatdhcp, but I
have seen the same thing with earlier versions of nova-net.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
My issue is the timezone changing on my Win2k8 instances. When an
instance boots up, it is on UTC. It gets a DHCP lease in this timezone.
After a few minutes, the timezone is then changed to PDT and the time
Windows thinks it obtained the lease gets screwed up (~136 years in the
past). DHCP then
** Changed in: nova
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1026621
Title:
nova-network gets release_fixed_ip events from someplace, but
This is also happening to me EXACTLY as you...
How can I reproduce this bug? This way:
I have a Windows 2008 Raw Image UP in my openstack cloud (ESSEX).
(with a flatdhcp multi-host configuration)
When I create a New instance with this W2008 image everything comes up
smoothly , Everything
Forgot to tell..
When restarting the network interface from windows via VNC, the interface
recovers its IP.
(It affects me everytime somebody creates a new Windows instance)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in
We cannot solve the issue you reported without more information. Could
you please provide the requested information ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1026621
Title:
Keeping on the radar as incomplete...
What Nova version was this happening against ?
** Changed in: nova
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
@Adam:
Bug #1006898 seems unlikely IMHO. We are not running with 'multi_host'
nor with VLANS. So there is one dnsmasq process.
The following is just conjecture as the event has rotated out of the logs and I
have not done any further testing. These events happen rather infrequently, but
are a
Andrew-
Can't seem to reproduce this locally. Its a long shot, but I wonder if
this might be related to the same problems reported in Bug #1006898. Are
there multiple instances of dnsmasq running? I know you're not
configured for VLANing, but I'm interested to know if the proposed fix
there
I should probably clarify that there are no API requests matching this
release_fixed_ip event, and the instance owner explicitly did not want
the event to take place.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
We're running nova with nova.network.manager.FlatDHCPManager. Grepping
the nova-network machine's syslog shows that the last DHCP lease request
was on Jul 16 14:04:29
Sample from the log file:
Jul 16 14:04:29 dziban dnsmasq-dhcp[30249]: DHCPREQUEST(br100) 10.55.60.141
fa:16:3e:11:c5:37
Jul 16
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1026621
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1026621
Title:
nova-network gets release_fixed_ip events from
24 matches
Mail list logo
