jevgeni,
for sure this should have happened during the upgrade. If you still have
the logs from that day you might find the error there. a spelling error in
name or desription might have happened, for instance. anyway, congrats on
solving it.
On Fri, Jul 20, 2018 at 2:45 PM, Jevgeni Zolotarjov
wr
Yes,
But isn't it what is written here
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.1.0/upgrade/upgrade-4.11.html
?
On Fri, Jul 20, 2018 at 3:29 PM Makrand wrote:
> I think you must have tried to register system VM template from template
> menu from the left side
I think you must have tried to register system VM template from template
menu from the left side manually. It will be registered as USER only in
that case.
--
Makrand
On Fri, Jul 20, 2018 at 5:41 PM, Jevgeni Zolotarjov
wrote:
> Eventually I fixed the problem, without clear understanding of the
Eventually I fixed the problem, without clear understanding of the root
cause.
I destroyed routerVM, and cloudstack recreated it. But I discovered, that
it is version 4.11.0. Not 4.11.1!
I checked and systemVM template for 4.11.1 is registered in cloudstack -
all OK.
I noticed however, that its "T
using vxlan as isolation method for advance network ?
On Fri, 20 Jul 2018 at 11:29, Daan Hoogland wrote:
> On Fri, Jul 20, 2018 at 9:09 AM, ilya musayev <
> ilya.mailing.li...@gmail.com>
> wrote:
>
> > Have you tried destroying router vm and let CloudStack create new one ?
> >
> yes, or restart
On Fri, Jul 20, 2018 at 9:09 AM, ilya musayev
wrote:
> Have you tried destroying router vm and let CloudStack create new one ?
>
yes, or restart network with cleanup
>
> On Fri, Jul 20, 2018 at 1:33 AM Jevgeni Zolotarjov >
> wrote:
>
> > - an ip-address conflict.
> > JZ: unlikely, but no
Have you tried destroying router vm and let CloudStack create new one ?
On Fri, Jul 20, 2018 at 1:33 AM Jevgeni Zolotarjov
wrote:
> - an ip-address conflict.
> JZ: unlikely, but not impossible. I tried to restart router VM in
> Network-Guest networks -> defaultGuestNetwork -> VirtualAppliances
- an ip-address conflict.
JZ: unlikely, but not impossible. I tried to restart router VM in
Network-Guest networks -> defaultGuestNetwork -> VirtualAppliances
While rebooting ping to this router VM disappeared. Hence, no other device
is using the same IP.
But!!! when this virtual router started,
that behaviour sound familiar from a couple of cases:
- an ip-address conflict.
- flakey hardware being one of
-+ if card in the host
-+ a router with bad firmware
- of course a strange cofiguration of the software router in you host might
be the issue as well
by all I know this happening after up
I updated cloudstack 4.11.0 -> 4.11.1
Everything went OK during update, but after host reboot guest VMs lost
connection after few minutes of normal work.
I tried restarting network - systemctl restart network.service
then connection was restored again for few minutes
Finally I could restore conne
10 matches
Mail list logo
