1308469 - socorro rpms are busted for third parties

Status: RESOLVED WONTFIX

(Socorro :: General, task)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

Recently, we switched from using the CentOS system Python version (2.7.5) to a manually installed Python version (2.7.11).

The problem this created is that we now generate RPMs on the build box with 2.7.11. Thus the socorro-virtualenv that gets created has a copy of the 2.7.11 binary and symlinks to the 2.7.11 libs, but those don't exist in a standard CentOS installation and thus the Socorro RPMs are totally busted.

The instructions in the Production install no longer work:

http://socorro.readthedocs.io/en/latest/production-install.html

This bug covers figuring out what to do about that.

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

I think there are a couple of options here.

1. Someone could spin up a fresh CentOS vm, generate an RPM, push that to s3 and then update the Production installation instructions to use that RPM. That RPM would work with standard CentOS, but we wouldn't update it automatically or regularly.

2. Someone fixes the virtualenv creation to copy files and not create symlinks (use the --always-copy flag). Pretty sure that will make the virtualenv contain everything it needs, but I could be wrong about that. This will likely increase the size of the RPM, but I don't know by how much or whether that matters.

3. Someone fixes the RPM so that it doesn't include the virtualenv at all.

4. Someone packages Python 2.7.11 and fixes our build box to use our RPM and then fixes the Socorro RPM to require the Python 2.7.11 RPM.


For now, I'm going to mark the instructions as busted.

Comment 2

[Lonnen :lonnen]

To clarify, this is a problem for third parties installing our RPM, not for Mozilla infrastructure.

Comment 3

[vm]

Any decision on how this will be solved?

Comment 4

[Will Kahn-Greene [:willkg] ET needinfo? me]

I updated the instructions and added a warning. While I suggested options in comment #1, I'm not planning to spend more time on this at present.

If someone else is interested in experimenting with the options and reporting back, that'd be cool. If that doesn't happen, then it's likely this bug will remain in its current status.

vm: Is this something you'd like to work on?

Comment 5

[vm]

Hi Will,

I've tried compiling from source on vanilla CentOS7 but failed there too. I will keep you guys posted, but I don't think I will be of any help here any time soon.

Comment 6

[Will Kahn-Greene [:willkg] ET needinfo? me]

We're not going to solve this because we're switching to docker-based infrastructure and we also no longer support third-parties using Socorro.

Given that, I'm going to mark this as WONTFIX.