Channel not available

[QUOTE=malcolmlewis;18682]Hi
I didn’t enable the virtualization check box, aside from remming out
the exit 1 bit, the only other thing I changed was;
CODE]
FULLY_UPDATE_THIS_BOX=0
[/CODE]
You shouldn’t need to add the gpg keys etc
Then run on the target machine;

curl -Sks https://test.contoso.com/pub/bootstrap/bootstrap.sles11.sh | /bin/bash


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]

Ok I fixed the bootstrap script and hers is the content:

echo
echo “MINOR MANUAL EDITING OF THIS FILE MAY BE REQUIRED!”
echo
echo “If this bootstrap script was created during the initial installation”
echo “of a SUSE Manager Server, the ACTIVATION_KEYS, and ORG_GPG_KEY values will”
echo “probably not be set (see below). If this is the case, please do the”
echo “following:”
echo " - copy this file to a name specific to its use."
echo " (e.g., to bootstrap-SOME_NAME.sh - like bootstrap-web-servers.sh.)"
echo " - on the website create an activation key or keys for the system(s) to"
echo " be registered."
echo " - edit the values of the VARIABLES below (in this script) as"
echo " appropriate:"
echo " - ACTIVATION_KEYS needs to reflect the activation key(s) value(s)"
echo " from the website. XKEY or XKEY,YKEY"
echo " - ORG_GPG_KEY needs to be set to the name(s) of the corporate public"
echo " GPG key filename(s) (residing in /srv/www/htdocs/pub) if appropriate. XKEY or XKEY,YKEY"
echo
echo “Verify that the script variable settings are correct:”
echo " - CLIENT_OVERRIDES should be only set differently if a customized"
echo " client-config-overrides-VER.txt file was created with a different"
echo " name."
echo " - ensure the value of HOSTNAME is correct."
echo " - ensure the value of ORG_CA_CERT is correct."
echo
echo “Enable this script: comment (with #'s) this block (or, at least just”
echo “the exit below)”
echo
#exit 1

can be edited, but probably correct (unless created during initial install):

NOTE: ACTIVATION_KEYS must be used to bootstrap a client machine.

ACTIVATION_KEYS=1-slesnew
ORG_GPG_KEY=suse-9C800ACA.key,suse-307E3D54.key

can be edited, but probably correct:

CLIENT_OVERRIDES=client-config-overrides.txt
HOSTNAME=sumgr.kardo.com

ORG_CA_CERT=RHN-ORG-TRUSTED-SSL-CERT
ORG_CA_CERT_IS_RPM_YN=0

USING_SSL=1
USING_GPG=1

REGISTER_THIS_BOX=1

ALLOW_CONFIG_ACTIONS=1
ALLOW_REMOTE_COMMANDS=1

FULLY_UPDATE_THIS_BOX=0

and I ran the command

curl -Sks https://test.contoso.com/pub/bootstrap/bootstrap.sles11.sh | /bin/bash

with no luck
REGISTRATION

  • registering

Error Message:
Could not find token ‘1-slesnew’
Error Class Code: 60
Error Class Info:
The activation token specified could not be found on the server.
Please retry with a valid key.

*** Error: Registering the system failed.

Hi
If you created a new key it would be 2-xxxx or did you delete the old
one?

The Description can be mixed characters, but the key shouldn’t, for
example I used;

Description: SLES11-SP3-x86_64 key
Key: sles11-sp3-x86_64_key (the 1- is automatic, but needed in the
bootstrap script)

Selected the base channel etc and then registered a test system.

Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[QUOTE=malcolmlewis;18684]Hi
If you created a new key it would be 2-xxxx or did you delete the old
one?

The Description can be mixed characters, but the key shouldn’t, for
example I used;

Description: SLES11-SP3-x86_64 key
Key: sles11-sp3-x86_64_key (the 1- is automatic, but needed in the
bootstrap script)

Selected the base channel etc and then registered a test system.

Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]

I deleted both key and create a new keys works fine, thanks for that…

How do I add the SLES11 SP3 repos into the channel, thanks.

Hi
I think the gpg stuff being added must have been the issue?

So is the product channel available via the cli? If so then

mgr-ncc-sync -l
spacewalk-repo-sync -c sles11-sp3-pool-x86_64
spacewalk-repo-sync --channel sles11-sp3-pool-x86_64

Or use the web interface to sync.

Once you have the channel available, in the web UI, select Channels →
manage Software Channels → create new channel. Then when creating
select the parent channel you want it in, or make it a parent
(probably better to keep each product as a parent). Then you can add
the channel to your systems as required.


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[QUOTE=malcolmlewis;18690]Hi
I think the gpg stuff being added must have been the issue?

