The last time i've looked up this issue, it was proposed to use
DNS round-robin, aka add every monitor-IP as A-Record to your monitor-
alias and refer to it by name.
Not, that I like that solution, since it adds up another dependency to
DNS, but that's how we run it since a few years ;)
And no, A
Hi Slavka,
no, i am not using any kind of custome offerings.
I try to provide a more detailled log this time.
Situation:
v-83-VM was the "broken" consoleproxy. So the following log starts with
it's expunging.
Afterwards the new consoleproxy shall be deployed - v-85-VM.
This first deployment (log
Thanks, Chris, for the information!
Are you using custom offerings for the system VMs? Can you share more info
if yes?
About the log, it's not the complete log from where the deployment started.
The deployment begins a bit earlier than what you shared. Can you search
the management log for `Sync
Hi Slavka,
thats what i did after your suggestion / informatin and where the error
occured.
Deleted / Destroyed the consoleproxy and waited till recreation. Which
didn't worked throwing the error i pasted above.
Sorry for beeing so unspecific.
Regards,
Chris
Am Mo., 29. Aug. 2022 um 12:46 Uhr sc
Hey everyone,
I am researching how to configure Cloudstack with Terraform. Unfortunately
i do not seem to find any that are responsible for the assignment of the
physical networks and their labels when zone is created.
Is this functionality included and what are the resources which provide it?
B
Hi Chris,
I mean to recreate the system VMs by destroying them.
On Mon, Aug 29, 2022 at 12:38 PM vas...@gmx.de wrote:
> Hi Slavka,
>
> didn't tried to restart the SystemVMs. Reading through the docs i had the
> impression that "live-patching" would be enough for this
> Anyway - I tried my l
Thank you Abishek! :)
On Mon, Aug 29, 2022 at 12:40 PM Abhishek Kumar <
abhishek.ku...@shapeblue.com> wrote:
> Hi Jordan,
>
> The issue with zone deployment has been fixed with
> https://github.com/apache/cloudstack/pull/6480
>
> You may try using APIs directly with cloudmonkey for now or you can
Hi Slavka,
didn't tried to restart the SystemVMs. Reading through the docs i had the
impression that "live-patching" would be enough for this
Anyway - I tried my luck with the console proxy.
Which failed utterly. Not starting as it isn't finding any useable storage
pool. - logs at the end of
Hi Jordan,
The issue with zone deployment has been fixed with
https://github.com/apache/cloudstack/pull/6480
You may try using APIs directly with cloudmonkey for now or you can also try
the latest nightly build.
You may also try rebuilding UI by referring Advanced customisation from
https://ww
Hey everyone,
I noticed something in the GUI, probably a bug. Here is how to reproduce.
Environment Cloudstack 4.17 installed on Debian 11.
1. Install cloudstack
2. Open the gui and login
3. Go to zones and select new zone
4. Select Zone type and go next
5. fill in zone details and go to the nex
Hi Chris,
Did you recreate the system VMs? In the 4.17 version, the `systemvm.iso` is
deprecated. In its place, you should have the file on agents
`/usr/share/cloudstack-common/vms/agent.zip`.
Can you share the complete log if the system VMs are newly created after
the upgrade?
Best regards,
Slav
11 matches
Mail list logo
