On 10/21/2015 01:50 AM, Ihar Hrachyshka wrote:
May I ask all bug reporters to attach logs and config files to bugs?
It’s so often the case that logs cited are not enough to understand what’s going on, and
there is no idea which configuration components were using.
Can we please make an additional step to make bug fixing more effective?
Ihar
> On 21 Oct 2015, at 09:57, Alan Pevec <apevec(a)gmail.com> wrote:
>
> 2015-10-21 3:44 GMT+02:00 Sasha Chuzhoy <sasha(a)redhat.com>:
>> While I fail to install the overcloud using the latest bits[1].
>> [1]
https://bugzilla.redhat.com/show_bug.cgi?id=1273680
>
> Does non-HA work?
> I see there's RPC timeout, is rabbitmq up and running?
>
> Cheers,
> Alan
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
What is a good general set of logs for a failed deployment where the
failure cause isn't clear?
--
Dan Sneddon | Principal OpenStack Engineer
dsneddon(a)redhat.com |
redhat.com/openstack
650.254.4025 | dsneddon:irc @dxs:twitter