So is the product channel available via the cli? If so then

mgr-ncc-sync -l
spacewalk-repo-sync -c sles11-sp3-pool-x86_64
spacewalk-repo-sync --channel sles11-sp3-pool-x86_64

Or use the web interface to sync.

Once you have the channel available, in the web UI, select Channels →
manage Software Channels → create new channel. Then when creating
select the parent channel you want it in, or make it a parent
(probably better to keep each product as a parent). Then you can add
the channel to your systems as required.


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]

Looks like the SLES SP3 channel is available but
test:~ # mgr-ncc-sync -l
Listing channels …

Status:

  • P - channel is installed (provided)
  • . - channel is not installed, but is available
  • X - channel is not available

[.] sles10-sp3-pool-i586
[.] sles10-sp3-pool-x86_64
[.] sles10-sp4-pool-i586
[.] sles10-sp4-pool-x86_64
[.] sles11-sp1-pool-i586
[P] sles11-sp1-pool-x86_64
[.] sle11-sdk-sp1-pool-x86_64
[.] sle11-sdk-sp1-updates-x86_64
[.] sle11-sdk-sp2-core-x86_64
[.] sle11-sdk-sp2-updates-x86_64
[.] sle11-smt-sp2-pool-x86_64
[.] sle11-smt-sp2-updates-x86_64
[.] sle11-smt-updates-x86_64
[.] sle11-sp1-debuginfo-pool-x86_64
[.] sle11-sp1-debuginfo-updates-x86_64
[.] sle11-sp2-debuginfo-core-x86_64
[.] sle11-sp2-debuginfo-updates-x86_64
[.] sle11-sp2-webyast-1.3-pool-x86_64
[.] sle11-sp2-webyast-1.3-updates-x86_64
[.] sle11-webyast-sp1-pool-x86_64
[.] sle11-webyast-sp1-updates-x86_64
[.] sle11-webyast-sp2-pool-x86_64
[.] sle11-webyast-sp2-updates-x86_64
[.] sles11-extras-x86_64
[X] sles11-sp1-ltss-updates-x86_64
[.] sles11-sp1-suse-manager-tools-x86_64
[P] sles11-sp1-updates-x86_64
[P] sles11-sp2-core-x86_64
[.] sles11-sp2-extension-store-x86_64
[P] sles11-sp2-suse-manager-tools-x86_64
[P] sles11-sp2-updates-x86_64
[.] sles11-sp3-pool-i586
[.] sles11-sp3-pool-x86_64

once I ran the first command I will get this error
test:~ # spacewalk-repo-sync -c sles11-sp3-pool-x86_64
ERROR: attempting to run more than one instance of spacewalk-repo-sync Exiting.

I installed the suse manager client on two sles 11 sp2 nad I can see them on the suse manger GUI but no update is available to patch these two sles 11 sp2, do I need to do any thing?
It is not possible because both sles servers have not update updated yet and the suse manager should pickup the patches but it does not show up any available patches, any idea? I attached the screenshot.

Hi
That’s a good error, it means it’s already syncing the packages from the repositories. If you go to Channels and hit ‘Show All Child Channels’ you should see the package counts increasing, see my attached screenshot as an example. It takes some time depending on your internet connection for me it was around 5 hours for the SLES repo…

[QUOTE=malcolmlewis;18692]Hi
That’s a good error, it means it’s already syncing the packages from the repositories. If you go to Channels and hit ‘Show All Child Channels’ you should see the package counts increasing, see my attached screenshot as an example. It takes some time depending on your internet connection for me it was around 5 hours for the SLES repo…[/QUOTE]

Ok, I got it and it is too slow and I have ADSL 2+ but it is still 2 slow, I can’t see the SLES 11 SP3 under Channels > All Channels.
I saw you attachment and you have OpenSUSE, how can I add the OpenSUSE 12.2?

Hi
So you are seeing the package count going up?

Just create your own repository channels, find a mirror that is close
by from here;
http://mirrors.opensuse.org/

I created a Parent, then added child ones as required, plus a local
repository on the SUSE Manager vm.

Note on my system it’s not active yet (as in no systems added), I am
just about to start having a play with adding a system, but the repo
structure is different so it pulls all the rpms down, I only want
x86_64 and noarch, else it’s a lot of packages (around 27,000 for
openSUSE 13.1 oss repo) get pulled down. So there is some more work to
do for me.


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[QUOTE=malcolmlewis;18694]Hi
So you are seeing the package count going up?

Just create your own repository channels, find a mirror that is close
by from here;
http://mirrors.opensuse.org/

I created a Parent, then added child ones as required, plus a local
repository on the SUSE Manager vm.

