Bug #753
No firewall setting shown in UI for newly created machines
| Status: | Closed | Start date: | 07/07/2011 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Kostas Papadimitriou | % Done: | 0% |
|
| Category: | Cyclades UI | Spent time: | - | |
| Target version: | v0.5.1 |
Description
It seems that in certain cases - I cannot reproduce it reliably - the UI will show no firewall
profile selected for a certain VM. One way to show this is to create a new VM, then try to take a look
at its firewall settings.
If I click on a radio button, the setting persists and everything works as it should.
Also, a minor correction: when the firewall settings expand, a very small dark color box appears over
the "Firewall" label, but it is slightly larger and a few pixels off, and it shows.
Related issues
History
#1 Updated by Kostas Papadimitriou almost 11 years ago
At the moment the ui takes as granted that a newly created machine will get added on the public network right after the build process, so it creates the entries in public network without asking the api if the machine exists in the network.
The bug will get solved if we change that behaviour and append machines in public network after the build process.
#2 Updated by Kostas Papadimitriou almost 11 years ago
a simple fix to avoid appending vms with no ip addresses in pulbic network list.
#3 Updated by Vangelis Koukis almost 11 years ago
- Status changed from Assigned to Closed
The real reason was that machines were displayed in the Internet pane even though no public IP address had been assigned to them, now that a fix has been committed this ticket may close.