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 1315608 - Enabling OStree repos from imported manifest raises: [E] 400 Bad Request (RestClient::BadRequest)
Summary: Enabling OStree repos from imported manifest raises: [E] 400 Bad Request (Res...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Partha Aji
QA Contact: Sachin Ghai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-08 08:36 UTC by Sachin Ghai
Modified: 2019-04-01 20:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-15 10:21:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
400 Bad Request on enabling ostree repos (82.20 KB, image/png)
2016-03-08 08:36 UTC, Sachin Ghai
no flags Details

Description Sachin Ghai 2016-03-08 08:36:51 UTC
Created attachment 1134065 [details]
400 Bad Request on enabling ostree repos

Description of problem:
I was trying to enable ostree repo from imported manifest and got following:


2016-03-08 03:30:15 [app] [I] Started PUT "/katello/products/67/toggle_repository" for 10.65.193.200 at 2016-03-08 03:30:15 -0500
2016-03-08 03:30:15 [app] [I] Processing by Katello::ProductsController#toggle_repository as */*
2016-03-08 03:30:15 [app] [I]   Parameters: {"repo"=>"1", "pulp_id"=>"Default_Organization-Red_Hat_Enterprise_Linux_Atomic_Host-Red_Hat_Enterprise_Linux_Atomic_Host_Trees", "content_id"=>"3822", "id"=>"67"}
2016-03-08 03:30:15 [foreman-tasks/dynflow] [I] start terminating throttle_limiter...
2016-03-08 03:30:15 [foreman-tasks/dynflow] [I] start terminating client dispatcher...
2016-03-08 03:30:15 [foreman-tasks/dynflow] [I] stop listening for new events...
2016-03-08 03:30:15 [foreman-tasks/dynflow] [I] start terminating clock...
2016-03-08 03:30:15 [foreman-tasks/dynflow] [I] start terminating throttle_limiter...
2016-03-08 03:30:15 [foreman-tasks/dynflow] [I] start terminating client dispatcher...
2016-03-08 03:30:15 [foreman-tasks/dynflow] [I] stop listening for new events...
2016-03-08 03:30:15 [foreman-tasks/dynflow] [I] start terminating clock...
2016-03-08 03:30:17 [katello/pulp_rest] [E] RestClient.post "https://cloud-qe-7.idmqe.lab.eng.bos.redhat.com/pulp/api/v2/repositories/", 105310 byte(s) length, "Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, deflate", "Content-Length"=>"105310", "accept"=>"application/json", "content_type"=>"application/json"
 | \n# => 400 BadRequest | application/json 385 bytes
 | 
2016-03-08 03:30:17 [foreman-tasks/action] [E] 400 Bad Request (RestClient::BadRequest)
 | /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in `return!'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.6.0/lib/runcible/base.rb:79:in `block in get_response'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:228:in `call'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:228:in `process_result'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/rbovirt-0.0.35/lib/restclient_ext/request.rb:50:in `block in transmit'
 | /opt/rh/rh-ruby22/root/usr/share/ruby/net/http.rb:853:in `start'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/rbovirt-0.0.35/lib/restclient_ext/request.rb:44:in `transmit'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:64:in `execute'


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

How reproducible:
always

Steps to Reproduce:
1. import manifest
2. go to OStree repo set
3. enable Red_Hat_Enterprise_Linux_Atomic_Host-Red_Hat_Enterprise_Linux_Atomic_Host_Trees

Actual results:
 [katello/pulp_rest] [E] RestClient.post "https://cloud-qe-7.idmqe.lab.eng.bos.redhat.com/pulp/api/v2/repositories/", 105310 byte(s) length, "Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, deflate", "Content-Length"=>"105310", "accept"=>"application/json", "content_type"=>"application/json"
 | \n# => 400 BadRequest | application/json 385 bytes
 | 
2016-03-08 03:30:17 [foreman-tasks/action] [E] 400 Bad Request (RestClient::BadRequest)


Expected results:
repo should be enabled successfully

Additional info:
Please note that I can enable other rhel repos like rhel7Server with same manifest

Comment 2 Partha Aji 2016-03-11 22:36:48 UTC
Hmm I ve tried this on a couple of sat boxes with Snap 3 and not hit this. Can ya give it a shot the latest snap again. Note you need to have ostree enabled and pulp-ostree available. If you hit this again can you attach a foreman debug?

Comment 3 Sachin Ghai 2016-03-15 10:21:06 UTC
python-gnupg package was blocking me to enable ostree plugin. I enabled it and can sync the ostree with snap3 from CDN now. Thanks.


Note You need to log in before you can comment on or make changes to this bug.