Mike,
Run iptables-save on the hypervisor running an actual VM, from the rules above
it looks like you are not running any (except system VMs). If you are running a
VM there, then something seems horribly wrong with the security groups.
Another way to check for firewall issues is to disable i
Hi Lucian,
The "Host HA" feature is entirely different from VM HA, however, they may work
in tandem, so please stop using the terms interchangeably as it may cause the
community to believe a regression has been caused.
The "Host HA" feature currently ships with only "Host HA" provider for KVM
Right, sorry for using the terms interchangeably, I see what you mean.
I'll do further testing then as VM HA was also not working in my setup.
I'll be back.
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Rohit Yadav"
> To: "dev"
>
Mike,
I tested basic zone KVM (with and without SG enabled, and with/without local
storage enabled) and could not reproduce the issue. My guest VMs got
ip/hostname from dnsmasq on the shared guest network VR. I tested it using
CentOS7 based KVM box [1], but not with Ubuntu based boxes. It's q
I performed VM HA sanity checks and was not able to reproduce any regression
against two KVM CentOS7 hosts in a cluster.
Without the "Host HA" feature, I deployed few HA-enabled VMs on a KVM host2 and
killed it (powered off). After few minutes of CloudStack attempting to find why
the host (kvm
Hi Mike,
Is dhclient installed in your vm ?
If you have the original password, try to log into the vm, and configure
the ip manually. By this way, we can see if there is issue with networking.
I faced the issue that some vms fail to fetch hostname and password because
of some miconfigurations in
I think I’ve hit a blocker when upgrading to 4.11
Here’s the jira id: https://issues.apache.org/jira/browse/CLOUDSTACK-10236
I’ve upgraded from 4.5 to 4.11, then I’ve logged in with admin and got session
expired immediately.
Regards,
Boris Stoyanov
boris.stoya...@shapeblue.com
www.shapeblue.
4.11.0 looks like an awesome reason ! Special thanks to Rohit !
I vote +0
- I vote for including CLOUDSTACK-9749 [1] into 4.11.0 still
- And if that is accepted, I vote for including CLOUDSTACK-10233 [2] also
(Nuage-internal fix)
thanks
Kris
[1] https://issues.apache.org/jira/browse/CLOUDS
People, People,
a lot of us are busy with meltdown fixes and a full component test takes about
the 72 hours that we have for our voting, I propose to extend the vote period
until at least Monday.
Is that a good idea?
On 17/01/2018, 14:33, "Kris Sterckx" wrote:
4.11.0 looks like an awesom
Yes: I definitely won’t be able to complete my regression tests within the
72-hour window. For 4.12, I plan to automate the remainder of my tests, but I’m
not quite there with 4.11 (the vast majority of managed-storage tests are
automated, but not yet all).
On 1/17/18, 7:34 AM, "Daan Hoogland"
On 01/17/2018 03:34 PM, Daan Hoogland wrote:
People, People,
a lot of us are busy with meltdown fixes and a full component test takes about
the 72 hours that we have for our voting, I propose to extend the vote period
until at least Monday.
Is that a good idea?
Yes please :-) I won't be a
On 01/17/2018 03:34 PM, Daan Hoogland wrote:
> People, People,
>
> a lot of us are busy with meltdown fixes and a full component test takes
> about the 72 hours that we have for our voting, I propose to extend the vote
> period until at least Monday.
+1
I wonder where this 72 hours windows com
It might also be helpful to know what version of ACS as well.
Some indication of your plan/desire to upgrade ACS, hypervisor, or
management server operating system might be helpful.
There is a big difference between the situation where someone is running
ACS 4.9x on CentOS 6 and wants to upgrade
The 72 hours is to make sure all stakeholders had a chance to glance. Testing
is supposed to have happened before. We have a culture of testing only after
RC-cut which is part of the problem. The long duration of a single test run
takes, is another part. And finally, in this case there is the ne
Hi Lucian,
Thanks for the e-mail. I haven’t yet gotten around to trying suggestions from
others, but I did run that script you pointed me to and then rebooted the user
VM that was running on that host. Unfortunately, I see the same results: no
specified hostname and no IP address for that VM.
The good part for 4.11 is that, per Rohit’s testing and comments, it seems like
it’s just an environment misconfiguration that is leading to these results.
That being the case, it’s not an issue we really need to be concerned with for
the 4.11 release candidate.
On 1/17/18, 7:56 AM, "Tutkowski,
If all of our testing were completely in an automated fashion, then I would
agree that the 72-hour window is sufficient. However, we don’t have that kind
of automated coverage and people aren’t always able to immediately begin
testing things out like migrating from their version of CloudStack to
Or perhaps just the first RC should have a longer window?
On 1/17/18, 8:12 AM, "Tutkowski, Mike" wrote:
If all of our testing were completely in an automated fashion, then I would
agree that the 72-hour window is sufficient. However, we don’t have that kind
of automated coverage and people
The 72hrs window is more of a guideline than a rule, without lazy consensus I
don't think we've any choice here, so Monday it is.
Kris - thanks, if we need RC2 and your proposed issues are blocker/critical we
can consider them so meanwhile engage with community to get them reviewed.
Bobby - can
Hi Rohit,
I've reinstalled and tested. Still no go with VM HA.
What I did was to kernel panic that particular HV ("echo c >
/proc/sysrq-trigger" <- this is a proper way to simulate a crash).
What happened next is the HV got marked as "Alert", the VM on it was all the
time marked as "Running" an
Mike,
Ok, at least we can rule out hypervisor firewall side, the problem in your
particular case may be with the VR then, but if you feel further testing is not
warranted then that's fine.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message --
Yes Rohit, tried other browser and I’m not able to login..
I’m +1 on the extend but unfortunately -1 cause of this blocker.
Bobby.
boris.stoya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
On 17 Jan 2018, at 18:24, Rohit Yadav
mailto:r
Once I run through the rest of my testing for the release candidate, I will
turn my attention back to this issue. Thanks!
> On Jan 17, 2018, at 10:53 AM, Nux! wrote:
>
> Mike,
>
> Ok, at least we can rule out hypervisor firewall side, the problem in your
> particular case may be with the VR t
The extension is welcome!
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Boris Stoyanov"
> To: "dev"
> Sent: Wednesday, 17 January, 2018 18:24:20
> Subject: Re: [VOTE] Apache Cloudstack 4.11.0.0 (LTS)
> Yes Rohit, tried other brows
24 matches
Mail list logo
