Bug #22357: "Content Source" not updated in the UI - Katello - Foreman

Actions

Copy link

Bug #22357

closed

"Content Source" not updated in the UI

Added by Evgeni Golov about 7 years ago. Updated almost 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Hosts

Target version:

Katello Recycle Bin

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

This happens on Katello 3.5, but I've also seen reports from Satellite 6.3 Beta (Katello 3.4.5).

When updating a host via the UI, you can set the "Content Source" to whichever proxy available and the next load of the edit page will show that the old proxy is still selected.

However, hammer host info and the API show the correct, new proxy:

Content Information:      
    Content View:          default-p4
    Lifecycle Environment: Library
    Content Source:        pipeline-proxy-3-5-centos7.kangae.example.com

The same happens when updating the host via hammer or the API directly.

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Justin Sherrill about 7 years ago

Translation missing: en.field_release set to 339

Actions

Copy link

Updated by Andrew Kofink about 7 years ago

I have not been able to reproduce this on master/nightly. Does this occur when only switching between two proxies, or does it happen when assigning/removing a proxy?

Actions

Copy link

Updated by Evgeni Golov about 7 years ago

The situation was:

Setup Katello + Proxy using the forklift pipeline job.
Attach a client to the Katello host
Try to move that client to the Proxy

I did not try any other combinations.

Actions

Copy link

Updated by Andrew Kofink about 7 years ago

By "attach a client", do you mean via subscription-manager, puppet? In testing, I used the Katello server itself (added by default as a client) on 3.5, and I am still unable to reproduce this. I'm using the centos7-katello-3-5 and centos7-foreman-proxy-3-5 forklift boxes.

Actions

Copy link