Landscape Repository Profile Lost After Access Group Change

Bug #1948055 reported by Jose Ortiz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

On standalone (on-prem) landscape web page, I created a new access group, and bulk assigned the new access group to several computers, landscape then generated a bulk activity to "apply repository profiles". The repository profile file for these computers in /etc/apt/sources.list.d/ was changed to .SAVE No new repository profile .LIST file was created. I had to manually move the .SAVE back to .LIST to restore the file. Seems like landscape wants to have a tight link between the repo profile and the access group, when it should not. My understanding is that the repo profile should be tightly linked to the Tag only. I assume if I remove any reference to the access group in the repo profile through landscape-api that this problem might go away. However, I don't think the Landscape software should care about that association.

OS:

Description: Ubuntu 18.04.5 LTS
Release: 18.04

Package details:

Unsure of specific landscape package that executes the landscape Web Server activities described above, so just used this landscape package to provide you with a reference:

$apt-cache policy landscape-common
landscape-common:
  Installed: 18.03~1075~git.256ad02~ubuntu18.04.1
  Candidate: 18.03~1075~git.256ad02~ubuntu18.04.1
  Version table:
 *** 18.03~1075~git.256ad02~ubuntu18.04.1 500
        500 https://archive.landscape.canonical.com bionic/main amd64 Packages
        500 http://ppa.launchpad.net/landscape/19.10/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status
     18.01-0ubuntu3.5 500
        500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
     18.01-0ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1948055/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Jose Ortiz (joortiz) wrote :

I reported this on the the wrong thread.

I re-posted under the correct thread. https://bugs.launchpad.net/landscape/+bug/1948455

You can close this one.

Revision history for this message
Paul White (paulw2u) wrote :

Closed as requested in comment #2.

Changed in ubuntu:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.