I got this error:
[root@A00138 ~]# yum update
Loaded plugins: changelog, dellsysid, langpacks, refresh-packagekit
Warning: Environment Group gnome-desktop-environment does not exist.

The system would not update

I ran 'yum clean all' and then rerun the 'yum update' and problem went away.

"yum clean all" does not resolve this issue for me

"yum group mark remove gnome-desktop-environment mate-desktop-environment ..." solves the issue

Why is it that groupname for installation works during installing, but not for update checks?  Seems like a good idea, making the groups remembered objects... it  just seems that it wasn't carried all the way through to working with updates.

After a

    # yum group install 'Xfce Desktop'


when executing

    # yum update

I've got the same environment warning message

    Warning: Environment Group xfce-desktop-environment does not exist.

(and no packages are updated)

A

    # yum clean all

fixed the issue for me, though. The next 'yum update' worked as expected - i.e. no bogus warning message and the expected updates were installed.

I have the same problem on two separate machines.  "yum clean all" does not fix anything for me.

I cannot actually install any groups: it tells me that they don't exist even after it lists the group and gives me all the info on the group.

Picking on Cinnamon as an example:

~]# yum group list ids
Loaded plugins: langpacks, refresh-packagekit, tmprepo
Available environment groups:
   ...
   Cinnamon Desktop (cinnamon-desktop-environment)
   ...

~]# yum group info cinnamon-desktop-environment
Loaded plugins: langpacks, refresh-packagekit, tmprepo

Environment Group: Cinnamon Desktop
 Environment-Id: cinnamon-desktop-environment
 ...

~]# yum group install cinnamon-desktop-environment
Loaded plugins: langpacks, refresh-packagekit, tmprepo
Warning: environment cinnamon-desktop-environment does not exist.
No packages in any requested group available to install or update


How can it list the group and show info on the group, but not actually install it?

I tried the yumex GUI tool and I can install the group that way, but not via the yum command.

(In reply to Jeff Bastian from comment #7)

> How can it list the group and show info on the group, but not actually
> install it?
> 

Same here. I suddenly cannot group-install any desktop anymore!! (It has not always been like this. But today some things went wrong on my computer and now I need to reinstall gnome)

This really is a mess. After yum convert groups following yum update wants to install almost complete Fedora repositories, 48 groups are Warning: does not exist". Marking them all as remove fixes the updates to sane packages, but group install is overall "broken". 

yum group install "Minimal Install" works but no group is in yum group list in the Installed groups list
Yum groups mark-install "Minimal Install" just says at the following yum operations 
Warning: Environment Group minimal-environment does not exist.
Warning: group core does not exist.

yum group info all 
just says
Warning: group/environment all does not exist, while the help says 
info [PACKAGE|all|available|installed|updates|distro-extras|extras|obsoletes|recent]

yum group list lists roughly 40 groups, but there is no "virtualization" group, while with yum group info virtualization prints the group content, the group can not be installed, 

yum group mark-install "ThisGroupDoesNotExist"
Marked install: ThisGroupDoesNotExist
marks any string for installation even it does not exist at all.

Is this GroupAsObject really supposed to work?

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

'yum group mark convert'

worked for me...

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.