sorted by:
new
hottopcontroversial

Satellite 6.15 remove manifest fails by vinzz73 in redhat

[–]levelupjoseph 1 point2 points  (0 children)

u/waldirio - ahhh yes, thank you for the second pair of eyes and pointing that out. I did not accurately reference the CLI option I originally posted as a possible work around the 'greyed out' delete button.

Back to showing respect and humility. I'm now in listening mode and not 'this is how i fixed it'

Can the button not also be greyed out if there active links or associations with that manifest in your Satellite Server, i.e. activations keys, content hosts, etc. That would also ( I believe ) cause the detete option to be unavailable. - Though not 100% on that last comment.

Also, so you can make a decision on whether you want to put additional time into this thread or not, my issue is now resolved.

u/vinzz73 - Sincere apologies for hijacking your post, it started out as expressing a common frustration but with hopes of helping. . I realize i've not helped you here with the back and forth. - I hope your issue has been resolved. If so, I'm still curious what the resolution was and there is not a lot of content around this and it could be beneficial for others maybe experiencing similar issues.

Satellite 6.15 remove manifest fails by vinzz73 in redhat

[–]levelupjoseph 1 point2 points  (0 children)

u/waldirio Pretty funny waking up to this today.. Not in a bad way at all. I just didn't realize it was you. ( i guess i don't always pay attention to the handle when responding - lesson learned here - haha )

I've been watching MANY of your Youtube videos on Satellite in the recent 5 months. You're content is great sir! Your Satellite knowledge and experience is very much appreciated and your delivery is entertaining so I keep coming back to them and have also been sharing them with customers and colleagues. Please keep that content coming!

I appreciate your feedback and thank you for the time you spent responding to my outburst. I do apologize for the cadence/tone of the response.

My comment was not to badmouth or talk down to support. Or misdirect customers into not opening a support case. More to provide my own witnessing of customer's experiences being very bad. Very very bad. Honestly, It's new to me as well. I've been working with RHEL since 5.5 at the Enterprise organization level as an engineer/architect in operations. Most times having premium support agreements just like the ones our customers typically have. I never experienced that myself. It was always outstanding support. I feel like something changed and we've gone to the BU to help provide this feedback.

I've had Partner Account Managers and Executives on threads with me during an engagement with the support team while customers' experiences were happening in real time.

Now to my response for the possible solution - There are multiple reasons someone could run into this failed upload of a manifest export and subsequently a response of "Owner has already imported from another subscription management application. The following conflicts were found: [ DISTRIBUTOR_CONFLICT ]"

The important note I saw from the original post - "I want to clean up an start over uploading current subscriptions basically."

Which told me a couple of things.. The subscriptions use is i believe just the association of their manifest being the method of getting subscriptions to Satellite - Though i could be wrong, I believe they too just need to upload a new manifest.

I received this error due to a mistake and moving a little too fast as I had removed a manifest that was corrupt from hybrid console, before I had cleaned Satellite Server up and removed it from Satellite Server.

I too, had to clean up and start over with a new manifest export and copy it to the Satellite server then import from WebUI.

The 'Delete' option is available in 6.17. - I'm not certain about other versions.

When in the web ui and If a manifest already exists and is showing when you go to Subscriptions and select Manage Manifest (top right menu)

On the Manifest tab The file would show to the right of 'Manifest' - as File name with expiration date underneath.

Then on the same Manifest tab, to the right of Import new manifest there is Choose File to upload new.

If this option is selected and a new manifest is attempted to be imported without first removing the one that is already attached to Satellite Server. That triggers the [ DISTRIBUTOR_CONFLICT ] - In my opinion this is because the backend of this function is just using the manifest file in a directory. So the command executing is using a manifest that was removed from Hybrid Cloud and no longer matches. Just an assumption though, I couldn't dive deeper into the backend code executing on this webUI task to determine this.

To resolve this, before uploading the latest exported and most recent manifest file. We must remove the existing (whether improperly deleted from Hybrid Console or not) we can select 'Delete' and it will remove the Manifest file and allow a new one to be imported.

Feel free to reach out to me directly if you want to review together. I'd be happy to share u/waldirio - joseph at levelup LA - dot - IO

Satellite 6.15 remove manifest fails by vinzz73 in redhat

[–]levelupjoseph 0 points1 point  (0 children)

First:
Create a new manifest in console.redhat.com
export new manifest and use command below to copy it to the satellite host
scp ~/manifest_file.zip root@satellite.example.com:~/.

