1:32 p.m.
Hi List,
Red Hat is moving to a new, "certificate-based" registration system.
They are doing away with rhn_register and moving to
subscription-manager.
Here is a trivial but possibly useful snippet which we have saved as
/var/lib/cobbler/snippets/install-puppet:
# Subscribe (register) the system
subscription-manager register --autosubscribe --username=XXXXXXX
--password=XXXXXXXXXX
# Add what used to be called channels
yum -y install yum-utils
yum-config-manager --enable rhel-6-server-optional-rpms
yum-config-manager --enable rhel-6-server-supplementary
I don't know the process for adding it to the cobbler github project,
and I'd want to make the username and password into settings rather
than having them hard coded, but I am open to doing that work and
adding it if it is wanted.
Regards,
Jim
1:37 p.m.
Thanks…
Probably some existence check to see if subscription-manager is present and then falling
back to the old way rhn_register way if that's installed instead sounds reasonable.
Cobbler should already be laying out the yum.repos.d files ok and shouldn't need to do
the channel enablement -- many users are going to be mirroring channels onto their cobbler
server anyway, and using stock yum, so I don't *think* this needs a new parameter to
work with the channel enablement. Maybe it should though.
Patches are pretty easy -- Basically it's just forking the project on github and then
sending github.com/cobbler/cobbler a pull request.
Anyway, one thing at a time -- send me a patch or the subscription-register part and we
can perhaps figure out if channel enablement should be there or not separately?
On Monday, February 13, 2012 at 2:32 PM, Jim Nachlin wrote:
Hi List,
Red Hat is moving to a new, "certificate-based" registration system.
They are doing away with rhn_register and moving to
subscription-manager.
Here is a trivial but possibly useful snippet which we have saved as
/var/lib/cobbler/snippets/install-puppet:
# Subscribe (register) the system
subscription-manager register --autosubscribe --username=XXXXXXX
--password=XXXXXXXXXX
# Add what used to be called channels
yum -y install yum-utils
yum-config-manager --enable rhel-6-server-optional-rpms
yum-config-manager --enable rhel-6-server-supplementary
I don't know the process for adding it to the cobbler github project,
and I'd want to make the username and password into settings rather
than having them hard coded, but I am open to doing that work and
adding it if it is wanted.
Regards,
Jim
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
https://fedorahosted.org/mailman/listinfo/cobbler-devel
2:11 p.m.
On Mon, Feb 13, 2012 at 2:37 PM, Michael DeHaan
<michael.dehaan(a)gmail.com> wrote:
Thanks…
Probably some existence check to see if subscription-manager is present and
then falling back to the old way rhn_register way if that's installed
instead sounds reasonable.
Hi Michael,
It makes a lot of sense to ensure that subscription-manager is
present. I'm not sure about falling back to the other way, though.
My thinking is that a shop will probably either want to use the new
cert-based registration or the old one, and not have the old one
available as a fallback. That is, if you are going with cert-based
registration and the registration fails, you probably just want to
fail and not register (but not fail completely!).
Cobbler should already be laying out the yum.repos.d files ok and shouldn't
need to do the channel enablement -- many users are going to be mirroring
channels onto their cobbler server anyway, and using stock yum, so I don't
*think* this needs a new parameter to work with the channel enablement.
Maybe it should though.
OK. I did not know that. In my case, it seemed to be necessary to
enable the repos explicitly, because there's no longer an
rhn.redhat,com where I can go and add the channels.
Patches are pretty easy -- Basically it's just forking the project on github
and then sending github.com/cobbler/cobbler a pull request.
Anyway, one thing at a time -- send me a patch or the subscription-register
part and we can perhaps figure out if channel enablement should be there or
not separately?
I don't have a patch. The way I did it was to create a complete file.
If there's a way to create a patch for a new file, I can't figure it
out!
I will send you a pull request, though.
Thanks,
Jim
On Monday, February 13, 2012 at 2:32 PM, Jim Nachlin wrote:
Hi List,
Red Hat is moving to a new, "certificate-based" registration system.
They are doing away with rhn_register and moving to
subscription-manager.
Here is a trivial but possibly useful snippet which we have saved as
/var/lib/cobbler/snippets/install-puppet:
# Subscribe (register) the system
subscription-manager register --autosubscribe --username=XXXXXXX
--password=XXXXXXXXXX
# Add what used to be called channels
yum -y install yum-utils
yum-config-manager --enable rhel-6-server-optional-rpms
yum-config-manager --enable rhel-6-server-supplementary
I don't know the process for adding it to the cobbler github project,
and I'd want to make the username and password into settings rather
than having them hard coded, but I am open to doing that work and
adding it if it is wanted.
Regards,
Jim
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel
2:15 p.m.
On Monday, February 13, 2012 at 3:11 PM, Jim Nachlin wrote:
On Mon, Feb 13, 2012 at 2:37 PM, Michael DeHaan
<michael.dehaan(a)gmail.com (mailto:michael.dehaan@gmail.com)> wrote:
> Thanks…
>
> Probably some existence check to see if subscription-manager is present and
> then falling back to the old way rhn_register way if that's installed
> instead sounds reasonable.
>
Hi Michael,
It makes a lot of sense to ensure that subscription-manager is
present. I'm not sure about falling back to the other way, though.
My thinking is that a shop will probably either want to use the new
cert-based registration or the old one, and not have the old one
available as a fallback. That is, if you are going with cert-based
registration and the registration fails, you probably just want to
fail and not register (but not fail completely!).
Yeah, so the script would just figure out which one to use, is what I was suggesting.
What you said was cert based seemed to still take a username/password from what you
pasted.
I suppose if it took a cert the field could hold the cert value and it could try the cert
value first.
I'm not opposed to the system trying all three methods as long as it does decent error
handling
and doesn't crash the installer.
>
> Cobbler should already be laying out the yum.repos.d files ok and shouldn't
> need to do the channel enablement -- many users are going to be mirroring
> channels onto their cobbler server anyway, and using stock yum, so I don't
> *think* this needs a new parameter to work with the channel enablement.
> Maybe it should though.
>
OK. I did not know that. In my case, it seemed to be necessary to
enable the repos explicitly, because there's no longer an
rhn.redhat,com where I can go and add the channels.
>
> Patches are pretty easy -- Basically it's just forking the project on github
> and then sending github.com/cobbler/cobbler (http://github.com/cobbler/cobbler) a
pull request.
>
> Anyway, one thing at a time -- send me a patch or the subscription-register
> part and we can perhaps figure out if channel enablement should be there or
> not separately?
>
I don't have a patch. The way I did it was to create a complete file.
If there's a way to create a patch for a new file, I can't figure it
out!
I will send you a pull request, though.
git-format-patch has some special magic in it.
Anyway, the github pull request is easier as it allows web based merge and such, plus
maintains the queue of patches
we need to review.
Thanks,
Jim
>
>
>
> On Monday, February 13, 2012 at 2:32 PM, Jim Nachlin wrote:
>
> Hi List,
>
> Red Hat is moving to a new, "certificate-based" registration system.
> They are doing away with rhn_register and moving to
> subscription-manager.
>
> Here is a trivial but possibly useful snippet which we have saved as
> /var/lib/cobbler/snippets/install-puppet:
>
>
> # Subscribe (register) the system
> subscription-manager register --autosubscribe --username=XXXXXXX
> --password=XXXXXXXXXX
>
> # Add what used to be called channels
> yum -y install yum-utils
> yum-config-manager --enable rhel-6-server-optional-rpms
> yum-config-manager --enable rhel-6-server-supplementary
>
>
> I don't know the process for adding it to the cobbler github project,
> and I'd want to make the username and password into settings rather
> than having them hard coded, but I am open to doing that work and
> adding it if it is wanted.
>
> Regards,
> Jim
> _______________________________________________
> cobbler-devel mailing list
> cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
> https://fedorahosted.org/mailman/listinfo/cobbler-devel
>
>
>
> _______________________________________________
> cobbler-devel mailing list
> cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
> https://fedorahosted.org/mailman/listinfo/cobbler-devel
>
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
https://fedorahosted.org/mailman/listinfo/cobbler-devel
2:25 p.m.
Pull request submitted.
Maybe someone else will chime in as to the logic of trying different
reg systems. I am a bit of a novice at certificate-based RHN, so
please bear with me. It's my impression that not many people are
using it yet, anyway.
Regards,
Jim
On Mon, Feb 13, 2012 at 3:15 PM, Michael DeHaan
<michael.dehaan(a)gmail.com> wrote:
On Monday, February 13, 2012 at 3:11 PM, Jim Nachlin wrote:
On Mon, Feb 13, 2012 at 2:37 PM, Michael DeHaan
<michael.dehaan(a)gmail.com> wrote:
Thanks…
Probably some existence check to see if subscription-manager is present and
then falling back to the old way rhn_register way if that's installed
instead sounds reasonable.
Hi Michael,
It makes a lot of sense to ensure that subscription-manager is
present. I'm not sure about falling back to the other way, though.
My thinking is that a shop will probably either want to use the new
cert-based registration or the old one, and not have the old one
available as a fallback. That is, if you are going with cert-based
registration and the registration fails, you probably just want to
fail and not register (but not fail completely!).
Yeah, so the script would just figure out which one to use, is what I was
suggesting.
What you said was cert based seemed to still take a username/password from
what you pasted.
I suppose if it took a cert the field could hold the cert value and it could
try the cert value first.
I'm not opposed to the system trying all three methods as long as it does
decent error handling
and doesn't crash the installer.
Cobbler should already be laying out the yum.repos.d files ok and shouldn't
need to do the channel enablement -- many users are going to be mirroring
channels onto their cobbler server anyway, and using stock yum, so I don't
*think* this needs a new parameter to work with the channel enablement.
Maybe it should though.
OK. I did not know that. In my case, it seemed to be necessary to
enable the repos explicitly, because there's no longer an
rhn.redhat,com where I can go and add the channels.
Patches are pretty easy -- Basically it's just forking the project on github
and then sending github.com/cobbler/cobbler a pull request.
Anyway, one thing at a time -- send me a patch or the subscription-register
part and we can perhaps figure out if channel enablement should be there or
not separately?
I don't have a patch. The way I did it was to create a complete file.
If there's a way to create a patch for a new file, I can't figure it
out!
I will send you a pull request, though.
git-format-patch has some special magic in it.
Anyway, the github pull request is easier as it allows web based merge and
such, plus maintains the queue of patches
we need to review.
Thanks,
Jim
On Monday, February 13, 2012 at 2:32 PM, Jim Nachlin wrote:
Hi List,
Red Hat is moving to a new, "certificate-based" registration system.
They are doing away with rhn_register and moving to
subscription-manager.
Here is a trivial but possibly useful snippet which we have saved as
/var/lib/cobbler/snippets/install-puppet:
# Subscribe (register) the system
subscription-manager register --autosubscribe --username=XXXXXXX
--password=XXXXXXXXXX
# Add what used to be called channels
yum -y install yum-utils
yum-config-manager --enable rhel-6-server-optional-rpms
yum-config-manager --enable rhel-6-server-supplementary
I don't know the process for adding it to the cobbler github project,
and I'd want to make the username and password into settings rather
than having them hard coded, but I am open to doing that work and
adding it if it is wanted.
Regards,
Jim
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel
2:28 p.m.
Basically, it should/could still source the same variables as before, right?
On Monday, February 13, 2012 at 3:25 PM, Jim Nachlin wrote:
Pull request submitted.
Maybe someone else will chime in as to the logic of trying different
reg systems. I am a bit of a novice at certificate-based RHN, so
please bear with me. It's my impression that not many people are
using it yet, anyway.
Regards,
Jim
On Mon, Feb 13, 2012 at 3:15 PM, Michael DeHaan
<michael.dehaan(a)gmail.com (mailto:michael.dehaan@gmail.com)> wrote:
>
> On Monday, February 13, 2012 at 3:11 PM, Jim Nachlin wrote:
>
> On Mon, Feb 13, 2012 at 2:37 PM, Michael DeHaan
> <michael.dehaan(a)gmail.com (mailto:michael.dehaan@gmail.com)> wrote:
>
> Thanks…
>
> Probably some existence check to see if subscription-manager is present and
> then falling back to the old way rhn_register way if that's installed
> instead sounds reasonable.
>
>
> Hi Michael,
>
> It makes a lot of sense to ensure that subscription-manager is
> present. I'm not sure about falling back to the other way, though.
> My thinking is that a shop will probably either want to use the new
> cert-based registration or the old one, and not have the old one
> available as a fallback. That is, if you are going with cert-based
> registration and the registration fails, you probably just want to
> fail and not register (but not fail completely!).
>
>
> Yeah, so the script would just figure out which one to use, is what I was
> suggesting.
>
> What you said was cert based seemed to still take a username/password from
> what you pasted.
> I suppose if it took a cert the field could hold the cert value and it could
> try the cert value first.
>
> I'm not opposed to the system trying all three methods as long as it does
> decent error handling
> and doesn't crash the installer.
>
>
>
>
>
>
> Cobbler should already be laying out the yum.repos.d files ok and shouldn't
> need to do the channel enablement -- many users are going to be mirroring
> channels onto their cobbler server anyway, and using stock yum, so I don't
> *think* this needs a new parameter to work with the channel enablement.
> Maybe it should though.
>
>
> OK. I did not know that. In my case, it seemed to be necessary to
> enable the repos explicitly, because there's no longer an
> rhn.redhat,com where I can go and add the channels.
>
>
> Patches are pretty easy -- Basically it's just forking the project on github
> and then sending github.com/cobbler/cobbler (http://github.com/cobbler/cobbler) a
pull request.
>
> Anyway, one thing at a time -- send me a patch or the subscription-register
> part and we can perhaps figure out if channel enablement should be there or
> not separately?
>
>
> I don't have a patch. The way I did it was to create a complete file.
> If there's a way to create a patch for a new file, I can't figure it
> out!
>
> I will send you a pull request, though.
>
>
> git-format-patch has some special magic in it.
>
> Anyway, the github pull request is easier as it allows web based merge and
> such, plus maintains the queue of patches
> we need to review.
>
>
> Thanks,
> Jim
>
>
>
>
> On Monday, February 13, 2012 at 2:32 PM, Jim Nachlin wrote:
>
> Hi List,
>
> Red Hat is moving to a new, "certificate-based" registration system.
> They are doing away with rhn_register and moving to
> subscription-manager.
>
> Here is a trivial but possibly useful snippet which we have saved as
> /var/lib/cobbler/snippets/install-puppet:
>
>
> # Subscribe (register) the system
> subscription-manager register --autosubscribe --username=XXXXXXX
> --password=XXXXXXXXXX
>
> # Add what used to be called channels
> yum -y install yum-utils
> yum-config-manager --enable rhel-6-server-optional-rpms
> yum-config-manager --enable rhel-6-server-supplementary
>
>
> I don't know the process for adding it to the cobbler github project,
> and I'd want to make the username and password into settings rather
> than having them hard coded, but I am open to doing that work and
> adding it if it is wanted.
>
> Regards,
> Jim
> _______________________________________________
> cobbler-devel mailing list
> cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
> https://fedorahosted.org/mailman/listinfo/cobbler-devel
>
>
>
> _______________________________________________
> cobbler-devel mailing list
> cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
> https://fedorahosted.org/mailman/listinfo/cobbler-devel
>
> _______________________________________________
> cobbler-devel mailing list
> cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
> https://fedorahosted.org/mailman/listinfo/cobbler-devel
>
>
>
> _______________________________________________
> cobbler-devel mailing list
> cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
> https://fedorahosted.org/mailman/listinfo/cobbler-devel
>
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
https://fedorahosted.org/mailman/listinfo/cobbler-devel
2:31 p.m.
Never mind, I see this in the second patch.
Anyone else want to offer thoughts (and testing?) before I pull this?
https://github.com/cobbler/cobbler/pull/66
--Michael
On Monday, February 13, 2012 at 3:28 PM, Michael DeHaan wrote:
Basically, it should/could still source the same variables as before,
right?
On Monday, February 13, 2012 at 3:25 PM, Jim Nachlin wrote:
> Pull request submitted.
>
> Maybe someone else will chime in as to the logic of trying different
> reg systems. I am a bit of a novice at certificate-based RHN, so
> please bear with me. It's my impression that not many people are
> using it yet, anyway.
>
> Regards,
> Jim
>
> On Mon, Feb 13, 2012 at 3:15 PM, Michael DeHaan
> <michael.dehaan(a)gmail.com (mailto:michael.dehaan@gmail.com)> wrote:
> >
> > On Monday, February 13, 2012 at 3:11 PM, Jim Nachlin wrote:
> >
> > On Mon, Feb 13, 2012 at 2:37 PM, Michael DeHaan
> > <michael.dehaan(a)gmail.com (mailto:michael.dehaan@gmail.com)> wrote:
> >
> > Thanks…
> >
> > Probably some existence check to see if subscription-manager is present and
> > then falling back to the old way rhn_register way if that's installed
> > instead sounds reasonable.
> >
> >
> > Hi Michael,
> >
> > It makes a lot of sense to ensure that subscription-manager is
> > present. I'm not sure about falling back to the other way, though.
> > My thinking is that a shop will probably either want to use the new
> > cert-based registration or the old one, and not have the old one
> > available as a fallback. That is, if you are going with cert-based
> > registration and the registration fails, you probably just want to
> > fail and not register (but not fail completely!).
> >
> >
> > Yeah, so the script would just figure out which one to use, is what I was
> > suggesting.
> >
> > What you said was cert based seemed to still take a username/password from
> > what you pasted.
> > I suppose if it took a cert the field could hold the cert value and it could
> > try the cert value first.
> >
> > I'm not opposed to the system trying all three methods as long as it does
> > decent error handling
> > and doesn't crash the installer.
> >
> >
> >
> >
> >
> >
> > Cobbler should already be laying out the yum.repos.d files ok and
shouldn't
> > need to do the channel enablement -- many users are going to be mirroring
> > channels onto their cobbler server anyway, and using stock yum, so I don't
> > *think* this needs a new parameter to work with the channel enablement.
> > Maybe it should though.
> >
> >
> > OK. I did not know that. In my case, it seemed to be necessary to
> > enable the repos explicitly, because there's no longer an
> > rhn.redhat,com where I can go and add the channels.
> >
> >
> > Patches are pretty easy -- Basically it's just forking the project on
github
> > and then sending github.com/cobbler/cobbler (http://github.com/cobbler/cobbler)
a pull request.
> >
> > Anyway, one thing at a time -- send me a patch or the subscription-register
> > part and we can perhaps figure out if channel enablement should be there or
> > not separately?
> >
> >
> > I don't have a patch. The way I did it was to create a complete file.
> > If there's a way to create a patch for a new file, I can't figure it
> > out!
> >
> > I will send you a pull request, though.
> >
> >
> > git-format-patch has some special magic in it.
> >
> > Anyway, the github pull request is easier as it allows web based merge and
> > such, plus maintains the queue of patches
> > we need to review.
> >
> >
> > Thanks,
> > Jim
> >
> >
> >
> >
> > On Monday, February 13, 2012 at 2:32 PM, Jim Nachlin wrote:
> >
> > Hi List,
> >
> > Red Hat is moving to a new, "certificate-based" registration system.
> > They are doing away with rhn_register and moving to
> > subscription-manager.
> >
> > Here is a trivial but possibly useful snippet which we have saved as
> > /var/lib/cobbler/snippets/install-puppet:
> >
> >
> > # Subscribe (register) the system
> > subscription-manager register --autosubscribe --username=XXXXXXX
> > --password=XXXXXXXXXX
> >
> > # Add what used to be called channels
> > yum -y install yum-utils
> > yum-config-manager --enable rhel-6-server-optional-rpms
> > yum-config-manager --enable rhel-6-server-supplementary
> >
> >
> > I don't know the process for adding it to the cobbler github project,
> > and I'd want to make the username and password into settings rather
> > than having them hard coded, but I am open to doing that work and
> > adding it if it is wanted.
> >
> > Regards,
> > Jim
> > _______________________________________________
> > cobbler-devel mailing list
> > cobbler-devel(a)lists.fedorahosted.org
(mailto:cobbler-devel@lists.fedorahosted.org)
> > https://fedorahosted.org/mailman/listinfo/cobbler-devel
> >
> >
> >
> > _______________________________________________
> > cobbler-devel mailing list
> > cobbler-devel(a)lists.fedorahosted.org
(mailto:cobbler-devel@lists.fedorahosted.org)
> > https://fedorahosted.org/mailman/listinfo/cobbler-devel
> >
> > _______________________________________________
> > cobbler-devel mailing list
> > cobbler-devel(a)lists.fedorahosted.org
(mailto:cobbler-devel@lists.fedorahosted.org)
> > https://fedorahosted.org/mailman/listinfo/cobbler-devel
> >
> >
> >
> > _______________________________________________
> > cobbler-devel mailing list
> > cobbler-devel(a)lists.fedorahosted.org
(mailto:cobbler-devel@lists.fedorahosted.org)
> > https://fedorahosted.org/mailman/listinfo/cobbler-devel
> >
>
> _______________________________________________
> cobbler-devel mailing list
> cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
> https://fedorahosted.org/mailman/listinfo/cobbler-devel
>
>
>
2:19 p.m.
New subject: Cobbler 2.3.1 Profiles vanish on rename via webui
Hello all!
We just upgraded to Cobbler 2.3.1 <http://cobbler.github.com/> last
week, playing around this afternoon and noticed that if one goes to the
profile list, clicks a 'check box' next to a profile, clicks rename,
enters a new name and then clicks OK the profile disappears. Repeat the
same steps on a different profile except DO NOT check the 'check box'
everything works as expected. It almost seems like clicking the 'check
box' makes cobbler think it is a delete.
Log reads as if it was a rename, but the renamed profile is not seen via
the webui or a profile list from the cmd line.
Mon Feb 13 15:08:20 2012 - INFO | REMOTE version; user(yacketrj)
Mon Feb 13 15:09:09 2012 - INFO | REMOTE has_item(profile); user(?);
name(CentOS-6-i386)
Mon Feb 13 15:09:09 2012 - DEBUG | get_item; ['profile', 'CentOS-6-i386']
Mon Feb 13 15:09:09 2012 - DEBUG | done with get_item; ['profile',
'CentOS-6-i386']
Mon Feb 13 15:09:09 2012 - DEBUG | authorize; ['yacketrj',
'modify_profile', <cobbler.item_prof
ile.Profile instance at 0x2cb5b90>, None, True]
Mon Feb 13 15:09:09 2012 - DEBUG | REMOTE yacketrj authorization result:
True; user(?)
Mon Feb 13 15:09:09 2012 - DEBUG | get_item; ['profile', 'CentOS-6-i386']
Mon Feb 13 15:09:09 2012 - DEBUG | done with get_item; ['profile',
'CentOS-6-i386']
Mon Feb 13 15:09:09 2012 - INFO | REMOTE rename_item(profile);
user(yacketrj); object_id(profil
e::CentOS-6-i386)
Mon Feb 13 15:09:09 2012 - DEBUG | get_item; ['profile', 'CentOS-6-i386']
Mon Feb 13 15:09:09 2012 - DEBUG | done with get_item; ['profile',
'CentOS-6-i386']
*Mon Feb 13 15:09:09 2012 - INFO | rename_item(profile);
['CentOS-6-i386', 'centOS-6-i386']*
Mon Feb 13 15:09:09 2012 - DEBUG | get_items; ['profile']
Mon Feb 13 15:09:09 2012 - DEBUG | done with get_items; ['profile']
Mon Feb 13 15:09:09 2012 - INFO | REMOTE find_items_paged(profile);
criteria({}); sort(name); u
ser(?)
-Ron
2:27 p.m.
New subject: Cobbler 2.3.1 Profiles vanish on rename via webui
On Mon, Feb 13, 2012 at 9:19 PM, Ronald J. Yacketta <yacketrj(a)potsdam.edu>wrote:
Hello all!
We just upgraded to Cobbler 2.3.1 <http://cobbler.github.com/> last week,
playing around this afternoon and noticed that if one goes to the profile
list, clicks a 'check box' next to a profile, clicks rename, enters a new
name and then clicks OK the profile disappears. Repeat the same steps on a
different profile except DO NOT check the 'check box' everything works as
expected. It almost seems like clicking the 'check box' makes cobbler think
it is a delete.
Log reads as if it was a rename, but the renamed profile is not seen via
the webui or a profile list from the cmd line.
Mon Feb 13 15:08:20 2012 - INFO | REMOTE version; user(yacketrj)
Mon Feb 13 15:09:09 2012 - INFO | REMOTE has_item(profile); user(?);
name(CentOS-6-i386)
Mon Feb 13 15:09:09 2012 - DEBUG | get_item; ['profile',
'CentOS-6-i386']
Mon Feb 13 15:09:09 2012 - DEBUG | done with get_item; ['profile',
'CentOS-6-i386']
Mon Feb 13 15:09:09 2012 - DEBUG | authorize; ['yacketrj',
'modify_profile', <cobbler.item_prof
ile.Profile instance at 0x2cb5b90>, None, True]
Mon Feb 13 15:09:09 2012 - DEBUG | REMOTE yacketrj authorization result:
True; user(?)
Mon Feb 13 15:09:09 2012 - DEBUG | get_item; ['profile',
'CentOS-6-i386']
Mon Feb 13 15:09:09 2012 - DEBUG | done with get_item; ['profile',
'CentOS-6-i386']
Mon Feb 13 15:09:09 2012 - INFO | REMOTE rename_item(profile);
user(yacketrj); object_id(profil
e::CentOS-6-i386)
Mon Feb 13 15:09:09 2012 - DEBUG | get_item; ['profile',
'CentOS-6-i386']
Mon Feb 13 15:09:09 2012 - DEBUG | done with get_item; ['profile',
'CentOS-6-i386']
*Mon Feb 13 15:09:09 2012 - INFO | rename_item(profile);
['CentOS-6-i386', 'centOS-6-i386']*
Mon Feb 13 15:09:09 2012 - DEBUG | get_items; ['profile']
Mon Feb 13 15:09:09 2012 - DEBUG | done with get_items; ['profile']
Mon Feb 13 15:09:09 2012 - INFO | REMOTE find_items_paged(profile);
criteria({}); sort(name); u
ser(?)
-Ron
i have verified this and found it to be true.
the profile (or system) json file on disk doesn't get renamed on my cobbler
system...
--
Grtz,
Jörgen Maas
2:29 p.m.
New subject: Cobbler 2.3.1 Profiles vanish on rename via webui
On Mon, Feb 13, 2012 at 9:27 PM, Jörgen Maas <jorgen.maas(a)gmail.com> wrote:
also, the object re-appear after restarting cobblerd
--
Grtz,
Jörgen Maas
2:35 p.m.
New subject: Cobbler 2.3.1 Profiles vanish on rename via webui
On 2/13/2012 3:29 PM, Jörgen Maas wrote:
On Mon, Feb 13, 2012 at 9:27 PM, Jörgen Maas
<jorgen.maas(a)gmail.com
<mailto:jorgen.maas@gmail.com>> wrote:
also, the object re-appear after restarting cobblerd
--
Grtz,
Jörgen Maas
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel
cmd line is broken as well
[root@eden ~]# cobbler profile list
CentOS-6-x86_64
SL-6-i386
SL-6-x86_64
*centOS-6-i386*
f11-PAE-i386
f11-i386
f11-x86_64
f15-PAE-i386
f15-i386
f15-x86_64
f16-PAE-i386
f16-i386
f16-x86_64
rescue-f11-PAE-i386
rescue-f11-i386
rescue-f11-x86_64
[root@eden ~]# cobbler profile rename --name=centOS-6-i386
--newname=CentOS-6-i386
internal error, unknown profile name CentOS-6-i386
[root@eden ~]# cobbler profile list
CentOS-6-x86_64
SL-6-i386
SL-6-x86_64
f11-PAE-i386
f11-i386
f11-x86_64
f15-PAE-i386
f15-i386
f15-x86_64
f16-PAE-i386
f16-i386
f16-x86_64
rescue-f11-PAE-i386
rescue-f11-i386
rescue-f11-x86_64
[root@eden ~]# service cobblerd restart
Stopping cobbler daemon: [ OK ]
Starting cobbler daemon: [ OK ]
[root@eden ~]# cobbler profile list
CentOS-6-x86_64
SL-6-i386
SL-6-x86_64
*centOS-6-i386*
f11-PAE-i386
f11-i386
f11-x86_64
f15-PAE-i386
f15-i386
f15-x86_64
f16-PAE-i386
f16-i386
f16-x86_64
rescue-f11-PAE-i386
rescue-f11-i386
rescue-f11-x86_64
2:36 p.m.
New subject: Cobbler 2.3.1 Profiles vanish on rename via webui
On 2/13/2012 3:35 PM, Ronald J. Yacketta wrote:
On 2/13/2012 3:29 PM, Jörgen Maas wrote:
> On Mon, Feb 13, 2012 at 9:27 PM, Jörgen Maas <jorgen.maas(a)gmail.com
> <mailto:jorgen.maas@gmail.com>> wrote:
>
> also, the object re-appear after restarting cobblerd
>
> --
> Grtz,
> Jörgen Maas
>
>
> _______________________________________________
> cobbler-devel mailing list
> cobbler-devel(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler-devel
cmd line is broken as well
[root@eden ~]# cobbler profile list
CentOS-6-x86_64
SL-6-i386
SL-6-x86_64
*centOS-6-i386*
f11-PAE-i386
f11-i386
f11-x86_64
f15-PAE-i386
f15-i386
f15-x86_64
f16-PAE-i386
f16-i386
f16-x86_64
rescue-f11-PAE-i386
rescue-f11-i386
rescue-f11-x86_64
[root@eden ~]# cobbler profile rename --name=centOS-6-i386
--newname=CentOS-6-i386
internal error, unknown profile name CentOS-6-i386
[root@eden ~]# cobbler profile list
CentOS-6-x86_64
SL-6-i386
SL-6-x86_64
f11-PAE-i386
f11-i386
f11-x86_64
f15-PAE-i386
f15-i386
f15-x86_64
f16-PAE-i386
f16-i386
f16-x86_64
rescue-f11-PAE-i386
rescue-f11-i386
rescue-f11-x86_64
[root@eden ~]# service cobblerd restart
Stopping cobbler daemon: [ OK ]
Starting cobbler daemon: [ OK ]
[root@eden ~]# cobbler profile list
CentOS-6-x86_64
SL-6-i386
SL-6-x86_64
*centOS-6-i386*
f11-PAE-i386
f11-i386
f11-x86_64
f15-PAE-i386
f15-i386
f15-x86_64
f16-PAE-i386
f16-i386
f16-x86_64
rescue-f11-PAE-i386
rescue-f11-i386
rescue-f11-x86_64
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel
Same issue with distros :(
2:41 p.m.
New subject: Cobbler 2.3.1 Profiles vanish on rename via webui
yay!
ok, 200 imaginary cobbler points to the fixer :)
there's probably a save=True or something not being sent to one of the add methods, at
least when it gets out of the XMLRPC layer. perhaps.
On Monday, February 13, 2012 at 3:35 PM, Ronald J. Yacketta wrote:
On 2/13/2012 3:29 PM, Jörgen Maas wrote:
> On Mon, Feb 13, 2012 at 9:27 PM, Jörgen Maas <jorgen.maas(a)gmail.com
(mailto:jorgen.maas@gmail.com)> wrote:
>
> also, the object re-appear after restarting cobblerd
>
cmd line is broken as well
[root@eden ~]# cobbler profile list
CentOS-6-x86_64
SL-6-i386
SL-6-x86_64
centOS-6-i386
f11-PAE-i386
f11-i386
f11-x86_64
f15-PAE-i386
f15-i386
f15-x86_64
f16-PAE-i386
f16-i386
f16-x86_64
rescue-f11-PAE-i386
rescue-f11-i386
rescue-f11-x86_64
[root@eden ~]# cobbler profile rename --name=centOS-6-i386 --newname=CentOS-6-i386
internal error, unknown profile name CentOS-6-i386
[root@eden ~]# cobbler profile list
CentOS-6-x86_64
SL-6-i386
SL-6-x86_64
f11-PAE-i386
f11-i386
f11-x86_64
f15-PAE-i386
f15-i386
f15-x86_64
f16-PAE-i386
f16-i386
f16-x86_64
rescue-f11-PAE-i386
rescue-f11-i386
rescue-f11-x86_64
[root@eden ~]# service cobblerd restart
Stopping cobbler daemon: [ OK ]
Starting cobbler daemon: [ OK ]
[root@eden ~]# cobbler profile list
CentOS-6-x86_64
SL-6-i386
SL-6-x86_64
centOS-6-i386
f11-PAE-i386
f11-i386
f11-x86_64
f15-PAE-i386
f15-i386
f15-x86_64
f16-PAE-i386
f16-i386
f16-x86_64
rescue-f11-PAE-i386
rescue-f11-i386
rescue-f11-x86_64
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
https://fedorahosted.org/mailman/listinfo/cobbler-devel
8:37 a.m.
New subject: Cobbler 2.3.1 Profiles vanish on rename via webui
Michael,
Any tips on were to start looking? Willing to give it a shot, never
wrote any python code but have done perl/c/c++ ;)
-on
On 2/13/2012 3:41 PM, Michael DeHaan wrote:
yay!
ok, 200 imaginary cobbler points to the fixer :)
there's probably a save=True or something not being sent to one of the
add methods, at least when it gets out of the XMLRPC layer. perhaps.
On Monday, February 13, 2012 at 3:35 PM, Ronald J. Yacketta wrote:
> On 2/13/2012 3:29 PM, Jörgen Maas wrote:
>> On Mon, Feb 13, 2012 at 9:27 PM, Jörgen Maas <jorgen.maas(a)gmail.com
>> <mailto:jorgen.maas@gmail.com>> wrote:
>>
>> also, the object re-appear after restarting cobblerd
>>
> cmd line is broken as well
>
> [root@eden ~]# cobbler profile list
> CentOS-6-x86_64
> SL-6-i386
> SL-6-x86_64
> *centOS-6-i386*
> f11-PAE-i386
> f11-i386
> f11-x86_64
> f15-PAE-i386
> f15-i386
> f15-x86_64
> f16-PAE-i386
> f16-i386
> f16-x86_64
> rescue-f11-PAE-i386
> rescue-f11-i386
> rescue-f11-x86_64
> [root@eden ~]# cobbler profile rename --name=centOS-6-i386
> --newname=CentOS-6-i386
> internal error, unknown profile name CentOS-6-i386
> [root@eden ~]# cobbler profile list
> CentOS-6-x86_64
> SL-6-i386
> SL-6-x86_64
> f11-PAE-i386
> f11-i386
> f11-x86_64
> f15-PAE-i386
> f15-i386
> f15-x86_64
> f16-PAE-i386
> f16-i386
> f16-x86_64
> rescue-f11-PAE-i386
> rescue-f11-i386
> rescue-f11-x86_64
> [root@eden ~]# service cobblerd restart
> Stopping cobbler daemon: [ OK ]
> Starting cobbler daemon: [ OK ]
> [root@eden ~]# cobbler profile list
> CentOS-6-x86_64
> SL-6-i386
> SL-6-x86_64
> *centOS-6-i386*
> f11-PAE-i386
> f11-i386
> f11-x86_64
> f15-PAE-i386
> f15-i386
> f15-x86_64
> f16-PAE-i386
> f16-i386
> f16-x86_64
> rescue-f11-PAE-i386
> rescue-f11-i386
> rescue-f11-x86_64
>
>
>
> _______________________________________________
> cobbler-devel mailing list
> cobbler-devel(a)lists.fedorahosted.org
> <mailto:cobbler-devel@lists.fedorahosted.org>
> https://fedorahosted.org/mailman/listinfo/cobbler-devel
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel
8:42 a.m.
New subject: Cobbler 2.3.1 Profiles vanish on rename via webui
API calls all enter into remote.py, and the WebUI and cli.py call that (possibly
incorrectly).
Things should be are all traceable down from there.
On Friday, February 17, 2012 at 9:37 AM, Ronald J. Yacketta wrote:
Michael,
Any tips on were to start looking? Willing to give it a shot, never wrote any python code
but have done perl/c/c++ ;)
-on
On 2/13/2012 3:41 PM, Michael DeHaan wrote:
> yay!
>
> ok, 200 imaginary cobbler points to the fixer :)
>
> there's probably a save=True or something not being sent to one of the add
methods, at least when it gets out of the XMLRPC layer. perhaps.
>
>
> On Monday, February 13, 2012 at 3:35 PM, Ronald J. Yacketta wrote:
>
> > On 2/13/2012 3:29 PM, Jörgen Maas wrote:
> > > On Mon, Feb 13, 2012 at 9:27 PM, Jörgen Maas <jorgen.maas(a)gmail.com
(mailto:jorgen.maas@gmail.com)> wrote:
> > >
> > > also, the object re-appear after restarting cobblerd
> > cmd line is broken as well
> >
> > [root@eden ~]# cobbler profile list
> > CentOS-6-x86_64
> > SL-6-i386
> > SL-6-x86_64
> > centOS-6-i386
> > f11-PAE-i386
> > f11-i386
> > f11-x86_64
> > f15-PAE-i386
> > f15-i386
> > f15-x86_64
> > f16-PAE-i386
> > f16-i386
> > f16-x86_64
> > rescue-f11-PAE-i386
> > rescue-f11-i386
> > rescue-f11-x86_64
> > [root@eden ~]# cobbler profile rename --name=centOS-6-i386
--newname=CentOS-6-i386
> > internal error, unknown profile name CentOS-6-i386
> > [root@eden ~]# cobbler profile list
> > CentOS-6-x86_64
> > SL-6-i386
> > SL-6-x86_64
> > f11-PAE-i386
> > f11-i386
> > f11-x86_64
> > f15-PAE-i386
> > f15-i386
> > f15-x86_64
> > f16-PAE-i386
> > f16-i386
> > f16-x86_64
> > rescue-f11-PAE-i386
> > rescue-f11-i386
> > rescue-f11-x86_64
> > [root@eden ~]# service cobblerd restart
> > Stopping cobbler daemon: [ OK ]
> > Starting cobbler daemon: [ OK ]
> > [root@eden ~]# cobbler profile list
> > CentOS-6-x86_64
> > SL-6-i386
> > SL-6-x86_64
> > centOS-6-i386
> > f11-PAE-i386
> > f11-i386
> > f11-x86_64
> > f15-PAE-i386
> > f15-i386
> > f15-x86_64
> > f16-PAE-i386
> > f16-i386
> > f16-x86_64
> > rescue-f11-PAE-i386
> > rescue-f11-i386
> > rescue-f11-x86_64
> >
> >
> >
> > _______________________________________________
> > cobbler-devel mailing list
> > cobbler-devel(a)lists.fedorahosted.org
(mailto:cobbler-devel@lists.fedorahosted.org)
> > https://fedorahosted.org/mailman/listinfo/cobbler-devel
> >
> >
> >
>
>
>
>
> _______________________________________________ cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
https://fedorahosted.org/mailman/listinfo/cobbler-devel
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org (mailto:cobbler-devel@lists.fedorahosted.org)
https://fedorahosted.org/mailman/listinfo/cobbler-devel
4481
days inactive
4485
days old
cobbler-devel@lists.fedorahosted.org
14 comments
4 participants
participants (4)
-
Jim Nachlin -
Jörgen Maas -
Michael DeHaan -
Ronald J. Yacketta