Hi,
we will need more information. Can you please add the following info:

* Command you used for the registration,
* DEBUG logs with the errors
* (if possible) site where we can reproduce the issue

Thank you

Also one question, is this a regression from the previous release or you can reproduce it only on 6.15?

Hi, I see that you run the command with ignore_errors=true, can I ask why? The field is there for the older versions of the subscription manager, if you use it you take full responsibility for the follow-up misbehavior in the registration process.

What's happening when you don't run it without ignore_errors?

(In reply to Leos Stejskal from comment #4)
> Hi, I see that you run the command with ignore_errors=true, can I ask why?
> The field is there for the older versions of the subscription manager, if
> you use it you take full responsibility for the follow-up misbehavior in the
> registration process.
> 
> What's happening when you don't run it without ignore_errors?

In that case, the registration won't be complete, and it will exit after encountering the first error (HTTP error (422 - Unknown): Validation failed: Content view environment content facets are invalid).

I was able to reproduce the issue as well, with following error:

> rhsm.connection.RestlibException: HTTP error (422 - Unknown): Validation failed: Content view environment content facets is invalid

Moving to the Content component, IMO this is not related to the registration.

Hi,

Thanks, Leos and Nofar,

I selected options to reproduce. I can see some updates that you can reproduce. Let me know if still any details are required.

This seems related to the error we added which disallows you from assigning a host to a lifecycle environment that is not synced on the host's capsule. If the lifecycle environment is indeed not synced to the capsule, this error would be expected (but we should still try to expose better wording so that you know that this is what the issue is.)

Hi Mohit,

Does this issue happen (a) only when the host's lifecycle environment is not synced to the Capsule at time of registration?

Or (b) does it ever happen even when the host's lifecycle environment is properly synced?

Hi Jeremy,

Thanks for checking.

It is (a)
I only observed this issue only when the host's lifecycle environment is not synced to the Capsule at time of registration.


Regards,
Mohit Kushwah

Changed title per https://bugzilla.redhat.com/show_bug.cgi?id=2255276#c5

This commit might fix the issue: https://github.com/Katello/katello/commit/a1c864acdde85deaff5b22e131086cff5e3ffb4a

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.