Bug 2273966

Summary: Generating a curl command fails with the error message "There was an error while generating the command, see the logs for more information."
Product: Red Hat Satellite Reporter: Aniket <amahindr>
Component: RegistrationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: ahumbe, lstejska, rlavi, sganar
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 17:27:48 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
Error Screenshot none

Description Aniket 2024-04-08 11:32:24 UTC 
Created attachment 2025839 [details]
Error Screenshot

Created attachment 2025839 [details]
Error Screenshot

Description of problem:

Generating a curl command fails with the error message "There was an error while generating the command, see the logs for more information."


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

Satellite 6.11
Satellite 6.12
Satellite 6.13
Satellite 6.14


How reproducible:

Capsule present at Location1

Steps to Reproduce:

1. In Satellite WebUI at top select Location2.

2. Now proceed to generate curl command.

 Satellite WebUI --> Hosts --> Register Host --> Location "Location1" --> Select Capsule --> Select Activation Key --> Generate

3.


Actual results:

Generating curl command fails with below error:

~~~
There was an error while generating the command, see the logs for more information.
~~~


Expected results:

Curl command should be generated successfully.


Additional info:

Tested on Satellite 6.11, Satellite 6.12, Satellite 6.13 and Satellite 6.14.
Comment 3 Leos Stejskal 2024-04-22 08:45:58 UTC 
Hi, can you provide a site (6.14) where we can reproduce it?
We don't have this problem on our instances.
Comment 5 Eric Helms 2024-06-06 17:27:48 UTC 
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.