Create tests for content host registration against varying hostnames

[JacobCallahan]

As discovered in [1], Satellite isn't properly handling content host registration when content hosts have an underscore in their name. Now that we can use docker to register content hosts, and are able to specify their hostname, we can specifically test for this. I think a small section of tests using our usual set of bad strings will be a good introduction.

[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1375591

[sghai]

This can be tackled in next sprint.

[ntkathole]

Please feel free to re-open, if this still needs fixing.

[JacobCallahan]

This is still something that should be tested.

[tstrych]

@mshriver, can I ask what is expected here ? based on labels I guess new test. but this was verified with 6.3.

If this problem was solved long time ago, and nobody cared from that point, how much credit should be given to it ? To discuss this with myself. On the other hand, most of test cases where created long time ago and yet we still test them. And this BZ has a lot of customer cases. So if it's not one time thing, but it can occur in future, you should implement it.

You bet I will.

[mshriver]

Your analysis is sound - what's expected is you (as component owner for this area) share your thoughts on our path to automating this customer scenario. If you think this area falls to a peer, tag them into this conversation and we can re-assign.

I didn't want to just close this issue based on the fact that the BZ was verified in 6.3, because this could be a meaningful customer scenario regression test. At the time of writing, and still now, it's not an easy case to automate, and will take some time and effort.

As @JacobCallahan stated in Jun2019 (and I think his statement still rings true) this should still be tested. He's working on broker-podman integration, and we're working towards containerized content host testing.

This issue can remain open and assigned, waiting for that day when the path to the automated test case is staightforward. You can add a stubbed test case in the meantime (completely your call).

[JacobCallahan]

Correct. This is still difficult but should be much easier once we have container-based hosts that we can more easily set a hostname on.