Note on my system it’s not active yet (as in no systems added), I am
just about to start having a play with adding a system, but the repo
structure is different so it pulls all the rpms down, I only want
x86_64 and noarch, else it’s a lot of packages (around 27,000 for
openSUSE 13.1 oss repo) get pulled down. So there is some more work to
do for me.


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]

  1. The package count is going up but still can’t see SLES11 SP3

  2. For the OpenSUSE 12.2 how can I add Open SUSE 12.2 repository this to the SUSE MANAGER?
    I have some OpenSUSE12.2 and I want patch them.

  3. “I created a Parent, then added child ones as required, plus a local
    repository on the SUSE Manager vm?”
    Can you please explain this in more details and the steps?

thank you

Hi
You can create your own parent channel under Channels->Manage Software
Channels, for example;

Channel Name*: openSUSE 12.2
Channel Label*: opensuse-12.2
Parent Channel: None
Architecture: x86_64
Channel Summary*: openSUSE 12.2

Then add a 12.2 repository under Manage Repositories;

Repository Label* opensuse-12.2-oss
Repository URL* http://download.opensuse.org/distribution/12.2/repo/oss/suse/
Has Signed Metadata? (I left unchecked)

Then add another channel called (This becomes a child of the parent);

Channel Name: openSUSE 12.2 OSS
Channel Label: opensuse-12.2-oss
Parent Channel: openSUSE 12.2
Architecture: x86_64
Summary: openSUSE 12.2 OSS Channel

And repeat adding repositories and child channels as per requirements.

The adding of openSUSE systems is still under development AFAIK, there
are some folks who have it working, but something I’m playing with at
the moment along with building the rpms, so not something I’m confident
sharing at this point…


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[QUOTE=malcolmlewis;18698]Hi
You can create your own parent channel under Channels->Manage Software
Channels, for example;

Channel Name*: openSUSE 12.2
Channel Label*: opensuse-12.2
Parent Channel: None
Architecture: x86_64
Channel Summary*: openSUSE 12.2

Then add a 12.2 repository under Manage Repositories;

Repository Label* opensuse-12.2-oss
Repository URL* http://download.opensuse.org/distribution/12.2/repo/oss/suse/
Has Signed Metadata? (I left unchecked)

Then add another channel called (This becomes a child of the parent);

Channel Name: openSUSE 12.2 OSS
Channel Label: opensuse-12.2-oss
Parent Channel: openSUSE 12.2
Architecture: x86_64
Summary: openSUSE 12.2 OSS Channel

And repeat adding repositories and child channels as per requirements.

The adding of openSUSE systems is still under development AFAIK, there
are some folks who have it working, but something I’m playing with at
the moment along with building the rpms, so not something I’m confident
sharing at this point…


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]

Great!!

Can you please guys make sure to add the Open SUSE because it will be easy to patch both SLES and OpenSUSE.

So I created a new channel for Open SUSE 12.2 and I added two repo opensuse-12.2-oss and opensuse-12.2-non-oss, can you please check the attached screenshot.

I also noticed that the SLES11 SP1 pool for x86_64 finished and it starts downloading the SLES 11 SP1 Update for x86_64. Is this means once it finishes the SLES SP1 then I will be able to patch the SLES 11 SP1, is this correct?

So is this the same for SLES 11 SP2 I have to wait until download all the patches then will be able to patch the SLES11 SP2.
One more issue I still can’t see the SLES11 SP3, how I am going to add the SLES11 SP3?

Hi
Yes, once the ‘update’ repos have synced, you should see things updating
on the overview screen if the registered systems have updates
available. You can then select, check and push the updates out.

If only the pools have synced, then you could start deploying
additional packages to the registered machines.

It seems to be a serial process, with only one sync occurring at a time.

Let the background syncs to finish and review the status then regarding
the SP3 repos, we can tackle that then if it’s still an issue.

The screenshot looks fine also.


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[QUOTE=malcolmlewis;18702]Hi
Yes, once the ‘update’ repos have synced, you should see things updating
on the overview screen if the registered systems have updates
available. You can then select, check and push the updates out.

If only the pools have synced, then you could start deploying
additional packages to the registered machines.

It seems to be a serial process, with only one sync occurring at a time.

Let the background syncs to finish and review the status then regarding
the SP3 repos, we can tackle that then if it’s still an issue.

The screenshot looks fine also.


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]

The progress of download the patches form the novell server is too slow. I will need to add the SLES 11 SP3, how do I add SP3?

thanks

Hi
So it hasn’t appeared if you run;

mgr-ncc-sync -l

I would suggest logging in to http://www.suse.com and grabbing an eval
licence for SLES 11 SP3, it should then show in your NCC page, then run
the above command again.

Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!