Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue withe `bees up` as per the README.md

See original GitHub issue

Following the README instructions to get a hive setup results in less than desired state.

(beesenv) user@machine:~/.../beeswithmachineguns$ tail ./.boto 
[Credentials]
aws_access_key_id = <REMOVED>
aws_secret_access_key = <REMOVED>

[Boto]
ec2_region_name = us-east-1a
ec2_region_endpoint = ec2.us-east-1.amazonaws.com  
(beesenv) user@machine:~/.../beeswithmachineguns$ bees up -s 4 -g ssh -k <REMOVED>
Connecting to the hive.
GroupId found: public
Placement: us-east-1d
Attempting to call up 4 bees.
('Unable to call bees:', u'Value () for parameter groupId is invalid. The value cannot be empty')
Is your sec group available in this region?
None
public
(beesenv) user@machine:~/.../beeswithmachineguns$

Added AWS ‘ssh’ security group with access via SSH from my IP as well. any idea what BWMG is needing at this point?

Issue Analytics

State:
Created 6 years ago
Comments:20

Top GitHub Comments

1reaction

msjmeyercommented, Mar 11, 2018

No problem, ill follow your commands later this week and see if i can replicate your issue.

0reactions

danbadds38commented, Nov 16, 2022

root@ba7d62120c6d:~/.ssh# bees up -s 2 -k bees -g bees-hq -l ubuntu -i ami-02354e95b39ca8dec -z us-east-1a
Connecting to the hive.
GroupId found: bees-hq
Placement: us-east-1a
Attempting to call up 2 bees.
Waiting for bees to load their machine guns...
Traceback (most recent call last):
  File "/usr/local/bin/bees", line 6, in <module>
    main.main()
  File "/usr/local/lib/python2.7/dist-packages/beeswithmachineguns/main.py", line 277, in main
    parse_options()
  File "/usr/local/lib/python2.7/dist-packages/beeswithmachineguns/main.py", line 216, in parse_options
    bees.up(options.servers, options.group, options.zone, options.instance, options.type, options.login, options.key, options.subnet, options.tags, options.bid)
  File "/usr/local/lib/python2.7/dist-packages/beeswithmachineguns/bees.py", line 249, in up
    instance.update()
  File "/usr/local/lib/python2.7/dist-packages/boto/ec2/instance.py", line 413, in update
    rs = self.connection.get_all_reservations([self.id], dry_run=dry_run)
  File "/usr/local/lib/python2.7/dist-packages/boto/ec2/connection.py", line 681, in get_all_reservations
    [('item', Reservation)], verb='POST')
  File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1186, in get_list
    raise self.ResponseError(response.status, response.reason, body)
boto.exception.EC2ResponseError: EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>InvalidInstanceID.NotFound</Code><Message>The instance ID 'i-03b05e9779a78ac90' does not exist</Message></Error></Errors><RequestID>b3d81a8f-83a5-4254-bb14-37066ee4a484</RequestID></Response>

getting an instance ID issue when providing an AMI? not sure but it doesn’t make much sense?