[
https://issues.apache.org/jira/browse/BIGTOP-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886182#comment-13886182
]
Konstantin Boudnik edited comment on BIGTOP-1192 at 1/30/14 2:12 AM:
---------------------------------------------------------------------
Ok, looks like the 3rd time isn't a charm yet.
- on Ubuntu, {{crond}} doesn't exist. It is called cron
- I'd recommend to declare a final variable for the service name and use it
elsewhere instead of hardcoding the service name
- output of {{service}} command might differ on distro variants. E,g, Ubuntu
says {{cron start/running...}} where's on CentOS it would be {{crond ... is
running}}
- for whatever reason when I am looking into rootShell output all the text I'm
getting as 0th element, not as 2nd
- word running is coming out without parenthesis. Regexp {{/.*\(running\).*/}}
doesn't match anything on Ubuntu (and looks like it won't do on CentOS as well
- {{/.*inactive \(dead\).*/}} won't work on ubuntu, neither on CentOS (where it
will say something like {{crond is stopped}} ) if I am not mistaken.
was (Author: cos):
Ok, looks like the 3rd time isn't a charm yet.
- on Ubuntu, {{crond}} doesn't exist. It is called cron
- I'd recommend to declare a final variable for the service name and use it
elsewhere instead of hardcoding the service name
- output of {{service}} command might differ on distro variants. E,g, Ubuntu
says {{cron start/running...}} where's on CentOS it would be {{crond ... is
running}}
- for whatever reason when I am looking into rootShell output all the text I'm
getting as 0th element, not as 2nd
- word running is coming out without parenthesis. Regexp {{/.*\(running\).*/}}
doesn't match anything on Ubuntu (and looks like it won't do on CentOS as well
- {{/.*inactive \(dead\).*/}} won't work on ubuntu, neither on CentOS (where it
will say something like {{crond is stopped}} if I am not mistaken.
> Add utilities to facilitate cluster failure testing into bigtop-test-framework
> ------------------------------------------------------------------------------
>
> Key: BIGTOP-1192
> URL: https://issues.apache.org/jira/browse/BIGTOP-1192
> Project: Bigtop
> Issue Type: New Feature
> Components: Tests
> Affects Versions: 0.7.0
> Reporter: Mikhail Antonov
> Assignee: Mikhail Antonov
> Labels: itest, smokes
> Fix For: 0.8.0
>
> Attachments: BIGTOP-1192.1.patch, BIGTOP-1192.2.patch,
> BIGTOP-1192.3.patch
>
>
> The goal is to provide Bigtop module maintainers with a set of set of util
> classes to help develop smoke tests able to simulate certain failures during
> smoke tests execution on a cluster.
> Summary of what is provided in current patch.
> Following failure types are supported now:
> - Service stopped and restarted (on given set of nodes)
> - Service killed with 'kill -9' and started back up (on given set of nodes)
> - Node inbound/outbound connections are shut down and brought back up (via
> iptables).
>
> System requirements to run smoke tests with failures.
> * password-less (PKI-based) root ssh to all nodes in cluster being tested
> is assumed.
> * for local tests, like ClusterFailuresTest, one should have password-less
> root ssh to localhost.
> * env variable BIGTOP_SMOKES_CLUSTER_IDENTITY_FILE should point to
> according private key file.
> Further thoughts (not included in this patch)
> Cluster provisioning
> - Bigtop test framework (failures part of it) doesn't need to know about
> cluster topology, as it simply executes set of SSH commands on remote hosts
> (whose addresses are provided by specific
> module smoke test developer). But the actual tests do need to know about
> cluster topology to run sophisticated failure scenarios.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
