Opened 2 years ago
Closed 2 years ago
#167 closed defect (fixed)
Apply fw rules for templateVMs as well
| Reported by: | joanna | Owned by: | marmarek |
|---|---|---|---|
| Priority: | critical | Milestone: | Release 1 Beta 1 |
| Component: | core | Keywords: | |
| Cc: |
Description
It makes perfect sense to limit the TemplateVM to e.g. only downloads.fedoraproject.org. I assume there is no reason why shouldn't we allow for that, right? (i.e. it doesn't complicate anything)/
Change History (5)
comment:1 follow-up: ↓ 2 Changed 2 years ago by joanna
- Component changed from graphical-manager to core
- Priority changed from major to critical
comment:2 in reply to: ↑ 1 Changed 2 years ago by smoku
Replying to joanna:
Also, for some reason when I start a templatevm no firewallruls (even the default ones) are added in the firewallvm. This makes networking not available in templatevm, which is bad (updates/new sofwtare installation).
It's an issue with VM class hierarchy - firewall rules are generated for AppVMs only (vm.is_appvm()) and TemplateVM is not AppVM.
comment:3 Changed 2 years ago by joanna
- Owner changed from joanna to marmarek
- Status changed from new to assigned
- Summary changed from Allow to edit fw rules for templateVMs as well to Apply fw rules for templateVMs as well
comment:4 Changed 2 years ago by marmarek
- Status changed from assigned to accepted
comment:5 Changed 2 years ago by marmarek
- Resolution set to fixed
- Status changed from accepted to closed
Note: See
TracTickets for help on using
tickets.
Also, for some reason when I start a templatevm no firewallruls (even the default ones) are added in the firewallvm. This makes networking not available in templatevm, which is bad (updates/new sofwtare installation).