Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1995230 - adding repo errors out and does not sync until a few hours later.
Summary: adding repo errors out and does not sync until a few hours later.
Keywords:
Status: CLOSED DUPLICATE of bug 2080348
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.10.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Cole Higgins
URL:
Whiteboard:
: 1995229 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-18 16:28 UTC by jomadiso
Modified: 2023-09-18 04:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-19 17:29:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Backtrace off error (293.13 KB, text/plain)
2021-08-19 14:42 UTC, jomadiso 		no flags Details
View All

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
Note You need to log in before you can comment on or make changes to this bug.