check if project_id is accessible

[durandom]

This is similar to ManageIQ/manageiq#14297
and it seems to be still the root cause here ansible/ansible_tower_client_ruby#68

@jameswnl Did we get to the root cause why this happens? Is it because of a mix of Ansible Tower v2 and v3 in the environment?

fixes https://bugzilla.redhat.com/show_bug.cgi?id=1485414

[miq-bot]

Checked commit durandom@a4ed443 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
1 file checked, 0 offenses detected
Everything looks fine. 🏆

[jameswnl]

This is as best as we can get being limited by ansible/ansible_tower_client_ruby#68 (which may need a overhaul of the way the gem works)

[durandom]

@bdunne you want to take a look?
imo this is an easy fix around ansible/ansible_tower_client_ruby#68

Dont know how far you've got to fix the initial problem in that issue. I still think we should not use the "related" array to create the _id methods

@miq-bot assign @bdunne

[durandom]

@miq-bot add_label blocker

@bdunne can you have a look? This became a blocker

[bdunne]

This could also happen at different levels of the API, but either way, this is probably the best way to fix it.

[bdunne]

@durandom can you add a "Fine" label?

[durandom]

@bdunne label added - can you merge here?

[bdunne]

Thanks, no I don't have merge rights here. Maybe @agrare

[durandom]

FINE BZ is https://bugzilla.redhat.com/show_bug.cgi?id=1496929

[simaishi]

Fine backport (to manageiq repo) details:

$ git log -1
commit 047c3314e171fcf2aefa41fdb2f44a30f9e46db4
Author: Adam Grare <agrare@redhat.com>
Date:   Mon Sep 25 11:08:45 2017 -0400

    Merge pull request #23 from durandom/job_template_project_id
    
    check if project_id is accessible
    (cherry picked from commit 76a9b64616703033bf291bc640a7bcdd19226fb2)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1496929