Bug 1995230

Summary: adding repo errors out and does not sync until a few hours later.
Product: Red Hat Satellite Reporter: jomadiso
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Cole Higgins <chiggins>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.10.0CC: ahumbe, dalley
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-19 17:29:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Backtrace off error none

Description jomadiso 2021-08-18 16:28:09 UTC 
Description of problem: 
When trying to add a repo after importing the manifest I got this error **Task 1eda2efa-3d0e-4b00-a8d3-f00c3e44188d: NoMethodError: undefined method `id' for nil:NilClass**

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Fresh Satellite Build
2. Import New Manifest 6.9. 
3. Content -> Red Hat Repositories -> Recommended Repositories -> Add 
Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server 
4. Error appears
5. Content -> Sync Status -> Select the repo you tried to add.
6. Click "Synchronize now".


Actual results:
When trying to add repo it errors to "NoMethodError: undefined method `id' for nil:NilClass"

When trying to sync the repo it does nothing.

Expected results:
Should add repos with no errors.
Should sync repos with no errors.


Additional info:
Comment 1 jomadiso 2021-08-18 16:29:57 UTC 
This Satellite was built from a 6.9 Satellite through provisioning. 
Deployed from kickstart. 
Added VPN to connect to dogfood Satellite. 
Installed Satellite
Ran the scenario command.
Imported Manifest
Adding repo failed.
Comment 2 Brad Buckingham 2021-08-19 14:21:00 UTC 
Is this error reproducible?
Would it be possible to attach the full stack trace of the errors that occurred?
Can we get access to the env where the error occurred?
Comment 3 Brad Buckingham 2021-08-19 14:21:20 UTC 
*** Bug 1995229 has been marked as a duplicate of this bug. ***
Comment 4 jomadiso 2021-08-19 14:41:34 UTC 
Yes I stood up at least 4 Satellite servers and they all got the same error. There was some conflict with locked tasks so I cleared them and eventually everything worked, but I only tried this on one server. I should be able to add repos as soon as the Satellite is stood up but that's not the case.
This server is within my home env and on the Red Hat vpn. I'm not sure if you would be able to access it. You could try though.
I'll attach the error log I got.
Comment 5 jomadiso 2021-08-19 14:42:18 UTC 
Created attachment 1815718 [details]
Backtrace off error
Comment 6 Daniel Alley 2022-08-24 23:05:40 UTC 
I suspect this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2080348
Comment 7 Brad Buckingham 2022-09-02 20:25:18 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 8 Brad Buckingham 2022-09-02 20:30:51 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 9 Daniel Alley 2022-10-19 17:29:13 UTC 

*** This bug has been marked as a duplicate of bug 2080348 ***
Comment 10 Red Hat Bugzilla 2023-09-18 04:25:15 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days