Server update timestamp not changed when networks are added or removed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Russell Bryant |
Bug Description
As the following recreate scenario shows, a server's "updated" timestamp is not being change when a network is added. This same problem occurs when a network is removed. As a result, the server is not returned as being changed when using the "changes-since" parameter to collect all server changes since a particular time.
I am using OpenStack Grizzly with quantum.
[root@node1 ˜]# nova show TTY_LINUX_TEST
+------
| Property | Value |
+------
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-STS:vm_state | active |
| accessIPv4 | |
| accessIPv6 | |
| config_drive | |
| created | 2013-02-
| flavor | m1.tiny (1) |
| hostId | 4d86eac0d9f3752
| id | 1e928526-
| image | MyBackup_backup (b9a92225-
| key_name | None |
| metadata | {} |
| name | TTY_LINUX_TEST |
| network1 network | |
| progress | 0 |
| security_groups | [{u'name': u'default'}] |
| status | ACTIVE |
| tenant_id | aef72eee4db84e8
| updated | 2013-02-
| user_id | e6de9232200b459
+------
[root@node1 ˜]#
[root@node1 ˜]# quantum net-list
+------
| id | name | subnets |
+------
| d26101d5-
+------
[root@node1 ˜]# nova add-fixed-ip TTY_LINUX_TEST d26101d5-
[root@node1 ˜]# nova show TTY_LINUX_TEST
+------
| Property | Value |
+------
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-STS:vm_state | active |
| accessIPv4 | |
| accessIPv6 | |
| config_drive | |
| created | 2013-02-
| flavor | m1.tiny (1) |
| hostId | 4d86eac0d9f3752
| id | 1e928526-
| image | MyBackup_backup (b9a92225-
| key_name | None |
| metadata | {} |
| name | TTY_LINUX_TEST |
| network1 network | 10.0.1.4 |
| progress | 0 |
| security_groups | [{u'name': u'default'}] |
| status | ACTIVE |
| tenant_id | aef72eee4db84e8
| updated | 2013-02-
| user_id | e6de9232200b459
+------
Changed in nova: | |
assignee: | nobody → Russell Bryant (russellb) |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-rc1 → 2013.1 |
An easy fix for this would be to simply update the instance in the add-fixed-ip remove-fixed-ip code path.