dsc22 : Depends: cassandra (= 2.2.3) but 3.0.0 is to be installed

[sidharthachatterjee]

Hello,

I am trying to use http://thecloudmarket.com/image/ami-8a3b35d8--datastax-auto-clustering-ami-2-6-3-1404-hvm and am facing the following issue —

[INFO] Performing deployment install...
[EXEC] 11/18/15-19:38:39 sudo mv /etc/security/limits.d/cassandra.conf /etc/security/limits.d/cassandra.conf.bak
[EXEC] 11/18/15-19:38:39 sudo apt-get install -y python-cql datastax-agent dsc22:
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dsc22 : Depends: cassandra (= 2.2.3) but 3.0.0 is to be installed

[ERROR] 11/18/15-19:38:39 sudo service cassandra stop:
cassandra: unrecognized service

[EXEC] 11/18/15-19:38:39 sudo rm -rf /var/lib/cassandra
[EXEC] 11/18/15-19:38:39 sudo rm -rf /var/log/cassandra
[EXEC] 11/18/15-19:38:39 sudo mkdir -p /var/lib/cassandra
[EXEC] 11/18/15-19:38:39 sudo mkdir -p /var/log/cassandra
[ERROR] 11/18/15-19:38:39 sudo chown -R cassandra:cassandra /var/lib/cassandra:
chown: invalid user: 'cassandra:cassandra'

[ERROR] 11/18/15-19:38:39 sudo chown -R cassandra:cassandra /var/log/cassandra:
chown: invalid user: 'cassandra:cassandra'

[EXEC] 11/18/15-19:39:18 sudo service opscenterd stop
[INFO] Reflector loop...
[INFO] 11/18/15-19:39:19 Reflector: Received 1 of 1 responses from: [u'172.31.240.141']
[INFO] Seed list: set([u'172.31.240.141'])
[INFO] OpsCenter: 172.31.240.141
[INFO] Options: Namespace(analyticsnodes=0, base64postscript=None, bootstrap=False, cfsreplication=None, clustername='Insider', customreservation=None, email=None, hadoop=False, heapsize=None, multiregion=False, opscenter=None, opscenterinterface=None, opscenterip=None, opscenteronly=False, opscenterssl=False, password=None, raidonly=False, realtimenodes=1, reflector=None, release=None, rpcbinding=False, searchnodes=0, seed_indexes=[0, 1, 1], seeds=None, totalnodes=1, username=None, version='community', vnodes=False)
[ERROR] Exception seen in ds1_launcher.py:
Traceback (most recent call last):
  File "/home/ubuntu/datastax_ami/ds1_launcher.py", line 22, in initial_configurations
    ds2_configure.run()
  File "/home/ubuntu/datastax_ami/ds2_configure.py", line 1179, in run
  File "/home/ubuntu/datastax_ami/ds2_configure.py", line 577, in construct_yaml
IOError: [Errno 2] No such file or directory: '/etc/cassandra/cassandra.yaml'

The user data I am passing is —

--clustername Insider --totalnodes 1 --version community --repository https://github.com/riptano/ComboAMI#b37423990fe18c2d942c1823b322b58f0c390b09

This occurs when I don't pass in the repository option as well. I tried that because I noticed that it was a fix for a similar issue.

[concretevitamin]

+1

I didn't dig into this, but is there any quick workaround?

[sidharthachatterjee]

Okay, I've figured out the issue.

Last evening, version 3.0.0 of cassandra was pushed to its PPA.

When not passing in a specific release version (by passing it in via the --release flag), the configure script (https://github.com/riptano/ComboAMI/blob/2.6/ds2_configure.py#L417) downloads the latest cassandra which dsc22 complains about since it needs version 2.2.3.

A quick fix for this is to pass --release 2.2.3 in the user data. A proper fix would involve updating the else branch to specify a suitable version of cassandra to install.

[mlococo]

That's the correct workaround, and we'll update the install scripts handle 3.0 shortly.

[sidharthachatterjee]

Alright. Thank you, @mlococo.

[mlococo]

Should be fixed now.

[sidharthachatterjee]

@mlococo Ah, that was quick. Thank you.