Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Incomplete
    • Affects Version/s: B44
    • Fix Version/s: not determined
    • Component/s: ipsenhancement
    • Labels:
      None
    • Environment:

      Operating System: Linux
      Platform: Sun

    • Issuezilla Id:
      1,986

      Description

      Platform : Linux SUSE Enterprise Server 10 SP2 64b
      User : non root user (felidris)

      I downloaded and unzipped the toolkit Pre-installed user image for linux

      I set the publisher URL to the URL of the local repo for that platform :

      felidris@grenache-08-vm01:~/UC24/B44/Linux/pkg-toolkit-linux-i386> ./bin/pkg
      publisher
      PUBLISHER TYPE STATUS URI
      layered.sun.com (preferred) origin online http://localhost:40000/

      I installed updatetool

      I tried to create a second user image on a different location, then I got the
      following message :

      felidris@grenache-08-vm01:~/UC24/B44/Linux/pkg-toolkit-linux-i386> ./bin/pkg
      image-create -U -a test.com=http://localhost:40000 ~/UC24/B44/GUITests/UC2-UT-I002
      Refreshing catalog 1/1 test.com
      The catalog retrieved for publisher 'test.com' only contains package data for
      these publisher(s): layered.sun.com. To resolve this issue, update this
      publisher to use the correct repository origin, or add one of the listed
      publishers using this publisher's repository origin.

      To correct the repository origin, execute the following command as a privileged
      user:

      pkg set-publisher -O <url> test.com

      To add a new publisher using this publisher's repository origin, execute the
      following command as a privileged user:

      pkg set-publisher -O http://localhost:40000/ <publisher>

      After the new publisher has been added, this one should be removed by executing
      the following command as a privileged user:

      pkg unset-publisher test.com

      -----------------------------------------------------------------

      The user image seems to be created, and the publisher seems to be correct :

      felidris@grenache-08-vm01:~/UC24/B44/Linux/pkg-toolkit-linux-i386> ./bin/pkg -R
      ~/UC24/B44/GUITests/UC2-UT-I002 publisher
      PUBLISHER TYPE STATUS URI
      test.com (preferred) origin online http://localhost:40000/
      felidris@grenache-08-vm01:~/UC24/B44/Linux/pkg-toolkit-linux-i386>

      But, I am not able to list the packages available for installation for the
      created user image :

      felidris@grenache-08-vm01:~/UC24/B44/Linux/pkg-toolkit-linux-i386> ./bin/pkg -R
      ~/UC24/B44/GUITests/UC2-UT-I002 list -a
      felidris@grenache-08-vm01:~/UC24/B44/Linux/pkg-toolkit-linux-i386>

      Trying a refresh results to the same message :
      felidris@grenache-08-vm01:~/UC24/B44/Linux/pkg-toolkit-linux-i386> ./bin/pkg -R
      ~/UC24/B44/GUITests/UC2-UT-I002 refresh
      Refreshing catalog 1/1 test.com
      The catalog retrieved for publisher 'test.com' only contains package data for
      these publisher(s): layered.sun.com. To resolve this issue, update this
      publisher to use the correct repository origin, or add one of the listed
      publishers using this publisher's repository origin.

      To correct the repository origin, execute the following command as a privileged
      user:

      pkg set-publisher -O <url> test.com

      To add a new publisher using this publisher's repository origin, execute the
      following command as a privileged user:

      pkg set-publisher -O http://localhost:40000/ <publisher>

      After the new publisher has been added, this one should be removed by executing
      the following command as a privileged user:

      pkg unset-publisher test.com

      felidris@grenache-08-vm01:~/UC24/B44/Linux/pkg-toolkit-linux-i386>

      I then tried to follow the recommendation from the displayed message and to set
      the publisher again, but this did not solve the issue :

      felidris@grenache-08-vm01:~/UC24/B44/Linux/pkg-toolkit-linux-i386> ./bin/pkg -R
      ~/UC24/B44/GUITests/UC2-UT-I002 set-publisher -O http://localhost:40000 test.com
      felidris@grenache-08-vm01:~/UC24/B44/Linux/pkg-toolkit-linux-i386> ./bin/pkg -R
      ~/UC24/B44/GUITests/UC2-UT-I002 refresh
      Refreshing catalog 1/1 test.com
      The catalog retrieved for publisher 'test.com' only contains package data for
      these publisher(s): layered.sun.com. To resolve this issue, update this
      publisher to use the correct repository origin, or add one of the listed
      publishers using this publisher's repository origin.

      To correct the repository origin, execute the following command as a privileged
      user:

      pkg set-publisher -O <url> test.com

      To add a new publisher using this publisher's repository origin, execute the
      following command as a privileged user:

      pkg set-publisher -O http://localhost:40000/ <publisher>

      After the new publisher has been added, this one should be removed by executing
      the following command as a privileged user:

      pkg unset-publisher test.com

      felidris@grenache-08-vm01:~/UC24/B44/Linux/pkg-toolkit-linux-i386>

        Activity

        Hide
        faouzia added a comment -

        Same issue happens if updatetool is used :
        if the local repo is used to create the user image, then the user image is
        created but when I click on the Available-Add-on view, then "No add-ons are
        available" messsage is displayed.

        But, the creation of a user image using an other repo like
        http://pkgshare.sfbay.sun.com/general/dev/ works fine

        Show
        faouzia added a comment - Same issue happens if updatetool is used : if the local repo is used to create the user image, then the user image is created but when I click on the Available-Add-on view, then "No add-ons are available" messsage is displayed. But, the creation of a user image using an other repo like http://pkgshare.sfbay.sun.com/general/dev/ works fine
        Hide
        Tom Mueller added a comment -

        This is the expected behavior with the new pkg(5) software. The name of the
        publisher used in the client must match the publisher name from the server. The
        image creation command should be:

        ./bin/pkg
        image-create -U -a layered.sun.com=http://localhost:40000
        ~/UC24/B44/GUITests/UC2-UT-I002

        Marking this as invalid.

        Show
        Tom Mueller added a comment - This is the expected behavior with the new pkg(5) software. The name of the publisher used in the client must match the publisher name from the server. The image creation command should be: ./bin/pkg image-create -U -a layered.sun.com= http://localhost:40000 ~/UC24/B44/GUITests/UC2-UT-I002 Marking this as invalid.
        Hide
        faouzia added a comment -

        By creating the user image using layered.sun.com as publisher name, then this
        issue was not faced.

        But, I find that this new behavior is introducing a usability issue :

        In updatetool and CLI , it was easier before to create user images, as the name
        of publisher can be anything.

        Now, the user should know both the URL and the publisher name.

        How the user is supposed to be aware of publisher names ? Will he need to access
        to the repository URL ? then click on a given packages to have the pblisher name
        displayed ? This info is not even displayed in the main page when browsing the
        repo, it is displayed when clicking on a given package link.

        Or this is something that should be documented by adopting products ?

        Show
        faouzia added a comment - By creating the user image using layered.sun.com as publisher name, then this issue was not faced. But, I find that this new behavior is introducing a usability issue : In updatetool and CLI , it was easier before to create user images, as the name of publisher can be anything. Now, the user should know both the URL and the publisher name. How the user is supposed to be aware of publisher names ? Will he need to access to the repository URL ? then click on a given packages to have the pblisher name displayed ? This info is not even displayed in the main page when browsing the repo, it is displayed when clicking on a given package link. Or this is something that should be documented by adopting products ?
        Hide
        Tom Mueller added a comment -

        Eventually, the user interfaces will be changed so that the publisher name does
        not need to be specified. A user will enter a URL, and the publisher name will
        be assigned automatically, or, if a URL offers multiple publishers (future
        feature), then the user will need to select one of them.

        Normally, user images will be created at the factory an installed via an
        installer, so the need to assign publishers will be rare. And in those cases
        where this does happen, product teams will be expected to publish the publisher
        names.

        Show
        Tom Mueller added a comment - Eventually, the user interfaces will be changed so that the publisher name does not need to be specified. A user will enter a URL, and the publisher name will be assigned automatically, or, if a URL offers multiple publishers (future feature), then the user will need to select one of them. Normally, user images will be created at the factory an installed via an installer, so the need to assign publishers will be rare. And in those cases where this does happen, product teams will be expected to publish the publisher names.

          People

          • Assignee:
            Tom Mueller
            Reporter:
            faouzia
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: