Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2175010

Summary: Some custom repositories are failing to synchorize with error "This field may not be blank" after upgrading to Red Hat Satellite 6.11
Product: Red Hat Satellite Reporter: Odilon Sousa <osousa>
Component: RepositoriesAssignee: Ian Ballou <iballou>
Status: CLOSED ERRATA QA Contact: Sam Bible <sbible>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.11.4CC: avnkumar, chiggins, iballou, juwatts, paji, sajha, vcojot, wpinheir, zhunting
Target Milestone: 6.12.3Keywords: Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-4.5.0.28-1,tfm-rubygem-katello-4.5.0.32-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2149893 Environment:
Last Closed: 2023-04-04 15:20:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 5 Sam Bible 2023-03-30 06:27:44 UTC
Verified on 6.12.3 - Snap 3

Steps to verify:
Followed both of the verification methods above, and both provided the proper results, with the console log for the second issue below:
[root@ip-10-0-167-32 ~]# foreman-rake console
Loading production environment (Rails 6.0.6)
irb(main):001:0> repo = ::Katello::Repository.library.first.root
=> #<Katello::RootRepository id: 1, name: "test1", created_at: "2023-03-30 06:11:36", updated_at: "2023-03-30 06:17:14", major: nil, minor: nil, gpg_key_id: nil, content_id: "1...
irb(main):002:0> repo.upstream_username
=> nil
irb(main):003:0> repo.upstream_password
=> nil
irb(main):004:0> repo.save(validate: false)
=> true
irb(main):005:0> repo.upstream_username
=> nil
irb(main):006:0> repo.upstream_password
=> nil
irb(main):007:0> exit
rake aborted!
Errno::EACCES: Permission denied @ rb_sysopen - /usr/share/foreman/config/irbrc_history
/usr/share/gems/gems/railties-6.0.6/lib/rails/commands/console/console_command.rb:70:in `start'
/usr/share/gems/gems/railties-6.0.6/lib/rails/commands/console/console_command.rb:19:in `start'
/usr/share/gems/gems/railties-6.0.6/lib/rails/commands/console/console_command.rb:102:in `perform'
/usr/share/gems/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
/usr/share/gems/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
/usr/share/gems/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
/usr/share/gems/gems/railties-6.0.6/lib/rails/command/base.rb:69:in `perform'
/usr/share/gems/gems/railties-6.0.6/lib/rails/command.rb:46:in `invoke'
/usr/share/foreman/lib/tasks/console.rake:5:in `block in <top (required)>'
/usr/share/gems/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
Tasks: TOP => console
(See full trace by running task with --trace)
[root@ip-10-0-167-32 ~]# foreman-rake db:migrate:redo
== 2021051713291621250977 AddHostProxyInvocations: reverting ==================
-- remove_index(:host_proxy_invocations, {:column=>[:host_id, :smart_proxy_id]})
   -> 0.0089s
-- drop_table(:host_proxy_invocations)
   -> 0.0074s
== 2021051713291621250977 AddHostProxyInvocations: reverted (0.0164s) =========

== 2021051713291621250977 AddHostProxyInvocations: migrating ==================
-- create_table(:host_proxy_invocations)
   -> 0.0426s
-- add_index(:host_proxy_invocations, [:host_id, :smart_proxy_id], {:unique=>true})
   -> 0.0046s
== 2021051713291621250977 AddHostProxyInvocations: migrated (0.0473s) =========

[root@ip-10-0-167-32 ~]#

Comment 10 errata-xmlrpc 2023-04-04 15:20:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.12.3 Async Security Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:1630