Broken elastic beasntalk deploy in latest update

[Amos47]

Problem

I'm not sure, but bootcore appears to be missing a variable that is needed in the eb deploy for my setup.

ERROR: UndefinedModelAttributeError - "serviceId" not defined in the metadata of the model: <botocore.model.ServiceModel object at 0x7f1695587050>

Seems to line up with 42a24e8 / atxwebs#43

[KONDO-Yuuki]

me too.
we avoid this problem by specifying aws-cli and awseb-cli version.

pip install awscli==1.16.9 awsebcli==3.14.4

[arnaudmm]

I don't really like being stuck with version but thanks for workaround, hope this get attention and fixed!

[leofernandezg]

+1 Please fix this issue.

[valtlfelipe]

+1 Please fix this. Broke all my deploys

[t-bonatti]

+1 Please fix this

[henrik-io]

+1 please fix this. Can't deploy from Circle CI.

[henrik-io]

I've tried the version workaround suggested in this thread, as well as other suggestions from StackOverflow, but I keep running into the same error :-(

[henrik-io]

BTW, I'm printing out the various versions in my Circle CI build file, and I'm seeing this. Does it look correct?

EB CLI 3.14.5 (Python 2.7.1)
Python 2.7.13
pip 9.0.1 from /usr/lib/python2.7/dist-packages (python 2.7)
aws-cli/1.16.10 Python/2.7.13 Linux/4.4.0-134-generic botocore/1.12.0

[henrik-io]

This got me around the problem:

      sudo apt update && sudo apt install python-pip
      pip install virtualenv
      pip install awscli==1.16.9
      pip install awsebcli

[justnance]

@Amos47, @KONDO-Yuuki, @arnaudmm, @leofernandezg, @valtlfelipe, @t-bonatti, @henrik-io

Thank you to everyone for reaching out and updating this issue. This GitHub repo is for bugs and features regarding the AWS CLI. The Elastic Beanstalk CLI is for a different project and team to which there is no public repo. Generally, it is recommended to reach out to AWS Support or the forums for the Elastic Beanstalk CLI.

As such, I did a little digging and found the AWS Elastic Beanstalk CLI version was updated 2 days ago. It appears the new version may have included a fix:

=========
Changelog
=========
-------------------
3.14.5 (2018-09-07)
-------------------
- Restricted `botocore` version to the range `<1.12` to avoid incompatibility with the EBCLI

[rahulrajaram]

Everyone, EBCLI 3.14.6 has been released. You should be able to use it in the same environment as the latest AWS CLI.

[ahelord]

+1 Please fix this issue. only downgrade awscli==1.16.9 and work.

[leofernandezg]

Verified, fixed in 3.14.6:

Changelog
=========
-------------------
3.14.6 (2018-09-11)
-------------------
- Added `--timeout` argument to the `eb platform create` command
- Added `--timeout` argument to the `eb ssh --setup` command
- Passed `serviceId` as a parameter to the `botocore`-managed service models patched by the EBCLI
- Removed dependency on `tabulate`
- Restricted `urllib3` requirement to range `>1.21,<1.23` to resolve dependency incompatibility between `botocore` and `requests`
- Updated `botocore` requirement to `>=1.12.1,<1.13`

[lucasvinals]

Hi all, just for clarification, if I install latest version of both of them, it works?

Thanks!

[rahulrajaram]

@lucasvinals -- you're correct.