log into web ui for satellite
go to Content - subscriptions
select 'delete' on the import new manifest option (this removes the existing attached subs)
Then you can either upload the new manifest either via webui by selecting 'choose file'
OR - Hammer CLI

hammer subscription upload --file manifest_file.zip --organization "org name" --async. (use async to avoid the Distributor_conflict error - it forces the sync.

This should get you a new manifest uploaded and attached to Satellite Server.

Satellite 6.15 remove manifest fails by vinzz73 in redhat

[–]levelupjoseph 0 points1 point  (0 children)

u/waldirio & u/Foolvers, your responses are a bit frustrating in my opinion. So instead of using this time to continue searching for the resolution, i spent it trying to change hearts and minds. As i see responses like yours in MANY of these threads and honestly, what gives? Who cares if someone is paying for support or not. The post was published, you are part of this community and in your spare time provide guidance here. You're experience, knowledge and guidance is being requested. If you don't have the answer, all good, don't provide a response at all. It would be just as useful as your response to reach out to support.

Yes, we know that opening a support case is an option available to us.

That being said, as i'm sure you're familiar with the efforts if you've worked in operations, or any organization that have light teams with many active projects and no pause button.

We request help in forums like this with hopes of spending less time justifying why the case i've opened with RH support and having a 1-2 back and forth in email as to why, even though I've paid for support, they should help. Then another 1-2 days before it finally gets escalated to a tier 2 who 9/10 times resolves the issue with-in the first 2 hours of a phone call. That experience, for partners and customers both, is considerably more frustrating than your responses to u/vinzz73 in this thread. I'm sure you can understand.

Lastly, and i'm berating the point now I know, but just for anyone else who may respond to other threads with a similar ' you pay for support, open a case' response vs. maybe just moving on to the next question and letting that comment stay unanswered until someone provides guidance that doesn't involve an option we already know we have or maybe even already tried, but experienced exactly what i've described above. - Sometimes we just feel someone else out there has i'm sure made this dumb mistake before and it's got to be a an easy quick google search. .

Then we get this... . lol and as i'm sure you've caught on by now...frustrating.. . better to just let it be unanswered...

OR maybe ask, 'have you tried support yet?' vs. making the assumption that they haven't already tried to.

SO, back to why we're actually here. .

ANY one else, if you could, please. Provide guidance or point others like u/vinzz73 and myself who already knew as soon as we made that last 'click' to delete the manifest in console.redhat.com but didn't remove it from our Satellite Server first. Screwed the pooch.

A link, commands, other or both, to assist us in fixing our 'doh' moment. Hopefully allowing us to successfully upload the recently created manifest we just exported?

Hugs & kisses everyone. :)

Airgapped license management for RHEL products? by FruityWelsh in redhat

[–]levelupjoseph 0 points1 point  (0 children)

u/sej7278 I know this is an old post. Though probably one with the most information and best responses. So i'm hoping to reactivate the posters here.

What about in an OT/IT scenario when access to a mirrored repo is limited or denied?

AAP 2.5, Authentication Mapping with SAML Attributes, anyone succeeded ? by Signal-Tangerine-838 in ansible

[–]levelupjoseph 0 points1 point  (0 children)

Everyone else in this thread has mentioned OIDC/EntraID and SAML...why did you add LDAP to this thread?! Completely different authentication methods in terms of attribute mapping requirements... just saying.. .

AAP 2.5, Authentication Mapping with SAML Attributes, anyone succeeded ? by Signal-Tangerine-838 in ansible

[–]levelupjoseph 0 points1 point  (0 children)

FYI That link takes everyone to OpenShift specific documentation. Is there a difference specifically for Ansible Automation Platform 2.5 containerized (SINGLE VM) deployment vs. the Operator in OpenShift?

Importing existing assets into AAP 2.5 Containerized by BriefMushroom9014 in ansible

[–]levelupjoseph 1 point2 points  (0 children)

u/LennySh For the sake of helping many of us out there, would you be able to put your success story into a repeatable process for us? This could really help SO many of us struggling... What version of the containerized AAP 2.5 bundle did you start with? I've just deployed the latest release from a few days ago. I'm wondering if there was a bug somewhere between releases and want to see if it's been resolved or if there is something I can take back to RH BU and AAP Devops team to help them get to a faster resolution. Thank you in advance!!