Workaround for python-rados package version

[swiftgist]

Zypper cannot successfully resolve both ceph and python-rados in the same path, but will pick the previous version of librados when python-rados is separated. This allows Stage 0 to complete. Manual intervention may remain on the Salt master due to the deepsea rpm.

Signed-off-by: Eric Jackson ejackson@suse.com

Checklist:

• [ ] Added unittests and or functional tests
• [ ] Adapted documentation
• [ ] Referenced issues or internal bugtracker
• [ ] Ran integration tests successfully (trigger with "@susebot run teuthology" in a GitHub comment; see the wiki for more information)

[jschmid1]

@susebot run teuthology

[susebot]

Commit ef86f78d49a036c0c886846bbe83e1ad55b3e3b9 is NOT OK for suite deepsea:tier2. Check tests results in the Jenkins job: http://ci.ses.suse.de:8080/job/pr-deepsea/380/

[swiftgist]

Looks like this is not needed for the CI.